Which versions of utilhttp are malicious?

The following PyPI versions of utilhttp are flagged malicious: 2.3.5. Treat any of these as compromised.

How do I remediate utilhttp if I installed it?

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

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

Yes — utilhttp is associated with the RLMA-2024-09477, 2024-08-invokehttp, RLUA-2026-00879 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 utilhttp 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 utilhttp (version 2.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging utilhttp across your stack and pipelines.

Malicious package

utilhttpPyPI

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

MAL-2024-10184

Immediate action

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

pip uninstall utilhttp

What this malware does

In the invokehttp, the init.py contains obfuscated code attempting to download and run one of two executables. They are identified as malicious by VT and the tracks of Telegram URLs suggests attempting data exfiltration. The package itself looks like a copy of requests. In flophttp, using exactly the same obfuscation method, the infostealer is directly embeded into package code and exfiltrates data to a telegram channel.

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

Campaign: 2024-08-invokehttp

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
obfuscation
clones-real-package

Malicious versions

1 flagged

2.3.5

Indicators of compromise (SHA-256)

9bcd0c5ac08a48be46e8597a96edc9580558d45062cd7fa606bf0281b4509572

746164209a39b4d7dfb5c28b257e79f9fe575dadca5efee038b5f37e008ce34b

f91f83da1ea0307373682776ad3de3a3fd320d57280f40fa82f47aaf316d3062

3a85882b21ad755b37c12046cdb9d71a574e2781a5bb6cc7d9ae0d756cb2eae4

850bed7d3acb3c8dc30a10bd39d77dcd9b6940382d3e9c6361d1e9d4b89bc8ca

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

Campaign

RLMA-2024-094772024-08-invokehttpRLUA-2026-00879

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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