Which versions of requestss3 are malicious?

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

How do I remediate requestss3 if I installed it?

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

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

Yes — requestss3 is associated with the RLMA-2025-00513, GENERIC-simple-tests, RLUA-2026-00712 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 requestss3 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 requestss3 (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 requestss3 across your stack and pipelines.

Malicious package

requestss3PyPI

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

MAL-2025-972

Immediate action

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

pip uninstall requestss3

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)

5c1919a6dceacc2422a7ccb9e2e41ad542331796200dad33cb7b44b48a52520c

6da81a1b9fddbafb79b42ac09a07809d7028a7285a073e4ffaa95482c181f4a9

1bfd2f315e97954adea4ee625dec63e7faf224270260aea1f9515ea35843b4ee

f1705071f9917892e3c957ad2a65f43f81a0217e1c771f2f3589e61bd6a67f83

aea10ac6fe8faad5af8032815ee3bc98e3bc3c77d08d138098a2908397b11e47

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 requestss3 (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 requestss3 across your stack and pipelines.
If you installed it — respond
Remove requestss3 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 requestss3 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 requestss3 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. requestss3 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-00513GENERIC-simple-testsRLUA-2026-00712

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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