Which versions of pythonhttp are malicious?

The following PyPI versions of pythonhttp are flagged malicious: 0.1, 1.0.4. Treat any of these as compromised.

How do I remediate pythonhttp if I installed it?

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

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

Yes — pythonhttp is associated with the RLMA-2025-01992, 2025-03-pythonhttp, RLUA-2026-00669 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 pythonhttp 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 pythonhttp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pythonhttp across your stack and pipelines.

Malicious package

pythonhttpPyPI

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

MAL-2025-2993

Immediate action

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

pip uninstall pythonhttp

What this malware does

Installing the package starts a heavily obfuscated Powershell Script that attempts to (at least) overwrite copied crypto wallets

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

Campaign: 2025-03-pythonhttp

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
malware
crypto-related

Malicious versions

2 flagged

0.11.0.4

Indicators of compromise (SHA-256)

6a122a77250072d59a6c30b2481a19b1b841182f8531a7007131dd824324c4b1

47baf933e5681e0c9ccded4eb43838eba6471b269f6d6931be73a7ad98d38974

3ed5759c2260c5467724f053f3d59eac62f5491fc2d03350fef0a6f832652e3b

9f890dd2f7a693f0c2fe632b76bd7d111480dab1a6200c6671731ce0b5161f07

6415283ba4a5019ab461dcae2e7ff6642ce84db38b6ee5f259c73dd3bdfcf597

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

Campaign

RLMA-2025-019922025-03-pythonhttpRLUA-2026-00669

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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