Which versions of pehttps are malicious?

The following PyPI versions of pehttps are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate pehttps if I installed it?

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

If pehttps was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is pehttps part of a known attack campaign?

Yes — pehttps is associated with the RLMA-2024-04244, RLUA-2024-08670 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 pehttps across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pehttps (version 0.0.2).

Malicious package

pehttpsPyPI

pehttps is a confirmed malicious PyPI package (MAL-2024-5462) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pehttps (PyPI)

MAL-2024-5462

Immediate action

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

pip uninstall pehttps

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

ff61ff15e2acf5fbf28e7b93a9768d6f58550f7a3ad1b9ac64b79bab3fe588cc

e6cee639863a1a519e9aa8fb7f4a382d30827b5b857ba6eb843f18381a825454

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pehttps (version 0.0.2).
If you installed it — respond
Remove pehttps 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 pehttps was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. pehttps on PyPI has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04244RLUA-2024-08670

References

Credits

ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database