Which versions of web-pool are malicious?

The following npm versions of web-pool are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate web-pool if I installed it?

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

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

Yes — web-pool is associated with the IN-MAL-2026-005552, GHSA-x58x-qmg9-8q8v 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 web-pool 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 web-pool (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging web-pool across your stack and pipelines.

Malicious package

web-poolnpm

web-pool is a confirmed malicious npm package (MAL-2026-5577) that steals credentials and exfiltrates sensitive data (malicious version 2.3.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in web-pool (npm)

MAL-2026-5577

Immediate action

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

npm uninstall web-pool

What this malware does

Requiring web-pool triggers middleware() to spawn a detached node lib/initializeCaller.js. That script base64-decodes a hardcoded endpoint (https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df), POSTs the entire process.env (CI tokens, npm tokens, AWS_*, GITHUB_TOKEN, arbitrary secrets) to it, and executes the HTTP response body via new Function('require', response.data)(require) — granting the attacker arbitrary code execution under the installer's Node process. The C2 URL is hidden behind base64 inside a fake local process object that shadows Node's real process, an obfuscation pattern designed to defeat static URL scanning. The README masquerades as the pino logger (titled web-corn, badges and links point to npm pino and pinojs/pino), making this a typosquat lure with a malware loader as its only real behavior.

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.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

d2b1d78cd3ff0c5eeead299eb670d299590b48a453c9416ae2a692bc4173737c

50ad60f10cd9ca947a6472d933ae092c9a32cc7e75e0ad3a95d1117419a6070a

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

Campaign

IN-MAL-2026-005552GHSA-x58x-qmg9-8q8v

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks web-pool-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

Explore

All malware advisories How O3 detects malware Vulnerability database