text stringlengths 14 502 |
|---|
[422.88 --> 425.38] And, you know, the allegedly having customer data. |
[426.44 --> 428.42] Good job on not being sure yet. |
[428.64 --> 432.38] But it's just so scary how much different this feels to me. |
[433.00 --> 434.96] You read about hacks like this all the time. |
[435.12 --> 437.80] Equifax was a big one in the States that affected many, many people. |
[437.94 --> 440.26] It didn't affect me, so I didn't really care that much. |
[440.26 --> 453.78] But when the screenshots have towns like Chilliwack, Coquitlam, Langley that are right around us, suddenly you're looking at the spreadsheet, tracing that line across from the town and finding a name. |
[453.90 --> 456.20] And you're like, oh, I might know the name that's right there. |
[456.20 --> 456.84] Yeah. |
[456.84 --> 456.90] Yeah. |
[456.98 --> 460.38] So here's some database snapshots. |
[461.88 --> 462.16] Yeah. |
[462.16 --> 468.98] The top one seems to be of an American database, and the second one seems to be of a Canadian database. |
[470.86 --> 475.30] So if someone bought this data, what could they do with it to screw you? |
[476.20 --> 477.32] They can do a lot. |
[477.32 --> 481.72] We're actually getting into a part of this that we didn't get into last time. |
[481.78 --> 486.54] But they could do actually a lot, especially with employees. |
[486.86 --> 492.68] So I'm going to jump back slightly and cover the different levels of data leak that had happened. |
[492.80 --> 500.12] So for customers, like I had already said, your full name, your address, your payment information, your password, all that kind of stuff, plain text. |
[500.22 --> 500.84] That's a lot. |
[500.92 --> 502.28] There's a lot they can do with that already. |
[502.66 --> 504.74] Now I'm going to jump to other people, however. |
[504.74 --> 510.20] As you can see up here, someone's T4 leaked. |
[511.62 --> 513.30] There's social security numbers. |
[513.56 --> 514.56] Is that the right one? |
[514.72 --> 516.12] I always get them confused because I have both. |
[516.56 --> 517.64] Social insurance number? |
[517.72 --> 518.32] Social insurance. |
[518.40 --> 518.88] Is that Canadian? |
[519.00 --> 519.16] Yeah. |
[519.34 --> 530.22] So your social insurance number, your residential history, because you have to update that with your employer all the time. |
[530.22 --> 538.56] Your first name, your last name, your middle name, like everything that an employer would need to legally employ you, which is a lot, leaked. |
[538.96 --> 540.60] So that's pretty bad. |
[540.70 --> 542.80] So let's go from the customer standpoint first. |
[543.14 --> 546.18] They could take credit out on your credit card. |
[546.28 --> 547.44] They could cash out your credit card. |
[548.30 --> 551.60] They could do those like terrible check things for your credit card. |
[551.60 --> 555.98] Now, would your – the information that leaked, it would have to be of a credit card that's still active? |
[556.16 --> 556.50] Yes. |
[556.62 --> 560.12] So I think that that is definitely a subset of the data. |
[560.40 --> 563.66] Yeah, because to be clear as well, this data goes back forever. |
[564.16 --> 566.00] But only as recent as 2017. |
[566.50 --> 567.60] Well, yeah, because they – |
[567.60 --> 568.00] But credit cards are – |
[568.00 --> 568.58] They went under. |
[568.58 --> 569.14] Three years. |
[569.14 --> 569.22] Three years. |
[570.44 --> 571.76] So if your credit card – |
[571.76 --> 574.26] Yes, but you could renew a credit card and keep the number. |
[575.06 --> 576.92] So you could have the same information. |
[577.64 --> 577.92] Yeah. |
[578.08 --> 579.06] Like I'm pretty – yeah. |
[579.46 --> 579.70] Yeah. |
[579.90 --> 582.30] I'm pretty sure there's one credit card that I have to null now. |
[582.70 --> 583.06] Dang. |
[583.28 --> 584.62] Which kind of sucks because – |
[584.62 --> 585.28] You like that one? |
[585.60 --> 587.86] Well, it's just – I've just been using it for a long time. |
[587.86 --> 592.50] So there's like some recurring billing on it that I'm going to have to kill and reset up. |
[592.70 --> 593.32] It's just annoying. |
[594.78 --> 596.96] But they don't have my more important ones. |
[597.12 --> 597.70] So ha ha ha. |
[597.70 --> 597.78] Yeah. |
[598.50 --> 599.78] But yeah, they could – |
[599.78 --> 600.34] Foiled again! |
[601.38 --> 603.78] They could mess with your credit if they already have that. |
[604.02 --> 610.26] If you paid with PayPal, they probably have your account information because your account – |
[610.26 --> 613.48] Most PayPal accounts that I know of are set up based on the email. |
[613.84 --> 618.88] And you would probably give them the email if you tried to pay through PayPal. |
[620.62 --> 626.76] If your password – if you have that – if you share that password elsewhere – |
[626.76 --> 627.42] Stuffing. |
[628.30 --> 629.18] That's what it's called, right? |
[629.98 --> 632.38] I've been watching that hair in your mouth forever. |
[633.34 --> 635.12] I tried to get rid of it like subtly. |
[635.58 --> 638.18] So Luke's talking and I'm looking at him from the side. |
[638.54 --> 642.20] And the way the lighting is, I can totally see this long hair. |
[642.24 --> 643.02] I don't even know where it came from. |
[643.14 --> 643.46] Me neither. |
[643.70 --> 644.02] It's long. |
[644.02 --> 646.28] Honestly, Ivan filled this cup and I just took a drink. |
[646.52 --> 647.26] So I'm a little – |
[647.26 --> 649.36] There's this long hair sticking out of his mouth. |
[649.86 --> 654.28] And then he finishes his sentence and goes, and I can see it shoot it. |
[656.28 --> 657.14] Totally inhaled it. |
[657.20 --> 658.04] I was like, oh my god. |
[659.62 --> 659.94] Okay. |
[660.00 --> 660.24] Sorry. |
[660.36 --> 660.68] Keep going. |
[660.68 --> 662.00] I don't know what we were talking about. |
[662.36 --> 664.86] We were talking about a password. |
[665.64 --> 665.86] Oh, yeah. |
[665.92 --> 669.08] Stuffing is when, let's say, LinkedIn gets hacked. |
[669.54 --> 670.78] They take your password. |
[671.28 --> 675.58] Well, then you can just take that password and assume that someone uses the password in lots of different sites. |
[675.58 --> 678.40] And they just brute force it on lots of different sites so you can get hacked. |
[678.80 --> 681.68] So you stuff that password and username into everything, essentially. |
[681.98 --> 686.06] So just because LinkedIn got hacked doesn't mean it's the only target for you to get pwned. |
[686.30 --> 693.34] That's why you should have something like a password manager and have unique passwords for every single service and website or whatever that you use. |
[694.34 --> 697.22] But anyways, so password could be a vector for attack. |
[697.42 --> 700.54] They also have your full name and your address and stuff. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.