Which versions of requesra are malicious?

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

How do I remediate requesra if I installed it?

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

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

Yes — requesra is associated with the RLMA-2025-01234, 2025-01-rqsts, RLUA-2026-00702 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 requesra 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 requesra (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 requesra across your stack and pipelines.

Malicious package

requesraPyPI

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

MAL-2025-1991

Immediate action

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

pip uninstall requesra

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)

043d9ce2e45f8664489ff09e45cc8da71167e8c8afd701d349cb62f0a56d5a1f

cae844115e69e37d56e1c68eded05d0dfad6b2a584f999ef7e79fc1e4c86ce49

42ce5266dc952340618c995bfe692bd0f801b7b3d098188739aa66038074122e

5020d0764d9327f6e9bc3a07d2c336edfc877455c3f7b3f0ea7cfd9f29742ff9

9ffafa26590e662a696d1b8cff78902addb6f20a38f7a916815fc43189622aee

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 requesra (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 requesra across your stack and pipelines.
If you installed it — respond
requesra 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 requesra 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 requesra 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. requesra 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-012342025-01-rqstsRLUA-2026-00702

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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