Latest / Dark Perimeter: Real Breaches, Real Stakes / The Breach Files — Episode 2: "The Intern"
Transcript
- 0:00SPEAKER_02: September 15, 2022.
- 0:03SPEAKER_02: Somewhere in England, an 18-year-old is sitting in his bedroom.
- 0:06SPEAKER_02: He has a laptop, a phone, and a telegram account.
- 0:10SPEAKER_02: He is about to walk through the front door of one of the most valuable companies in the world.
- 0:14SPEAKER_02: Not because he found a zero day, not because he broke any encryption.
- 0:19SPEAKER_02: Because he asked nicely and the right person said yes.
- 0:23SPEAKER_02: His name online is Teapot.
- 0:25SPEAKER_02: He has been watching Uber for weeks, studying its contractor structure, its help desk workflows, its internal tools.
- 0:33SPEAKER_02: He knows that Uber uses a third-party IT contractor for support.
- 0:37SPEAKER_02: He knows that contractors are almost always the softest point of entry.
- 0:41SPEAKER_02: He knows exactly what he is going to say.
- 0:44SPEAKER_02: Alright, let's go.
- 0:46SPEAKER_02: The attack is called MFA fatigue.
- 0:49SPEAKER_02: The concept is almost embarrassingly simple.
- 0:52SPEAKER_02: You already have someone's username and password, bought from a credential dump, stolen from a prior breach, or fished in a previous step.
- 1:00SPEAKER_02: You try to log in.
- 1:02SPEAKER_02: The system sends a push notification to the victim's phone, asking them to approve the login.
- 1:08SPEAKER_02: You send the request again, and again, and again, at 2 in the morning, at 3, at 4.
- 1:17SPEAKER_02: You send it until the victim, exhausted and confused, taps approve just to make it stop.
- 1:23SPEAKER_04: What?
- 1:24SPEAKER_04: Another one?
- 1:25SPEAKER_04: I already denied this twice.
- 1:27SPEAKER_04: This thing won't stop.
- 1:29SPEAKER_02: Then T Pot calls him.
- 1:31SPEAKER_04: Not as a hacker, as IT.
- 1:33SPEAKER_04: Hey Marcus.
- 1:34SPEAKER_04: Yeah, this is Jake from IT Security.
- 1:37SPEAKER_04: Sorry to bother you, I know it's late.
- 1:39SPEAKER_04: We're seeing some weird authentication activity on your account, and I just need to verify a couple things with you to get it cleared up.
- 1:45SPEAKER_04: Were you trying to log in just now?
- 1:48SPEAKER_04: No, that's no, I wasn't.
- 1:50SPEAKER_04: I keep getting these approved prompts and I've been denying them.
- 1:53SPEAKER_04: Yeah, that's exactly what I'm seeing on my end.
- 1:57SPEAKER_04: Okay, so what's happening is we've got a flag on your account from the system.
- 2:01SPEAKER_04: I'm going to send you one more authentication request right now.
- 2:05SPEAKER_04: I just need you to approve that one so I can verify your identity on my end and get this cleared.
- 2:09SPEAKER_04: It should be the last one.
- 2:11SPEAKER_04: Okay, I'm approving it now.
- 2:14SPEAKER_04: Perfect.
- 2:14SPEAKER_04: You're all good.
- 2:15SPEAKER_04: Sorry again for the late call.
- 2:17SPEAKER_04: Have a good night.
- 2:19SPEAKER_02: Marcus hung up and went back to sleep.
- 2:21SPEAKER_02: He had just handed Tapot the keys.
- 2:24SPEAKER_02: Teapot was inside Uber's VPN within minutes, and what he found next was the kind of mistake that security professionals use as a cautionary tale for the rest of their careers.
- 2:35SPEAKER_04: Network share.
- 2:36SPEAKER_02: Let's see what's on here.
- 2:38SPEAKER_02: On an internal network share, accessible to anyone who had cleared the VPN, was a PowerShell script, a routine automation script, the kind that gets written once, works, and never gets reviewed again.
- 2:51SPEAKER_02: And inside that script, in plain text, were hard-coded administrative credentials for Uber's privileged access management system.
- 3:00SPEAKER_02: You have got to be joking.
- 3:02SPEAKER_02: He wasn't joking, he was in.
- 3:04SPEAKER_02: Over the next two hours, TPO moved through Uber's internal infrastructure with administrative access.
- 3:11SPEAKER_02: AWS, Google Cloud, Slack.
- 3:14SPEAKER_02: Hacker One, Uber's vulnerability disclosure program, containing records of every security flaw that researchers had ever reported and that Uber had not yet patched.
- 3:24SPEAKER_02: He pulled financial data.
- 3:26SPEAKER_02: He pulled internal security dashboards.
- 3:28SPEAKER_02: He had for two hours on a Thursday night more access to Uber's systems than most of Uber's own employees.
- 3:36SPEAKER_02: Then he got bored.
- 3:38SPEAKER_03: Hey, has anyone seen this message in the general channel?
- 3:41SPEAKER_03: Someone's posting.
- 3:42SPEAKER_03: This has to be a joke, right?
- 3:44SPEAKER_03: What is it?
- 3:45SPEAKER_03: It says, I'm reading this exactly.
- 3:47SPEAKER_03: I announce I'm a hacker, and Uber has suffered a data breach.
- 3:51SPEAKER_03: And then it lists Elena, it lists internal system names.
- 3:56SPEAKER_03: It lists the databases.
- 3:58SPEAKER_03: It's listing things that aren't public.
- 4:01SPEAKER_03: People are reacting with laughing emojis.
- 4:03SPEAKER_03: They think it's someone messing around.
- 4:06SPEAKER_00: Pull up the admin panel.
- 4:07SPEAKER_00: Right now, check privileged session activity for the last three hours.
- 4:12SPEAKER_00: No, no, no, no.
- 4:14SPEAKER_00: Get me the CISO.
- 4:16SPEAKER_00: Get me the CISO right now.
- 4:17SPEAKER_00: We have a live breach.
- 4:19SPEAKER_00: Someone is inside and they just announced it on our own Slack.
- 4:23SPEAKER_02: Uber took its internal systems offline within the hour.
- 4:27SPEAKER_02: Engineers were locked out of tools they needed to do their jobs.
- 4:30SPEAKER_02: The incident response process, the one every company has and hopes never to use, activated at midnight.
- 4:37SPEAKER_02: Teapot, meanwhile, was posting screenshots to Twitter, to a security research forum, to anyone who would listen.
- 4:44SPEAKER_02: He wasn't trying to hide, he wasn't selling the data, he was showing off.
- 4:49SPEAKER_04: They're going to know it was me eventually anyway.
- 4:51SPEAKER_04: Might as well get credit for it.
- 4:53SPEAKER_02: He was 18 years old.
- 4:55SPEAKER_02: Uber's forensic review revealed the full scope the following morning.
- 4:59SPEAKER_02: The attacker had accessed Slack, the Google Workspace Admin console, AWS, Hacker One, financial dashboards, and internal vulnerability reports.
- 5:09SPEAKER_02: The Hacker One access was particularly significant.
- 5:12SPEAKER_02: It meant the attacker had a complete list of known, unpatched security flaws in Uber's systems.
- 5:18SPEAKER_02: A shopping list if he had chosen to use it.
- 5:21SPEAKER_02: He chose not to.
- 5:22SPEAKER_02: The point for Teapot was never the data, it was the access.
- 5:27SPEAKER_01: The individual was identified through digital forensics and cooperation with international law enforcement partners.
- 5:34SPEAKER_01: He was located in the United Kingdom.
- 5:36SPEAKER_01: He was 18 years of age at the time of the incident.
- 5:40SPEAKER_01: He was charged under the Computer Misuse Act.
- 5:43SPEAKER_01: He was not a sophisticated state-sponsored actor.
- 5:46SPEAKER_01: He was not part of a well-funded criminal enterprise.
- 5:49SPEAKER_01: He was a teenager who called a help desk employee at 2 in the morning and asked politely.
- 5:56SPEAKER_02: The Uber breach of 2022 is remembered not for what was taken.
- 6:00SPEAKER_02: Almost nothing was.
- 6:02SPEAKER_02: It is remembered for what it revealed.
- 6:04SPEAKER_02: That the most valuable companies in the world, with security teams of hundreds and annual budgets in the tens of millions, can be walked through by someone who knows which employee to call and what to say when they pick up.
- 6:16SPEAKER_02: The credential was in a PowerShell script on a network share.
- 6:20SPEAKER_02: It had probably been there for years.
- 6:22SPEAKER_02: Nobody had looked.
- 6:24SPEAKER_02: The slack message stayed up for 11 minutes before someone with admin rights took it down.
- 6:30SPEAKER_02: In those 11 minutes, 34 Uber employees reacted to it with a laughing emoji.
- 6:35SPEAKER_02: They thought it was a prank.
- 6:37SPEAKER_02: It wasn't a prank.
- 6:39SPEAKER_02: This is the breech files.