Which versions of fluxhttp are malicious?

The following PyPI versions of fluxhttp are flagged malicious: 1.0.1, 1.0.2, 1a1. Treat any of these as compromised.

How do I remediate fluxhttp if I installed it?

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

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

Yes — fluxhttp is associated with the 2026-03-license-utils-kit 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 fluxhttp 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 fluxhttp (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fluxhttp across your stack and pipelines.

Malicious package

fluxhttpPyPI

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

MAL-2026-2244

Immediate action

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

pip uninstall fluxhttp

What this malware does

Malicious clone of a legitimate package. When using it, the code attempts to download and execute remote code. In on of the incarnations, the malicious code was embeded in the strongly obfuscated file, which at least collected data from cryptowallets and password managers and exfiltrated them to a hardcoded remote location.

The downloaded next stage varies depending on the running platform. On Windows, it's extream obfuscated script. On Linux and MacOS they are binaries, named "systemd-resolved" and "com.apple.systemevents" with clear signs of stealing browsers and cryptocurrency data.

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

Campaign: 2026-03-license-utils-kit

Reasons (based on the campaign):

infostealer
obfuscation
crypto-related
action-hidden-in-lib-usage
exfiltration-credentials
clones-real-package

Malicious versions

3 flagged

1.0.11.0.21a1

Indicators of compromise (SHA-256)

89f45079c25c2a6ce670f2f2a1d79b0680ce53717df7be67130280fc866e4995

2669b72303bd592ba1633febc04bca1f0a8804d8546baf21b5f3f12baaa80f29

68ff41be5889bcb120b225c9689f1c0ec6be5db6110a6e66bc840b6f74a4d0b1

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

Campaign

2026-03-license-utils-kit

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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