Which versions of 24712-pl5006 are malicious?

The following npm versions of 24712-pl5006 are flagged malicious: 0.0.2, 0.0.4. Treat any of these as compromised.

How do I remediate 24712-pl5006 if I installed it?

Remove 24712-pl5006 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 24712-pl5006 — how do I know if it already compromised me?

If 24712-pl5006 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.

How do I find 24712-pl5006 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 24712-pl5006 (2 malicious versions).

Malicious package

24712-pl5006npm

Advisory published May 7, 2026Updated May 12, 2026

24712-pl5006 is a confirmed malicious npm package (MAL-2026-3362) that executes malicious code on install (malicious versions 0.0.2, 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 24712-pl5006 (npm)

MAL-2026-3362

Immediate action

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

npm uninstall 24712-pl5006

What this malware does

The package 24712-pl5006 was found to contain malicious code.

The OpenSSF Package Analysis project identified '24712-pl5006' @ 0.0.4 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

0.0.20.0.4

Indicators of compromise (SHA-256)

115fd80ded696b407b50be96be06645124c2e3c5ca360f283388fcd4bcf3b2de

5c998277f8ad56f2757fe4a9a41de3e65f6c04442079c74b14497f1712a6f00b

d2546cdc76edb1f8a93dcf66c855ca6246bb0d4ed76c72a7fd3c1aec44f34761

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks 24712-pl5006-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

Explore

All malware advisories How O3 detects malware Vulnerability database