Which versions of 24712-pl4712 are malicious?

The following npm versions of 24712-pl4712 are flagged malicious: 0.0.1. Treat any of these as compromised.

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

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

If 24712-pl4712 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-pl4712 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 24712-pl4712 (version 0.0.1).

Malicious package

24712-pl4712npm

Advisory published May 6, 2026Updated May 12, 2026

24712-pl4712 is a confirmed malicious npm package (MAL-2026-3358) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 24712-pl4712 (npm)

MAL-2026-3358

Immediate action

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

npm uninstall 24712-pl4712

What this malware does

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

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

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5c130e58d93fcafbcca8c2b96d5f118ed91f68603d46541f5a261bdea8beaa29

4c8947855d76def29ae6497648e1355d55d891c01d5eea51f475ef033c0eda29

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for 24712-pl4712 (version 0.0.1).
If you installed it — respond
Remove 24712-pl4712 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-pl4712 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-pl4712 on npm has been identified as a malicious package (version 0.0.1 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-pl4712-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