Which versions of package-resources are malicious?

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

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

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

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

Yes — package-resources is associated with the 2025-06-diar-ai-basic 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 package-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 package-resources (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging package-resources across your stack and pipelines.

Malicious package

package-resourcesPyPI

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

MAL-2025-191808

Immediate action

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

pip uninstall package-resources

What this malware does

Research packages targeting typosquatting and dependency confusions, without really harmful behaviour - just calling home through DNS resolver.

Related to 2025-06-stubsout (using the same remote domain), but without dangerous activity

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: 2025-06-diar-ai-basic

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

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

66a39eb6a99f6a3c82112d2bed26ef992a2fc406ba72a4678fced96168b4b088

ca5a9eea6d70ca2932b87cad82f57aa47d4ca38f9ba6c9d2f45d465b46c8358f

58d9a45eed476652ad45860a9e7eeae7e75ad84658e4dd4bdca85f7ed1835782

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 package-resources (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging package-resources across your stack and pipelines.
If you installed it — respond
package-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 package-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 package-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. package-resources on PyPI 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.

Campaign

2025-06-diar-ai-basic

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks package-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