What does the importlib-metadate malware do?

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: baidu-readver Reasons (based on the campaign): - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk. The OpenSSF Package Analysis project identified 'importlib-metadate' @ 99.99 (pypi) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of importlib-metadate are malicious?

The following PyPI versions of importlib-metadate are flagged malicious: 99.9, 99.99. Treat any of these as compromised.

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

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

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

Yes — importlib-metadate is associated with the baidu-readver 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-metadate 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-metadate (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-metadate across your stack and pipelines.

Malicious package

importlib-metadatePyPI

Malicious code in importlib-metadate (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-1624

Immediate action

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

pip uninstall importlib-metadate

What this malware does

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: baidu-readver

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

The OpenSSF Package Analysis project identified 'importlib-metadate' @ 99.99 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

99.999.99

Indicators of compromise (SHA-256)

53bd3e80b1638e34adc48ddfa9c544d1abe457f834b99802aec80f9de97a1609

540e9c9d054904f5342d684bd5cabf212fdbe7e4d20bac7407c937a6b8264cab

c3a970a330e8642d80689a8e79c8ca4a5df45f4c7c570b09a432d75914f22baf

b6db8994d6a78a5d0d95df2d0add2257ee6188f8c5419cbd7e2813426739d15d

fa2b68b5159c5a57f42a3cc0b11555eccc9a75c75d1920f9511e5d35964500ad

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for importlib-metadate (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-metadate across your stack and pipelines.
If you installed it — respond
importlib-metadate 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 importlib-metadate 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-metadate 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-metadate on PyPI has been identified as a malicious package (versions 99.9, 99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

baidu-readver

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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