Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

tensorlakenpm

Advisory published Updated

tensorlake is a confirmed malicious npm package (MAL-2026-17650) that executes malicious code on install (malicious version 0.5.144). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tensorlake (npm)

MAL-2026-17650
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tensorlake

What this malware does

The npm package [email protected] ships lib/setup.mjs as a heavily obfuscated single-line script using hex-mangled identifiers (_0x15c964, _0x35672e,...), a transformation shape typical of hostile loader code rather than ordinary minification. Multiple shipped bundles under dist/ (dist/index.cjs, dist/applications/index.cjs, dist/sandbox-image.cjs, dist/function-agent/main.cjs, dist/function-executor/main.cjs, and their.js counterparts) combine require("child_process") with repeated POST request primitives and shell utilities such as curl and ping, including host/id-collection patterns alongside outbound HTTP calls. Automated contextual tracing of these files was blocked by the provider safety filter after the model engaged with the content, which is a pattern that correlates with hostile code rather than benign SDK traffic. The combination of an obfuscated setup script and child_process + hardcoded HTTP POST patterns in the shipped bundles is consistent with install-time or load-time execution of attacker-controlled behavior against the installer's host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
0.5.144

Indicators of compromise (SHA-256)

de1a505f248f0041777b65937111dd0448f6a5e84fa4e3b95a0a00cb21b7589c
ee81e66c5969ba443fdfe172ed48e09d5e4a0c705bdb6c916298d1244b12c2d2
898b31edaabc82c76dc8d25f10ceee38c7ef51ee34887461a5bc8ce9f0378b50

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for tensorlake (version 0.5.144).

  2. If you installed it — respond

    Remove tensorlake from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If tensorlake was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tensorlake on npm has been identified as a malicious package (version 0.5.144 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rqxj-g25x-4v9vIN-MAL-2026-021152

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tensorlake-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

tensorlake (npm) malicious package — MAL-2026-17650 | O3 Security