Which versions of reqest are malicious?

The following PyPI versions of reqest are flagged malicious: 0.0.1, 2.32.2, 2.32.3. Treat any of these as compromised.

How do I remediate reqest if I installed it?

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

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

Yes — reqest is associated with the RLMA-2025-00507, 2024-12-reqesst, RLUA-2026-00695 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 reqest 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 reqest (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reqest across your stack and pipelines.

Malicious package

reqestPyPI

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

MAL-2025-966

Immediate action

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

pip uninstall reqest

What this malware does

Importing the module downloads and starts an infostealer attempting to exfiltrate data and establishing persistence through autorun directory.

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

Campaign: 2024-12-reqesst

Reasons (based on the campaign):

infostealer
peristence-autorun
typosquatting
exfiltration-generic
Downloads and executes a remote executable.
clones-real-package
dependency-confusion
exfiltration-browser-data
exfiltration-crypto

Malicious versions

3 flagged

0.0.12.32.22.32.3

Indicators of compromise (SHA-256)

8de8096d1e3df2d3158a0fac832dabfc338ab7191ef7abd85ac0c6ab40bea722

5c312677f39911b9857e8d680b9c0b9f95c9ac9e3661ed792c9581b660670c85

35a7c05f500ebad2694b0b98105f189762f1892d35081dfd36a47787a2205f59

d371a722fb85bc85d5c37ba100708013a35ac82ce9217cd28c41d8de28dd53d2

dfdfce702ca54e49f9322f4231e3eed82850b5cc1201f85c73223472921d8dde

605494460ec5e159518a1f1e0432c5fe683ad6277dd2487038f02f73f1a5d6af

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

Campaign

RLMA-2025-005072024-12-reqesstRLUA-2026-00695

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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