Which versions of importlib-metadata are malicious?

The following npm versions of importlib-metadata are flagged malicious: 1.0.0, 10.1.1. Treat any of these as compromised.

How do I remediate importlib-metadata if I installed it?

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

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

Yes — importlib-metadata is associated with the RLMA-2024-01176, RLUA-2024-06728, GHSA-pxch-f2f7-mh4p, RLUA-2025-05391, RLUA-2025-05812 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 importlib-metadata 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 importlib-metadata (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging importlib-metadata across your stack and pipelines.

Malicious package

importlib-metadatanpm

importlib-metadata is a confirmed malicious npm package (MAL-2024-2506) that executes malicious code on install (malicious versions 1.0.0, 10.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in importlib-metadata (npm)

MAL-2024-2506

Immediate action

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

npm uninstall importlib-metadata

What this malware does

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

2 flagged

1.0.010.1.1

Indicators of compromise (SHA-256)

1ef7d52bb90ba04464a96553577a3c9932f213f898c83d21017b7e240a4e67aa

4420bfda836bd0e620a16387d5e069229bf7ea25dbd05f18e50fc1b7400c364e

35c1ba96ae1a4f623e6b2c175b5745b1a1eaa0c1c04c6022a3eb07c135d2dcdb

dcd02c14cf867c1c3a61d70da7cac70f53b2a4f5dece4d057cd6467a397088a4

5196284c66479a72c61a8fffb2d880264cc33d60df3b5dcda399c423c95c91ca

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for importlib-metadata (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging importlib-metadata across your stack and pipelines.
If you installed it — respond
Remove importlib-metadata 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 importlib-metadata 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 importlib-metadata 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. importlib-metadata on npm has been identified as a malicious package (versions 1.0.0, 10.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-01176RLUA-2024-06728GHSA-pxch-f2f7-mh4pRLUA-2025-05391RLUA-2025-05812

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks importlib-metadata-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