Which versions of rehttps are malicious?

The following PyPI versions of rehttps are flagged malicious: 2.32.3, 2.32.4. Treat any of these as compromised.

How do I remediate rehttps if I installed it?

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

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

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

Malicious package

rehttpsPyPI

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

MAL-2025-6575

Immediate action

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

pip uninstall rehttps

What this malware does

During installation, package attempts to download and starts an executable. The package itself is a clone of requests

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

Campaign: 2025-06-rehttps

Reasons (based on the campaign):

clones-real-package
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

2.32.32.32.4

Indicators of compromise (SHA-256)

b924fe0d983802e0680682969caba92b2cbf7bc4e283e6d5cfb4a6643190ba46

ed0558450100f600f2ea688d6b1eaca23336eb304951c8ca13765f80828bb3ab

08172961784989f62b2b0793fa7686e1c25883883f790293df61591aa2fc6940

919decb344bd0a061ab33c4673f869cfb8fa964bbf2f8e75e6d747ebdb2c1d08

4448fe512725b4d8b1fba97c4b40d4169bb5e2fe9ea7301204dc3c874fe923ed

f0f176f75f3299a0d4103c5fb13964d0f736fd04528850a18b7c7f170c06bb66

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

Campaign

RLMA-2025-036742025-06-rehttpsRLUA-2026-00693

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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