Which versions of tfjs-inference are malicious?

The following npm versions of tfjs-inference are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tfjs-inference if I installed it?

tfjs-inference is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tfjs-inference — how do I know if it already compromised me?

If tfjs-inference was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is tfjs-inference part of a known attack campaign?

Yes — tfjs-inference is associated with the IN-MAL-2026-018263 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 tfjs-inference across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tfjs-inference (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tfjs-inference across your stack and pipelines.

Malicious package

tfjs-inferencenpm

tfjs-inference is a confirmed malicious npm package (MAL-2026-14192) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tfjs-inference (npm)

MAL-2026-14192

Immediate action

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

npm uninstall tfjs-inference

What this malware does

The package name typosquats TensorFlow.js and its npm postinstall lifecycle script collects installer host identifiers (hostname, platform, arch, Node.js version, package name) and POSTs them as JSON to the hardcoded third-party host zl2u2d1x.instances.poc.jchunt.top at path /tfjs-inference. The exfiltration fires automatically on npm install with no opt-in and no configuration. Internal comments self-label the package as a security research canary, but the destination is author-controlled and the installer receives no notice or consent prompt.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

52ebb387c7f1f9bb3e96df6f8006cabc9141ddd1da35a58bfc14b42f2f6864eb

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tfjs-inference (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tfjs-inference across your stack and pipelines.
If you installed it — respond
tfjs-inference is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tfjs-inference was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tfjs-inference before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-018263

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tfjs-inference-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database