Which versions of byteff are malicious?

The following PyPI versions of byteff are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate byteff if I installed it?

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

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

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

Malicious package

byteffPyPI

Malicious code in byteff (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11547

Immediate action

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

pip uninstall byteff

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

912.6

Indicators of compromise (SHA-256)

e0c906d9067232a7488fce8d078673ae4ad49171bb575d730268611fc6450f84

b3040ce772fcc31ceaf6844d02cd264bcb9c4bc5ba37f506f119d670711fd968

a56aa5a63bf5b3ed081b62351f3aedb42fd6c2e834ab240922247add79aee664

0bee623683b22bcdff50c231ca89429cbf4bbf574a866f9fac7411508f1705f2

a3c9c91eba58481a22be32655fcdd2264ac11d24ecd4f2841f77057b5548fe50

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

Campaign

RLMA-2024-109932024-11-byted-dastRLUA-2026-00172

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks byteff-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