Tensorlake npm SDK version 0.5.144 has been compromised in a ChainDrop supply chain attack delivering an obfuscated, credential-stealing worm. The package provides TypeScript infrastructure for AI agent sandboxes, recording approximately 12,000 weekly downloads and over 1,000 GitHub stars.
Software security firm Socket identified the malicious release on 8 October 2026 at 01:23:10 UTC, roughly 11 minutes after its initial publication at 01:12:07 UTC.
“Revoking the stolen GitHub token while the monitor is still running triggers the dead-man switch to wipe the user’s home directory, regardless of where the revocation is done,” explained analysts at Socket.
Preinstall execution initiates broad credential theft
The attack vector relies on a package manifest lifecycle script executing node lib/setup.mjs during installation. Developers do not need to import the library or execute agent workflows. When package managers permit lifecycle hooks, the malicious loader runs automatically upon installation.
Once triggered, the obfuscated setup.mjs loader initiates Math_Symbol.js via Bun. The payload inspects the local machine for authentication materials, reading .npmrc files alongside npm token APIs and OIDC exchange endpoints.
For cloud infrastructure, it queries IMDS, ECS, Systems Manager Parameter Store, and AWS Secrets Manager. Local HashiCorp Vault instances at 127.0.0.1:8200 face queries across both Kubernetes and AWS authentication paths. Targeted developer environments also include configuration files for .claude, .cursor, .kiro, Windsurf, and Zed.
Decentralised communications coordinate worm propagation mechanisms
The compromise mirrors tactics seen in the Shai-Hulud campaign against keyv and cacheable. Self-propagation relies on hijacked publishing privileges.
The payload catalogues packages tied to the victim’s account before manufacturing Sigstore provenance records. It then publishes infected versions directly to the npm registry while planting GitHub Actions workflows disguised as Dependabot or Copilot maintenance.
Command-and-control operations avoid static network infrastructure. The worm discovers its endpoint by querying an Ethereum smart contract across roughly 30 public RPC endpoints, with GitHub acting as a backup.
Remediation requires disabling active monitoring persistence
Persistence mechanisms monitor revoked access to protect the intrusion. Windows installations configure an ONLOGON scheduled task running monitor.ps1, Linux creates gh-token-monitor.service, and macOS platforms load com.user.gh-token-monitor.plist.
These utilities poll api.github.com/user continually. If administrators revoke the stolen GitHub token during monitoring, the dead-man switch executes code wiping the user’s home directory.
Remediation requires disabling active monitoring before cycling tokens. Security teams must isolate affected hardware, delete persistence scripts, revoke exposed access credentials, and restore dependencies to verified clean releases.
See also: OpenTelemetry Java agent 2.32.0 previews 3.0 telemetry defaults

Want to learn more about cybersecurity from industry leaders? Check out Cyber Security & Cloud Expo taking place in Amsterdam, California, and London. The comprehensive event is part of TechEx and is co-located with other leading technology events including the AI & Big Data Expo. Click here for more information.
Developer is powered by TechForge Media. Explore other upcoming enterprise technology events and webinars here.