What happened to tensorlake?
In its analysis, StepSecurity says malicious files were pushed directly to the main branch of tensorlakeai/tensorlake under a maintainer's name on October 7, 2026, and tensorlake 0.5.144 was released to npm the next day with a valid provenance attestation. A GitHub advisory lists it as malware.
A preinstall hook fetches Bun and runs a payload that steals GitHub and npm tokens, cloud keys, Kubernetes and Vault secrets, SSH keys, browser logins and AI tool configs. It spreads through npm republishing and by committing .claude/settings.json and .vscode/tasks.json. It also installs a gh-token-monitor service that runs rm -rf ~/ if the stolen GitHub token is revoked within 24 hours, so the cleanup order matters.
Which tensorlake versions are affected?
tensorlake0.5.144 on npm. Pin 0.5.143.- Anyone who pulled tensorlakeai/tensorlake
mainafter October 7, 2026 and rannpm installintypescript/. - GitHub accounts where the worm committed
.claudeor.vscodefiles or created public repositories described "Shai-Hulud: Here We Go Again".
How to check if you're affected
- Run
npm ls tensorlakeand search lockfiles for 0.5.144. - Look for
~/.config/gh-token-monitor/and~/.local/bin/gh-token-monitor.sh, or the equivalent launchd or scheduled task. - Check your GitHub account for unexpected public repositories and commits titled "chore: update dependencies" that add
.claudeor.vscodefiles. - Check network logs for
iseekaigogo.com.
What to do now
- Don't revoke any GitHub token until the monitor service is removed.
- Remove the monitor: on Linux run
systemctl --user disable --now gh-token-monitor.serviceand delete its files; on macOS boot out thecom.user.gh-token-monitorlaunch agent; on Windows delete the monitor scheduled task. - Then revoke the GitHub token and rotate npm, cloud, SSH, Kubernetes, Vault,
.env, AI tool and browser credentials, ideally from another computer. - Pin 0.5.143, delete
node_modules, runnpm cache clean --force, and wipe and reinstall if you can't confirm the machine is clean.
Why cleanup order matters here
Most incident playbooks start with revoking stolen tokens. This payload turns that habit against the victim: it watches whether its token still works and deletes the home directory if it doesn't. Read the analysis of a specific payload before acting, remove persistence first, and keep backups of developer machines current so a destructive payload costs time, not work.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify finds every repository and container image that pulls an affected package version and runs the upgrade as one campaign, scoped by CVE, package, repo or team, with owners, Slack escalation and SLA tracking. Your developers approve every merge.
Nullify can't tell you whether the payload ran on a given machine or runner. Use the checks above for that, then fix the dependency everywhere it appears.
Frequently Asked Questions
Which tensorlake version is malicious?
tensorlake 0.5.144 on npm, released October 8, 2026 from malicious commits pushed the day before. Pin 0.5.143. GitHub's advisory GHSA-rqxj-g25x-4v9v lists no patched version, so stay on 0.5.143 for now.
Why shouldn't I revoke my GitHub token right away?
The payload installs a gh-token-monitor service that deletes your home directory if the stolen token is revoked within 24 hours. Remove the monitor service first, then revoke the token and rotate everything else.
How does the tensorlake worm spread?
StepSecurity says it republishes npm packages the victim can publish and commits .claude/settings.json and .vscode/tasks.json files to the victim's repositories, so other developers who open those projects can run it too.
Update Log
- Nov 17, 2026: page published from the primary sources linked above.