Which versions of evil-pkg1 are malicious?

The following PyPI versions of evil-pkg1 are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate evil-pkg1 if I installed it?

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

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

Yes — evil-pkg1 is associated with the RLMA-2025-01958, GENERIC-simple-tests, RLUA-2026-00303 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 evil-pkg1 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 evil-pkg1 (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evil-pkg1 across your stack and pipelines.

Malicious package

evil-pkg1PyPI

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

MAL-2025-2960

Immediate action

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

pip uninstall evil-pkg1

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.2

Indicators of compromise (SHA-256)

cc9b70f736586afbe9b8333614541672998b5abc96bd4f31b05efef94bdae2f7

3f5e1a73b990d977aa2790b256d5af90a34e9362dc32122ac26d6b2a36a03811

f3f9795022d3525ac5206d67f60906020987aabf1bf4580b48d7ac7c6429108c

72f0591ef3d8cfebf595e501f68ee135d5655d8e472c401dedff59717327fd50

fbdc2ae30cdc8a58a29ff574c4e7ab1b52643a6bb4445abdf8ff19da7ac47e98

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

Campaign

RLMA-2025-01958GENERIC-simple-testsRLUA-2026-00303

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks evil-pkg1-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