In Lorenzo, last week, you went down a Twitch-shaped rabbit hole of reporting, and it all started with a recent leak.

Can you hit me with some of the very, very basic facts of kind of what happened that got you started on all this?

Yeah, so a couple of weeks ago, we reported that Twitch had been hacked and that someone posted on the

internet on 4chan, particularly hundreds of gigabytes of internal data, including source code,

financial data of streamers, like their earnings and things like that. And once I wrote that story, I started hearing from

former Twitch employees that essentially told me, wow, it's, you know, it's surprising that

happened again, you know, the hack in 2015, and that was really bad. The hack in 2015 is, is public.

You know, it was already reported at the time,

but all we knew before our story was that Twitch had to reset some passwords because of a

breach and life went on, sort of like, you know, pretty simply. What we, by speaking to this former which employees, however, we discovered that the hack was

much worse than Twitch ever talked about.

First of all, it didn't happen in 2015.

It was discovered in 2014 and the employees I spoke with are not even sure that's when

actually it started the company didn't really have good logs so it wasn't really confident

of when when the hackers got in and you know the breach was bad the hackers got a hold of everyone's passwords, internal databases, source code, just like in the latest incident.

And the company, for months, was trying to recover.

All right.

Well, this is cyber, and this is the story of urgent pizza.

Tad, it's got the code. It's going to launch.

It's a unique system. I know this.

It's how all the files of the whole park.

It tells her everything.

...