Which versions of rqsts are malicious?

The following PyPI versions of rqsts are flagged malicious: 2.28.1. Treat any of these as compromised.

How do I remediate rqsts if I installed it?

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

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

Yes — rqsts is associated with the RLMA-2025-01238, 2025-01-rqsts, RLUA-2026-00731 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 rqsts 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 rqsts (version 2.28.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rqsts across your stack and pipelines.

Malicious package

rqstsPyPI

Malicious code in rqsts (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-1995

Immediate action

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

pip uninstall rqsts

What this malware does

Clone of the requests package that modified the code to send all get and post requests to a hardcoded URL

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

Campaign: 2025-01-rqsts

Reasons (based on the campaign):

clones-real-package
dependency-confusion
action-hidden-in-lib-usage

Malicious versions

1 flagged

2.28.1

Indicators of compromise (SHA-256)

57702300f5f501f1ab1a263a8c5def6487e55baf3aaa009fd805b0f63452d2c9

08f341e4a6bb7d1a61001636633c9095b6ce869578791c61c8cbea8cf6caea1e

f9b439bd545383aa5d5b1739d488888d95d4db48c34dc5d8c0339d0e95036af5

b26fbf60519c0a813686bd4c94657fa06694648bcc8053a9255c78c2980555c6

f2d08efd18c12dbf3082aeef93dc81d81f3eca9703a5020a89869649a7c5205e

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

Campaign

RLMA-2025-012382025-01-rqstsRLUA-2026-00731

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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