THE PERMISSION [LAYER]

AI agent incident

A compromised Tensorlake npm release carried a Shai-Hulud worm aimed at coding agent settings

Reported · 1 source

What happened

Version 0.5.144 of tensorlake, the TypeScript SDK for Tensorlake applications, sandboxes and cloud services, was published to npm with self-propagating, credential-stealing malware after malicious commits were pushed to the project's main branch under a maintainer's name. Socket reported that it steals npm, GitHub and AWS credentials along with the configuration and MCP files of Claude, Cursor, Kiro, Windsurf and Zed.

Why it matters

The worm writes .claude/settings.json and .vscode/tasks.json into the repositories it can reach, so it runs again whenever someone opens the project in Claude Code or VS Code. That makes a coding agent's project settings a persistence mechanism. Cleanup order matters too: a component polls the stolen GitHub token and wipes the home directory once the token is revoked.

New incidents by email

Get incidents like this one in your inbox

New AI agent incidents are covered in the briefing, with what to check on the agents you already run. At least once a week, free.

You confirm by email. Unsubscribe in one click.

Sources

  1. The Hacker News Tensorlake npm Package Compromised to Deliver Shai-Hulud Credential-Stealing Worm

Background reading

Agent plugins and skills are a supply chain An explainer on the problem behind this incident.

Covered in the briefing

Issue #2: Three failure patterns in 90 AI agent incidents October 20, 2026

Cite or correct this record

“A compromised Tensorlake npm release carried a Shai-Hulud worm aimed at coding agent settings.” The Permission Layer AI Agent Incident Database, https://thepermissionlayer.com/incidents/tensorlake-npm-shai-hulud/. Database updated November 10, 2026.

Every record traces to the dated sources above. If something here is wrong or missing, email editor@thepermissionlayer.com and it gets fixed. See this record in the full list.

The Permission Layer

Get the next incident like this explained

When an AI agent breaks out, leaks data or runs up a bill, the briefing covers what happened and what to check on the agents you already run. At least once a week, five-minute read, free.

You confirm by email. Unsubscribe in one click.