Which versions of tensorzero-node are malicious?

The following npm versions of tensorzero-node are flagged malicious: 1000.0.100. Treat any of these as compromised.

How do I remediate tensorzero-node if I installed it?

Remove tensorzero-node 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 tensorzero-node — how do I know if it already compromised me?

If tensorzero-node 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 tensorzero-node part of a known attack campaign?

Yes — tensorzero-node is associated with the GHSA-g3vv-q9j6-pw39 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 tensorzero-node 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 tensorzero-node (version 1000.0.100). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tensorzero-node across your stack and pipelines.

Malicious package

tensorzero-nodenpm

Malicious code in tensorzero-node (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2684

Immediate action

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

npm uninstall tensorzero-node

What this malware does

The package tensorzero-node was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'tensorzero-node' @ 1000.0.100 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1000.0.100

Indicators of compromise (SHA-256)

513e45c6bbcfc01472644de1bc7840f2c82663c0a1a96e36ee94a3feeadd07a7

d152b28b710406f0a3eede30abb61ae9698eca9fc72a46a2b6b59eaf23876dcc

72b66b5b70cb431f4427417df356e75438bfa64c106e3c1762f27c257246e445

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tensorzero-node (version 1000.0.100). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tensorzero-node across your stack and pipelines.
If you installed it — respond
Remove tensorzero-node 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 tensorzero-node 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 tensorzero-node 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. tensorzero-node on npm has been identified as a malicious package (version 1000.0.100 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g3vv-q9j6-pw39

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks tensorzero-node-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