Which versions of zuper-stream are malicious?

The following npm versions of zuper-stream are flagged malicious: 2.0.9. Treat any of these as compromised.

How do I remediate zuper-stream if I installed it?

zuper-stream 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 zuper-stream — how do I know if it already compromised me?

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

Yes — zuper-stream is associated with the GHSA-f7w4-78r2-578g 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 zuper-stream 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 zuper-stream (version 2.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zuper-stream across your stack and pipelines.

Malicious package

zuper-streamnpm

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

MAL-2025-190862

Immediate action

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

npm uninstall zuper-stream

What this malware does

The package zuper-stream 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

2.0.9

Indicators of compromise (SHA-256)

123b2f89234617b4d3a0968f699b3cd51545e8d268e5fc793b393f71645c4784

74a0f9381a4c5030be93c471e6489c9de683e8c9e2ab2872d8db32583c4fc35e

bae97003ddbb4e58f122341cfba6d281dd7d4df0d2759d8ab4c6137c36b50fb2

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 zuper-stream (version 2.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zuper-stream across your stack and pipelines.
If you installed it — respond
zuper-stream 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 zuper-stream 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 zuper-stream 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. zuper-stream on npm has been identified as a malicious package (version 2.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f7w4-78r2-578g

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zuper-stream-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