Tensorlake npm Package Compromised to Deliver Shai-Hulud Credential-Stealing Worm
Compromised tensorlake npm 0.5.144 delivered the Shai-Hulud worm to steal secrets and spread to other packages.
Socket and StepSecurity reported that tensorlake npm version 0.5.144 was compromised in the ChainDrop/Shai-Hulud campaign and later removed from the registry. A preinstall hook launched an obfuscated Bun loader that runs a self-propagating credential worm, Math_Symbol.js. The malware steals npm, GitHub, AWS, Vault, Kubernetes, SSH, cryptocurrency, and AI-assistant secrets, drops HackBrowserData, persists, and can execute remote code. It republishes infected packages, resolves C2 iseekaigogo.com through an Ethereum contract, stages data in public GitHub repositories, and may run a destructive PowerShell handler if a stolen GitHub token is revoked.
- Version 0.5.144, now removed from npm, ran a preinstall hook into a Bun worm.
- It harvests cloud, CI, Kubernetes, Vault, SSH, wallet, and AI coding-tool secrets.
- The worm republishes packages under the victim identity and can add GitHub Actions.
- C2 iseekaigogo.com is resolved via an Ethereum contract, with GitHub as fallback.
- A PowerShell monitor may run destructive code if the stolen GitHub token is revoked.
Indicators of compromiseauto-extracted · verify before use · export allAll →
| Type | Indicator | Context |
|---|---|---|
| domain | iseekaigogo.com | contract to resolve its command-and-control (C2) endpoint ("iseekaigogo[.]com"), with GitHub acting as a fallback mechanism to stage th |
Full article582 words · extracted from thehackernews.com · click to collapse
Ravie LakshmananOct 08, 2026Artificial Intelligence / Cloud Security
The npm package known as "tensorlake," a TypeScript software development kit (SDK) for Tensorlake applications, sandboxes, and cloud services, was compromised as part of a ChainDrop / Shai-Hulud supply chain attack.
The malicious version 0.5.144 "contains obfuscated malware that harvests credentials, exfiltrates secrets, establishes persistence, and executes remotely supplied code," Socket said. Version 0.5.144 is no longer available for download from the npm package registry.
An analysis of the compromised release shows that it contains a preinstall hook designed to launch a JavaScript file ("package/lib/setup.mjs"), an obfuscated loader that launches the main credential-stealing and self-propagating worm ("package/lib/Math_Symbol.js") using the Bun runtime.
The stealer malware is designed to harvest credentials across local files, CI environments, Kubernetes, and Vault sources. It also drops the HackBrowserData binary, exfiltrates the collected data, establishes persistence on the host, and facilitates the execution of remotely-supplied code.
"That combination extends the risk beyond a single stolen API key," Socket said. "Any secrets accessible to the executing process may be exposed, and persistence can retain attacker access after the affected dependency is removed."
The types of data stolen by the malware are below -
- npm tokens
- GitHub tokens
- Amazon Web Services (AWS) credentials and secrets
- HashiCorp Vault
- Kubernetes credentials
- SSH keys
- .env files
- Cryptocurrency wallets
- Messaging app data
- Configuration and MCP files associated with Anthropic Claude, Cursor, Kiro, Windsurf, and Zed
"To propagate, the worm enumerates packages associated with the victim's publishing identity, builds Sigstore provenance, and republishes compromised versions," Socket explained. "Strings referencing a fake Copilot/Dependabot workflow suggest it also plants GitHub Actions workflows."
The malware also makes use of an Ethereum contract to resolve its command-and-control (C2) endpoint ("iseekaigogo[.]com"), with GitHub acting as a fallback mechanism to stage the encrypted stolen data in a public repository with the description "Shai-Hulud: Here We Go Again."
In addition, there exists a "hostage token" component that uses a PowerShell monitor to repeatedly poll "api.github.com/user" using the stolen GitHub token to check if the token is valid. Should the victim take steps to revoke the token, the monitor proceeds to execute an attacker-supplied handler through the "Invoke-Expression" cmdlet to execute PowerShell code designed to likely trigger a destructive routine – a tactic observed in earlier Shai-Hulud waves.
According to StepSecurity, the malicious files were pushed to the main branch of tensorlakeai/tensorlake under a maintainer's name, after which the package was released from that same repository. The first rogue commit took place on October 7, 2026, at 01:20 a.m. UTC. A day later, the repository's release workflow published 0.5.144 to npm
"The malware also writes .claude/settings.json and .vscode/tasks.json files into repos it can reach, so it runs again when someone opens the project in Claude Code or VS Code," StepSecurity's Ashish Kurmi said.
ChainDrop was first documented in early August 2026 in connection with the compromise of hundreds of npm packages, including Keyv and Cacheable, that were found to contain a Mini Shai-Hulud variant with a self-propagating credential-stealing worm delivered through an obfuscated Bun-based JavaScript payload.
The development extends the supply chain attack to artificial intelligence (AI) agent infrastructure, once again highlighting how threat actors are increasingly targeting AI tools and services to extract valuable data from enterprises. Users who have installed the malicious version are advised to remove it immediately and rotate their credentials.
Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.