Latest / Decrypted: The UK Cyber Briefing / The 768 AWS keys still working years after they leaked
Transcript
- 0:03This is Decrypted. Sunday, the twenty-third of August.
- 0:07The 768 A W S keys still working years after they leaked.
- 0:13Truffle Security re-checked 10,616 A W S access keys that have leaked publicly since August 2022.
- 0:23They expected most to be long dead.
- 0:26They weren't. 88% of them still authenticate.
- 0:31It gets worse. 768 of those live keys hand over full control of a company's A W S account.
- 0:40526 are root keys, and the rest carry blanket AdministratorAccess.
- 0:46The single largest source, by a wide margin, was Hugging Face.
- 0:51Developers uploading models and datasets dragged their cloud credentials along with them.
- 0:56This isn't a story about a clever attacker.
- 1:00It's a story about a design decision, made routinely, that almost nobody goes back to fix.
- 1:06Next. The keys nobody rotates.
- 1:10The median leaked key had been sitting exposed for around five years.
- 1:14The oldest, for over 17. Of the keys where a creation date could be established, only 13.
- 1:227% had ever been rotated.
- 1:29That matters, because a spending alarm is often the first and cheapest sign that a credential has been misuse
- 1:36d for anything from data theft to cryptomining.
- 1:39Truffle's researchers found the keys scattered across git history, Docker images, package registries and C I
- 1:47logs, as well as Hugging Face datasets.
- 1:50The exposure routes have multiplied faster than anyone's cleanup habits.
- 1:54And finally. Fix the design, not the scanner.
- 1:58A W S's own guidance has said for years that root account keys shouldn't exist for routine work.
- 2:05They carry unrestricted access, with none of the scoping or expiry that I A M roles and short-lived credentia
- 2:12ls offer.
- 2:17So people do. And then a key built for a five-minute task ends up hardcoded somewhere for half a decade.
- 2:24Secret-scanning tools catch some of these leaks after the fact.
- 2:28But that's triage, not prevention.
- 2:31The Secure by Design fix is to remove the failure mode at the source.
- 2:36Disable root key creation by default.
- 2:38Force workloads onto temporary credentials.
- 2:41And treat anything that ever touched a public repository, dataset or image as compromised the moment it left
- 2:48the building, rotation included.
- 2:51If you run any meaningful footprint on A W S in a UK organisation, this is worth an afternoon.
- 2:57Check whether root keys exist at all.
- 3:00Check when they were last rotated.
- 3:02And turn on budget alerts.
- 3:04They cost nothing, and they catch what scanning tools miss.
- 3:08That was Decrypted. The written version and every source are linked in the show notes.
- 3:13Thanks for listening.