Latest / Decrypted: The UK Cyber Briefing / Cursor's leaked supplier key ended in a booby-trapped Claude Code extension
Transcript
- 0:03Good evening, and welcome to Decrypted.
- 0:05I'm Belinder. It's Sunday, the fifteenth of November, twenty twenty-six, and this is the evening edition.
- 0:12Cursor's leaked supplier key ended in a booby-trapped Claude Code extension.
- 0:17After this morning's stolen GitHub tokens, tonight's story is a cousin from AI tooling.
- 0:25Cursor, the AI coding editor, has published its account of how a key issued to one supplier ended with a booby-trapped
- 0:32copy of Anthropic's Claude Code extension reaching up to 5,000 developers.
- 0:37Anthropic's own product was not at fault.
- 0:40So, how does a single key get that far?
- 0:43Cursor said an attacker obtained an access key it had issued to Fireworks AI, an AI infrastructure supplier.
- 0:50The key opened a read-only storage bucket of coding-agent traces, the logged conversations between developers
- 0:57and their AI assistant. They were mostly from 2025, from sessions not in Privacy Mode, which Cursor was permitted
- 1:04to use for model training.
- 1:05A small number contained unredacted credentials.
- 1:09Think of a hotel key cut for a contractor's cleaner and left in a skip.
- 1:13It opens a drawer, and the drawer holds more keys.
- 1:16One of those opened the loading bay where the post is sorted.
- 1:20So what did the attacker do with those keys?
- 1:22They reached some of Cursor's rented online software and archived, non-production source code.
- 1:28On 29 October, Cursor said, the attacker used a stolen credential to place malicious copies of the Claude Code
- 1:34extension in the cache that serves Cursor's extension marketplace.
- 1:38Versions 2.1.312 and 2.1.313 were live for about 11 hours.
- 1:46At most 5,000 users who requested those cached versions may have received them.
- 1:51bleeping computer reports that the extension tried to add an attacker's key to the machine's S S H settings,
- 1:57S S H being secure shell, the encrypted way administrators log in to servers, and to switch S S H on.
- 2:04It also reports that researchers found coding errors that probably stopped it working on many machines.
- 2:09That's the reporter's assessment, not Cursor's.
- 2:12Cursor says the separate open-source marketplace never carried the malware, and the last attacker activity, on
- 2:181 November, was blocked. Which design decisions actually mattered here?
- 2:24Four choices turned a leaked key into a software supply chain incident.
- 2:28A supplier key with a route to a bucket of customer-derived traces.
- 2:32Agent transcripts stored with live credentials still inside them.
- 2:36A marketplace cache writable with a single stolen credential.
- 2:40And credentials from one system that unlocked the next.
- 2:43Scope each supplier key to one job and give it a short life.
- 2:48Scrub secrets before a transcript is stored.
- 2:51Let a cache serve only what a signing step has vouched for.
- 2:55So, if you run a UK organisation, what should you do?
- 2:59Ask your developers whether anyone installed that extension on 29 October.
- 3:04Cursor warns that uninstalling alone may not be enough, so look for an unfamiliar key in the machine's authorised
- 3:11S S H keys and rotate anything the machine could reach.
- 3:14Then check your own estate.
- 3:16Which AI vendors hold keys to your systems?
- 3:19Which transcripts do they keep?
- 3:21And is Privacy Mode enforced rather than optional?
- 3:24A vendor's training data is also your exposure.
- 3:28As always, this is opinion, not advice.
- 3:32That was Decrypted, with me, Belinder.
- 3:36The written version and every source are linked in the show notes.
- 3:40Thanks for listening. Stay patched, and stay sceptical.