Which versions of reqzest are malicious?

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

How do I remediate reqzest if I installed it?

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

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

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

Malicious package

reqzestPyPI

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

MAL-2025-975

Immediate action

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

pip uninstall reqzest

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

2 flagged

2.32.22.32.3

Indicators of compromise (SHA-256)

92b20595bdfe882d43cf9b555add76689ff68c07aaf257e198b6798a8817d0ac

2090bcd15889edb966592ef66ccc935b92ff2bc8be830550d3cff07ea4854852

32fb197467e37327d9d2b079a85faa4ffffa0cdc05c9703957a9f36de8f453e6

6e61b0291c3932ff2a6225c9cb3ae5a5c5762e0162dd4c6682e8bb268311c13d

dbe06125519e641822ea152e34601107dceeb78fe424480b4dfced1ded1c61e6

924491c6d012ac65bcae24bfc01477a710a6b71d131e338cc21163c74c17dea4

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 reqzest (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reqzest across your stack and pipelines.
If you installed it — respond
reqzest 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 reqzest 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 reqzest 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. reqzest on PyPI has been identified as a malicious package (versions 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-005162024-12-reqesstRLUA-2026-00718

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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