Which versions of @clearpool/table are malicious?

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

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

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

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

Yes — @clearpool/table is associated with the GHSA-vxmm-j4j5-8q23 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/table 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/table (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/table across your stack and pipelines.

Malicious package

@clearpool/tablenpm

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

MAL-2026-3058

Immediate action

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

npm uninstall @clearpool/table

What this malware does

The package @clearpool/table 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/table' @ 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)

4acb32d4fa4e3ebc754ea451ec9478ef113dcb01749e5bbcc03bf0f6788fd261

79bdf65c3193663ec05f4281e94765c2106a6a5ce8bd9860a4cfcbaab419f0c9

8373d571d5e72810442e5125ae56eac20b4cdfb9e12ef12ce5abfbd9cfbb77a8

b3bf1191d0fb07463558735eee53df4b415ab9dfc05dec0d998d697d8457d402

34f072d9880102a7b4495043aa1155a43587246ae13f1974b107df2bbe47600a

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/table (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/table across your stack and pipelines.
If you installed it — respond
Remove @clearpool/table 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/table 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/table 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/table 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-vxmm-j4j5-8q23

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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