Which versions of requires-python are malicious?

The following PyPI versions of requires-python are flagged malicious: 10.0.5. Treat any of these as compromised.

How do I remediate requires-python if I installed it?

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

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

Yes — requires-python is associated with the RLMA-2025-04242, 2025-07-triple-equals, RLUA-2026-00716 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 requires-python 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 requires-python (version 10.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requires-python across your stack and pipelines.

Malicious package

requires-pythonPyPI

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

MAL-2025-41747

Immediate action

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

pip uninstall requires-python

What this malware does

When imported, the package attempts to exfiltrate environment variables and basic user info

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

Campaign: 2025-07-triple-equals

Reasons (based on the campaign):

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

Malicious versions

1 flagged

10.0.5

Indicators of compromise (SHA-256)

579193d7aae052e05a939ea93ad44f8bd4185886f39e3441c1605a480910269d

206b3ac96122408ffbbda6deec04c04f185d3c9593c68669bf9ed247fcc7725f

fa1ee2e2c3ead90338250a60177535b23b5f30016e1d06a5b944092cbc3305e7

70e608cee8925bfd99294033811eece0e262363e1cfff761207d06d088f959e3

dd9c6561ae4bdaa27af1e04d70ac63259edbae1186122a0812514b71435b7b35

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

Campaign

RLMA-2025-042422025-07-triple-equalsRLUA-2026-00716

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks requires-python-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