reuestsPyPI
Malicious code in reuests (PyPI) Remove it immediately and rotate any exposed credentials.
What this malware does
Malicious packages typosquatting the popular requests package. payload execute a cryptomining malware
Malicious versions
Every published version of this package is considered malicious — remove it entirely.
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for reuests (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reuests across your stack and pipelines.
If you installed it — respond
reuests is a typosquat — you almost certainly intended a legitimately-named package. Remove reuests, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If reuests 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 reuests 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
References
Credits
- Checkmarx · finder
Detect & block this
O3 blocks reuests-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.