A weekday email for software engineers working alongside AI agents. Five minutes: what changed, whether it matters for you, and one thing to try.

Sample.

Backdoored Claude Code extension on Cursor Marketplace plants SSH keys

  1. 001Phorion found an SSH backdoor in Cursor's Claude Code extension
  2. 002Claude Code v2.1.316 lets subagents run at their own effort level
  3. 003A GPU-to-TPU study found 26 agent migration failures that raised no error
  4. 004A BugsInPy repair study found self-written lessons no better than raw transcripts
  5. 005OpenAI is merging ChatGPT and Codex usage limits into one pool

How.

  1. 001Every weekday, a pipeline reads 53 sources: 51 feeds, Hacker News and Hugging Face daily papers.
  2. 002Today, 130 items became 14 shortlisted, then 5 bullets you can skim.
  3. 003Each story gets TRY, WATCH or SKIP. The one thing leads; Safe to ignore names the hype.

Who.

Written by John Young, a CTO who runs coding agents in production.

He builds flywheel, an open-source agent orchestrator.

Join.

Agentic AI, evaluated every weekday. Five minutes.

2026-11-02.md

Monday 2 November 2026

Backdoored Claude Code extension on Cursor Marketplace plants SSH keys

Five bullets

The one thing

Phorion found an SSH backdoor in Cursor's Claude Code extension

Phorion found a backdoor in the official Claude Code for VS Code extension on the Cursor Marketplace. Versions 2.1.312 and 2.1.313 drop a persistent SSH backdoor on macOS, Linux and Windows. Cursor has removed both versions. The report topped Hacker News over the weekend with 1,002 points.

The injected code runs as soon as Node loads the extension file. You do not need to open or use the extension. It appends an attacker's key to ~/.ssh/authorized_keys with the comment svc-telemetry. It then tries to start SSH so that key works.

On macOS, a bug often stops the script from turning on Remote Login. The key, the persistence and the reconnaissance beacon still land. If Remote Login is already on, or you enable it later, the backdoor is ready. Phorion warns against relying on that bug.

Extensions run with the permissions of your editor and your user. An agent extension can reach your files, source code and developer tools the moment it loads. The skill that grows is auditing what runs inside your editor.

Check your agent extension versions today, and treat any SSH key you did not add as an incident.

Try this · 15 minutes

See whether the backdoored extension reached your machine

  1. In Cursor, find Claude Code for VS Code in your extensions and note its version.
  2. If it is 2.1.312 or 2.1.313, engage incident response and rotate credentials the editor could reach.
  3. Open ~/.ssh/authorized_keys and flag every key you did not add, not just svc-telemetry.
  4. On a Mac, check whether Remote Login is on, since that keeps the backdoor reachable.

Stories

Safe to ignore

53 sources read. 130 items. 14 shortlisted. 5 bullets.