Which versions of requestss2 are malicious?

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

How do I remediate requestss2 if I installed it?

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

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

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

Malicious package

requestss2PyPI

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

MAL-2025-971

Immediate action

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

pip uninstall requestss2

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)

d9ad88f8d922090a6ab22d5b1b5518f400f9cb974fd52afa25bb7f7cb94327a3

f8416a41f33e7b3b0482ca5c50d77977c90d3193028514ed56f3fedfc832f708

cc5f79bbd1f7d898cef93f24aa48c839ee4f03a3e641eed065c15094dece6e78

c65beb66383dcf3d246e281a4344e3b51a65886a078b33e122fa63b675ad94c9

464601a470d988e676b8826e626f87ce87d94a8a761b7fffba68b4cb90a30ecf

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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