Which versions of requeszs are malicious?

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

How do I remediate requeszs if I installed it?

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

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

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

Malicious package

requeszsPyPI

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

MAL-2025-973

Immediate action

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

pip uninstall requeszs

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)

0c8d42630b9cf503d3bf152e56a2ffdb625618583ca4077c038be59b8c88fc26

8784c5c388685fbcf778d36a06af620f43b251331f203b14bbe12ab11578faf1

d8c95a5f64dd212c781d6b3c45eb03f38bcf5220f688c4d903e9bfca20911b62

6965ffe498037e1f0b45e8af111f7a2f125fb0a468dabb797b5391b2807708a1

9558843b8a3aac26d19bf1e7cba0fe1a78070dd70726ab5d3f2d3ee7ca99215e

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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