Which versions of reque are malicious?

The following PyPI versions of reque are flagged malicious: 2.28.1. Treat any of these as compromised.

How do I remediate reque if I installed it?

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

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

Yes — reque is associated with the RLMA-2025-01232, 2025-01-rqsts, RLUA-2026-00700 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 reque 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 reque (version 2.28.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging reque across your stack and pipelines.

Malicious package

requePyPI

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

MAL-2025-1989

Immediate action

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

pip uninstall reque

What this malware does

Clone of the requests package that modified the code to send all get and post requests to a hardcoded URL

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

Campaign: 2025-01-rqsts

Reasons (based on the campaign):

clones-real-package
dependency-confusion
action-hidden-in-lib-usage

Malicious versions

1 flagged

2.28.1

Indicators of compromise (SHA-256)

29aefd9ca63f8ee7fea9da5bf797eb4521431fac5ecee585297799a6264f1449

2868969f8f103a53f2d494ac3568026c853853f99dd462dadb68b038a46cc319

8ce48406d7fce137de7e9a500179d7d6fcc5857714587372c977c5d6793cad30

c054f35fcaaeb583dc752886025bafb2b905c04e6c0060798fdbc3109f655576

f101fc291d74fc131e907585f697741bc9431e84a0c6b1f4a96912eba7ae2dad

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

Campaign

RLMA-2025-012322025-01-rqstsRLUA-2026-00700

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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