Which versions of vuln-package are malicious?

The following npm versions of vuln-package are flagged malicious: 99.9.9, 99.9.10, 99.9.11, 99.9.14. Treat any of these as compromised.

How do I remediate vuln-package if I installed it?

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

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

Yes — vuln-package is associated with the IN-MAL-2026-009772, IN-MAL-2026-009770, IN-MAL-2026-009769, IN-MAL-2026-009771 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 vuln-package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vuln-package (4 malicious versions).

Malicious package

vuln-packagenpm

Advisory published Jul 12, 2026Updated Jul 12, 2026

vuln-package is a confirmed malicious npm package (MAL-2026-10212) that steals credentials and exfiltrates sensitive data (malicious versions 99.9.9, 99.9.10, 99.9.11…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vuln-package (npm)

MAL-2026-10212

Immediate action

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

npm uninstall vuln-package

What this malware does

On npm install, the package's preinstall script triggers a DNS lookup to a unique subdomain of oast.fun (fabekzbnjtufpffkzzmvjvi5eafhny3ok.oast.fun), an out-of-band interaction service, confirming code execution on the installer's machine to a third-party collector. A sibling file indexCopy.js collects host identifiers (os.userInfo().username, os.hostname(), process.cwd(), and process.env references) and issues an https.request POST to a hardcoded webhook.site endpoint (https://webhook.site/cde465c1-3853-40ea-880c-fdca6fe508cc). The combination of an OOB DNS beacon at install time and a staged HTTPS exfiltration payload targeting installer host identifiers is characteristic of a supply-chain reconnaissance/exfiltration attack rather than any legitimate package behavior.

Malicious versions

4 flagged

99.9.999.9.1099.9.1199.9.14

Indicators of compromise (SHA-256)

06af9ab71bf0ad37fd3f56b2f80f4eb81eed1cac671e59e63d2c2c09570d6df7

a8bd105bf3b12062f312b41f2a1eead5e8481f8d3749fc78bc79ed8675c11394

cebe00f077147fe571b1fcee6ec9b2b057bcf609686e92a14ad060145b2fce3d

23c4656f79e1b726cb17dfec791f278af6b9aa41b5c6215c8a0e8c8d8179feb7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for vuln-package (4 malicious versions).
If you installed it — respond
vuln-package 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 vuln-package 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. vuln-package on npm has been identified as a malicious package (versions 99.9.9, 99.9.10, 99.9.11, 99.9.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009772IN-MAL-2026-009770IN-MAL-2026-009769IN-MAL-2026-009771

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vuln-package-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