Which versions of @clearpool/streaming are malicious?

The following npm versions of @clearpool/streaming are flagged malicious: 9.9.9, 99.99.99, 100.0.0. Treat any of these as compromised.

How do I remediate @clearpool/streaming if I installed it?

Remove @clearpool/streaming 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 @clearpool/streaming — how do I know if it already compromised me?

If @clearpool/streaming 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 @clearpool/streaming part of a known attack campaign?

Yes — @clearpool/streaming is associated with the GHSA-m2h2-p59r-798j 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 @clearpool/streaming 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 @clearpool/streaming (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @clearpool/streaming across your stack and pipelines.

Malicious package

@clearpool/streamingnpm

Malicious code in @clearpool/streaming (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3057

Immediate action

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

npm uninstall @clearpool/streaming

What this malware does

The package @clearpool/streaming 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 '@clearpool/streaming' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

9.9.999.99.99100.0.0

Indicators of compromise (SHA-256)

4d4bd8a2d8815f1838f5205624a1dbcd14ac5cc881d94192892c6da4b5cc4b9e

febaceb862fd80f68bdcefbbed2667f056ba0b09cc0607d92962dd0d1c2a8b5d

28894f78e1846e099161df5f8235bc00a5826b97ca218b2856e43dcc41916e54

81e7c0e39e35642113aa70e5ff90d5757939a97c0aeb1d0841f47fc3ff5af4e2

55f28bcf1127ae264990c5322ea14ea6e37aae259923c23e3c6731715059ed8d

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

Campaign

GHSA-m2h2-p59r-798j

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @clearpool/streaming-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