Which versions of byte-flux-3822a6dd00d6414daba3ae0de3930a5a are malicious?

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

I already installed byte-flux-3822a6dd00d6414daba3ae0de3930a5a — how do I know if it already compromised me?

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

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

Malicious package

byte-flux-3822a6dd00d6414daba3ae0de3930a5aPyPI

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

MAL-2024-11542

Immediate action

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

pip uninstall byte-flux-3822a6dd00d6414daba3ae0de3930a5a

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)

654071e046a5b7fdecba02c3c3cbf5c243a254e7abf1143e45c9c17f80f0eb73

44fd67da3ee2aa348e3b96c12b6553757a92ae0f983277fdc3f2774e50a1d47c

cec00e10a19e19684fc4887fa09aa1025aafc00f1121baacdf55f0c3b2ba9aec

142d085cd73df118d9050b8f9c746d57b723a71a4389ac8ea2106d14bb0fa50d

4624ebd7892fdf31f5b4f5815b036152b33868b069cc6829790a99ae11612ca3

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 byte-flux-3822a6dd00d6414daba3ae0de3930a5a (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging byte-flux-3822a6dd00d6414daba3ae0de3930a5a across your stack and pipelines.
If you installed it — respond
byte-flux-3822a6dd00d6414daba3ae0de3930a5a 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 byte-flux-3822a6dd00d6414daba3ae0de3930a5a 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 byte-flux-3822a6dd00d6414daba3ae0de3930a5a 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. byte-flux-3822a6dd00d6414daba3ae0de3930a5a 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-109882024-11-byted-dastRLUA-2026-00163

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks byte-flux-3822a6dd00d6414daba3ae0de3930a5a-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