Which versions of byted-flux are malicious?

The following PyPI versions of byted-flux are flagged malicious: 9.6. Treat any of these as compromised.

How do I remediate byted-flux if I installed it?

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

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

Yes — byted-flux is associated with the RLMA-2024-10991, 2024-11-byted-dast, RLUA-2026-00167 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 byted-flux 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 byted-flux (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging byted-flux across your stack and pipelines.

Malicious package

byted-fluxPyPI

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

MAL-2024-11545

Immediate action

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

pip uninstall byted-flux

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

9.6

Indicators of compromise (SHA-256)

18a474894b1d69a9ea6486e7462beac8ea6565199d3ed4fa7f299d35d036c3f0

b3b00b151352d1d06f3c8caf5b4d8352fd167821802b1acbd5db359435d6b603

a8424c4934716d4a7390731613807c89bca1d0f11a56e3062dacef247d859e80

0033e8dc7b12b6aea9bbf09f221317b7191704efa548fffc50a200e50c996dcf

5a759d7febad110853618af0e88932ba664decab45afed135e05e56566d9e1ad

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

Campaign

RLMA-2024-109912024-11-byted-dastRLUA-2026-00167

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks byted-flux-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