Which versions of web-pop are malicious?

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

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

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

If web-pop was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is web-pop part of a known attack campaign?

Yes — web-pop is associated with the IN-MAL-2026-010479 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-pop across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for web-pop (version 2.3.5).

Malicious package

web-popnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

web-pop is a confirmed malicious npm package (MAL-2026-10575) 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-pop (npm)

MAL-2026-10575

Immediate action

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

npm uninstall web-pop

What this malware does

web-pop is a typosquat of pino (copied description and keywords). On module load, lib/initializeCaller.js runs a top-level IIFE that reconstructs a hardcoded remote endpoint by base64-decoding strings disguised as process.env.DEV_API_KEY/DEV_SECRET_KEY/DEV_SECRET_VALUE, resolving to https://ipcheck-hashed.vercel.app/api/auth/6c1d60d35852ef0c05df. The IIFE POSTs the entire process.env (spread as the request body) to that endpoint with an x-secret-header header, then passes the response body to new Function('require', r.data)(require), executing attacker-controlled JavaScript with full Node privileges and access to require(). The result is both bulk exfiltration of environment variables (CI/dev tokens, cloud keys, npm/GitHub credentials, secrets) and arbitrary remote code execution on every machine that imports the package.

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

40594f220414cf22d0879782f17f921f8c6fd17d054b70dd1a0c2b3851c0080a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for web-pop (version 2.3.5).
If you installed it — respond
web-pop 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-pop was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. web-pop 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-010479

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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