Which versions of flophttp are malicious?

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

How do I remediate flophttp if I installed it?

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

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

Yes — flophttp is associated with the RLMA-2024-08282, 2024-08-invokehttp, RLUA-2026-00330 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 flophttp 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 flophttp (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 flophttp across your stack and pipelines.

Malicious package

flophttpPyPI

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

MAL-2024-10028

Immediate action

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

pip uninstall flophttp

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)

838e8440b566dd2d9b660f7b4e1d4cfb8c29d4382be5c67030c27ebe2ab860ce

dafd91dca29837e4dcbfd4ca962e4f07958dd2d0eed0167f409f7e21edb2bd1c

45ad705b0505a09a4123e74a68d03c4a16dd91604a6d9ab323eb0d776320f68a

5608b0f7a925eb264c300488f850a36780819772784b21fa4d111bfa93f3fe2b

d2abfd7b220fcba6ae800efea0a692c915770a82656bd342d8471f3819921a23

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 flophttp (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 flophttp across your stack and pipelines.
If you installed it — respond
flophttp 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 flophttp 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 flophttp 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. flophttp 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-082822024-08-invokehttpRLUA-2026-00330

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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