Which versions of requests-os are malicious?

The following PyPI versions of requests-os are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate requests-os if I installed it?

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

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

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

Malicious package

requests-osPyPI

Malicious code in requests-os (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191657

Immediate action

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

pip uninstall requests-os

What this malware does

Package contains capabilities for remote control of the user's computer and exfiltrating data

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

Campaign: 2025-10-requests-os

Reasons (based on the campaign):

rat
typosquatting
backdoor
exfiltration-generic

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e50a22cb721c4b0aa9988c063b5780b9b83ee1e6f71d956c08a5efeba36e6fd1

6fc264ccaee37a8db76ec4e4a262750f71ab25d557aae34a6c3cc96b08329275

c944343070e83d2eab122e862b5c7349722ee7ceae5ae21e428926480681d24f

71c1fb1be00d5c213e25b3e577efae441b34a535f74d8da6c1fcbf3265f8ecbe

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

Campaign

RLMA-2025-056332025-10-requests-osRLUA-2026-00705

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks requests-os-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