Which versions of byted-flex are malicious?

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

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

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

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

Yes — byted-flex is associated with the RLMA-2024-10990, 2024-11-byted-dast, RLUA-2026-00166 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-flex 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-flex (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-flex across your stack and pipelines.

Malicious package

byted-flexPyPI

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

MAL-2024-11544

Immediate action

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

pip uninstall byted-flex

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)

24557b2aaeb88e87cb6f5ddd6e9ee423d6e5a45ce1a2730a759e5e34364a0cb7

d842593135a7be692b4b202d3d9e82e9d0811ef6918c349fafad4606c8d481c6

f7c46f02d189ba471aba10b985193a2e0476f4f7f9f6e068ddf3fe79c2088ea1

93d6ba83fe38c916ac3b910d7e7fb4209e3a5857a39b88101e0955f9bbfac056

5c42259b150d72c135f4196ff59c6145dbdf1bd665f86603dbd613e424eaee05

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-flex (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-flex across your stack and pipelines.
If you installed it — respond
byted-flex 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-flex 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-flex 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-flex 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-109902024-11-byted-dastRLUA-2026-00166

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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