Which versions of reqesst are malicious?

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

How do I remediate reqesst if I installed it?

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

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

Yes — reqesst is associated with the RLMA-2025-00506, 2024-12-reqesst, RLUA-2026-00694 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 reqesst 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 reqesst (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 reqesst across your stack and pipelines.

Malicious package

reqesstPyPI

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

MAL-2025-965

Immediate action

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

pip uninstall reqesst

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)

d94c3bdb37d37ea8180aa42f88fa5a3c84db9303bd1546c737afd16a08c1e12c

c8786d007c3e5cd893c74f360b9a48ed27a2b7ac293f41ea13c215927377d08f

8e4a4682ad923d5e0f2e444487e5f42a4bae8d753ecd747f7b652e407f5cc32f

c928201f9561558642a7b86acbd315fd4da2eba4e7189f38336daa138a284d58

419caeccba0c55f6ee477c131628a23ae84692d37e628ecb80ddabf59db9f248

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 reqesst (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 reqesst across your stack and pipelines.
If you installed it — respond
reqesst 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 reqesst 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 reqesst 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. reqesst 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-005062024-12-reqesstRLUA-2026-00694

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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