Which versions of requests1 are malicious?

The following PyPI versions of requests1 are flagged malicious: 3.3.3.3. Treat any of these as compromised.

How do I remediate requests1 if I installed it?

Remove requests1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed requests1 — how do I know if it already compromised me?

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

Yes — requests1 is associated with the RLMA-2025-00511, GENERIC-simple-tests, RLUA-2026-00709 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 requests1 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 requests1 (version 3.3.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requests1 across your stack and pipelines.

Malicious package

requests1PyPI

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

MAL-2025-970

Immediate action

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

pip uninstall requests1

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

3.3.3.3

Indicators of compromise (SHA-256)

9d3b8f2e89f181b016255bcaa1f89581634a8b23d8bb21a1bea74faad1109898

f6d7802fea36a8a4e8091d0d663eac22ec9dda0e2e4aa8c45ffcb642b46c8de6

8a90fb9bdcfcbdf0996c9b09ca72f9577185947dd235586518b7b30ce3e0a5ff

dda32545a1fdeb694966833861fa82168ff0ae284d3e086640e3a80ad0f626d9

405141e96a6a1b2434e2fe0b90ba142b3062367eaf106a03ae3008aff0cb5670

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for requests1 (version 3.3.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging requests1 across your stack and pipelines.
If you installed it — respond
Remove requests1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If requests1 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 requests1 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. requests1 on PyPI has been identified as a malicious package (version 3.3.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00511GENERIC-simple-testsRLUA-2026-00709

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks requests1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring