Which versions of invokehttp are malicious?

The following PyPI versions of invokehttp are flagged malicious: 2.5.3, 2.5.5. Treat any of these as compromised.

How do I remediate invokehttp if I installed it?

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

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

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

Malicious package

invokehttpPyPI

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

MAL-2024-8726

Immediate action

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

pip uninstall invokehttp

What this malware does

The init.py contains a call to execute a Base64-encoded script to download a second stage payload.

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

2 flagged

2.5.32.5.5

Indicators of compromise (SHA-256)

f0092914933fe4888b5cdc55f1b3235c3e846530444b2606fc0b2262a7aa28e2

51a7f71567d888552aa8c2e50bbfd2d99b751a9594957dbcc93694d78ed83081

e3374942a3d2de4ea1f9444223c351c0ef5356c571a08e8ddb62144f7564def0

5547cc28855d673eab964ac8dd47c53e86707b2f1f6f2d318a12e1e82c4255c7

0878ad5c66d246ce361ff0ac6806338377a4de3bd4aa2fb3e50de3c06d3bd7c7

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

Campaign

RLMA-2024-110702024-08-invokehttpRLUA-2026-00431

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder
Stacklok: trustypkg.dev · finder

Detect & block this

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