Which versions of tensorflowjs are malicious?

The following npm versions of tensorflowjs are flagged malicious: 0.6.8, 0.6.9, 0.7.0. Treat any of these as compromised.

How do I remediate tensorflowjs if I installed it?

Remove tensorflowjs 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.

I already installed tensorflowjs — how do I know if it already compromised me?

If tensorflowjs 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.

Is tensorflowjs part of a known attack campaign?

Yes — tensorflowjs is associated with the RLMA-2025-04703, RLUA-2026-01612 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tensorflowjs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tensorflowjs (3 malicious versions).

Malicious package

tensorflowjsnpm

Advisory published Aug 12, 2025Updated Mar 19, 2026

tensorflowjs is a confirmed malicious npm package (MAL-2025-6829) that executes malicious code on install (malicious versions 0.6.8, 0.6.9, 0.7.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tensorflowjs (npm)

MAL-2025-6829

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tensorflowjs

What this malware does

Package is malicious due to code obfuscation, arbitrary command execution via child_process.spawn, and suspicious postinstall script.

Malicious versions

3 flagged

0.6.80.6.90.7.0

Indicators of compromise (SHA-256)

c0e2d4e742598129f3703c03a304e085e99295fbc5169b3e16902dd3dc33692a

54ed4038fbe5eee9ed09656abbbf1fb00e7562462d99b9ff872c779b2cd8d53e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tensorflowjs (3 malicious versions).
If you installed it — respond
Remove tensorflowjs 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.
Did it already run?
If tensorflowjs 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. tensorflowjs on npm has been identified as a malicious package (versions 0.6.8, 0.6.9, 0.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04703RLUA-2026-01612

References

Credits

ReversingLabs · finder
SafeDep · finder

Detect & block this

O3 blocks tensorflowjs-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database