Which versions of requests-x64 are malicious?

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

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

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

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

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

Malicious package

requests-x64PyPI

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

MAL-2025-1992

Immediate action

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

pip uninstall requests-x64

What this malware does

Code in setup.py attempts to silently download and execute an executable. The file contains a malware

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

Campaign: 2025-02-requests-x64

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

f127b68d650d7dc2e2142f0f4d07a799060c9bdb649b87317a15b2f071316ee7

b61dd802c58f2577835c7848f5dd2977e05737aed2c00ccc9bd73c6003971140

996690f6aae3ce7456b45309072e2b12f5afda24b2f58e7f66b004c1f2b99872

16987150630b3870a214ee45dd7d75b168c3597d79d092549b4f418ea08553aa

055be74d01199b570cb1f9f875f9e3409ed8cfd35ff6fc0b5ff1bb09f30f7493

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

Campaign

RLMA-2025-012352025-02-requests-x64RLUA-2026-00708

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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