Which versions of py-requests are malicious?

The following PyPI versions of py-requests are flagged malicious: 0.41.25. Treat any of these as compromised.

How do I remediate py-requests if I installed it?

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

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

Yes — py-requests is associated with the 2026-05-py-requests 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 py-requests 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 py-requests (version 0.41.25). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging py-requests across your stack and pipelines.

Malicious package

py-requestsPyPI

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

MAL-2026-3662

Immediate action

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

pip uninstall py-requests

What this malware does

Package installs persistent malware acting as Rat, with the focus of stealing data and modifying copied cryptowallet addresses.

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

Campaign: 2026-05-py-requests

Reasons (based on the campaign):

rat
typosquatting
persistence
Downloads and executes a remote malicious script.
crypto-related
clipboard-modify
exfiltration-browser-data
exfiltration-crypto
infostealer

Malicious versions

1 flagged

0.41.25

Indicators of compromise (SHA-256)

2bd2bd26870d2cf5df73c69bca7ed9088604eccf44727e4c59f0301cc8ccd35a

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

Campaign

2026-05-py-requests

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks py-requests-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