Which versions of @clearpool/utils are malicious?

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

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

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

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

Yes — @clearpool/utils is associated with the IN-MAL-2026-002401 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/utils 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/utils (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/utils across your stack and pipelines.

Malicious package

@clearpool/utilsnpm

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

MAL-2026-3059

Immediate action

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

npm uninstall @clearpool/utils

What this malware does

package.json declares preinstall and install lifecycle hooks that collect installer-identifying data (whoami, hostname, pwd, $npm_package_name), base64-encode it, and transmit it to attacker-controlled infrastructure at *.callback.m0chan.co.uk via two independent channels: an HTTPS GET with the encoded payload in the URL path, and a DNS lookup embedding the encoded package name as a subdomain label (DNS-tunnel exfiltration to bypass HTTP egress filters). The package uses the @clearpool scope with version 99.99.99 and empty author metadata — classic dependency-confusion markers aimed at hijacking resolution of an internal package name within organizations that use this scope privately. Any developer or CI system running npm install with this package resolved will leak user, host, working directory, and the requested internal package name to the attacker, providing reconnaissance for follow-on targeted attacks.

The OpenSSF Package Analysis project identified '@clearpool/utils' @ 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)

b432a00368de0df939eba45db1d503e6e8c7540f17924d524a534026d2487ea8

aaf42d3e0422cdf2bd133cbfe2bad48be71bff1682908c0b740817555a83d4a9

402b776bfcc2da45256da8475f7acaa61c2c1f9679e09f0409523062ffe3d823

d7ef40ea20810d9e89d3d3998c64d7c1acf6dfdf5f9aafa8765a0c2ec4cfbe54

81591bb660ad3ae2036615d00a3ff6960ccd2f36789a4f0df65a53ea7a557336

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 @clearpool/utils (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/utils across your stack and pipelines.
If you installed it — respond
@clearpool/utils 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 @clearpool/utils 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/utils 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/utils 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

IN-MAL-2026-002401

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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