Which versions of mflux-streamlit are malicious?

The following PyPI versions of mflux-streamlit are flagged malicious: 0.0.3, 0.0.4. Treat any of these as compromised.

How do I remediate mflux-streamlit if I installed it?

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

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

Yes — mflux-streamlit is associated with the 2026-06-compr-woodpecker, IN-MAL-2026-008588, IN-MAL-2026-008905 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 mflux-streamlit 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 mflux-streamlit (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mflux-streamlit across your stack and pipelines.

Malicious package

mflux-streamlitPyPI

Malicious code in mflux-streamlit (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5301

Immediate action

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

pip uninstall mflux-streamlit

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Versions 0.0.3, 0.0.4 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

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

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

2 flagged

0.0.30.0.4

Indicators of compromise (SHA-256)

27ef4c7f33e59dbe037d4b212286dd08cb7b1824c28c0032eb2d91db7a2b0174

78056caffa187ecd62662eefc42d17dd25cb0d010fd6995b2a1857889ebe3b72

24886fb9c3f7248367f9e8709b3ef1245a010d0bed4a35f1b83f0199b2498dba

5da8453add83bdfa35dc65b2be55d7820ae94737974de952b77cfb4fc79d735e

9924feddaacd4b86934ddc7bdf8ff498921a80b34bf99a9136baa592fcc504b6

5a5969e0bdbaab767b8a6de48420d21566df2dcaee8c655fd82a34bceada7fd3

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

Campaign

2026-06-compr-woodpeckerIN-MAL-2026-008588IN-MAL-2026-008905

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks mflux-streamlit-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