Which versions of rreqest are malicious?

The following PyPI versions of rreqest are flagged malicious: 2.32.3. Treat any of these as compromised.

How do I remediate rreqest if I installed it?

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

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

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

Malicious package

rreqestPyPI

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

MAL-2025-976

Immediate action

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

pip uninstall rreqest

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

1 flagged

2.32.3

Indicators of compromise (SHA-256)

22b6abc81adc0ece6dddaeedb83df73434fbfb025c80ac1cbed8fb0bab090dde

1cabfd3035ac04c36ceab6cd66a75dd1b7b6e2248609eabfa9c965ac37250c85

baa2747741fea6c476a38254b1cd32094fd0879e82055ae401b379cb31fa6b7d

ede0b73688761526459bfdf0038be09734bedda73c742cb7b9605f64566e3519

688bfbe8ee06f06e1e1e11c547f810e6bcaf98dbf717efe8caac8dad132502c0

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

Campaign

RLMA-2025-005172024-12-reqesstRLUA-2026-00732

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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