Which versions of importlibs-resources are malicious?

The following PyPI versions of importlibs-resources are flagged malicious: 95.6. Treat any of these as compromised.

How do I remediate importlibs-resources if I installed it?

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

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

Yes — importlibs-resources is associated with the 2024-11-byted-dast 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 importlibs-resources 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 importlibs-resources (version 95.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging importlibs-resources across your stack and pipelines.

Malicious package

importlibs-resourcesPyPI

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

MAL-2024-10739

Immediate action

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

pip uninstall importlibs-resources

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'importlibs-resources' @ 95.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

95.6

Indicators of compromise (SHA-256)

23a47f53489d4c74802f93b23e712eab76aa8ba30cb51a93f900e5e5ff632413

a80ddd3520525af57c942628b997a0cfeab4f0bb328bde44001868777c9a0c08

39a9626350ac0a042f49ec8c9203914a49f675be30c5f8f051e0315b5266d4f7

01282d4b2658db676fe735936dd61e2a952cddd02d1de4b58d853b9c1d4d9e88

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 importlibs-resources (version 95.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging importlibs-resources across your stack and pipelines.
If you installed it — respond
importlibs-resources 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 importlibs-resources 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 importlibs-resources 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. importlibs-resources on PyPI has been identified as a malicious package (version 95.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks importlibs-resources-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