Which versions of byted-tbs are malicious?

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

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

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

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

Yes — byted-tbs is associated with the RLMA-2024-07909, 2024-08-byted-22.ax, RLUA-2026-00168 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-tbs 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-tbs (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging byted-tbs across your stack and pipelines.

Malicious package

byted-tbsPyPI

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

MAL-2024-9957

Immediate action

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

pip uninstall byted-tbs

What this malware does

Collects basic information about the system, most probably a pentest or bug bounty.

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-08-byted-22.ax

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.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

d9ee68a28ecc687350b9b7d9d8dabd25f35abbb1e0b67f4301c7db80a46ba6d6

c3a53a7c8acbad5a8fbd4f7d5d6fb603797208edeb860e7e0a792c51465a7dc6

749adf634a79e321082a53a1715caf4c239935563b6c3dadbd8e3e60e0e41485

8f39a268af75e3669e5104359e23f59174edc1068a36444af8b2a83d0ec85216

230a48a5e936ca70c96783b7b4b870aa2f7a23a9a17eb6e616ac37cde2b52dfd

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

Campaign

RLMA-2024-079092024-08-byted-22.axRLUA-2026-00168

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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