Which versions of bytepps are malicious?

The following PyPI versions of bytepps are flagged malicious: 94.6. Treat any of these as compromised.

How do I remediate bytepps if I installed it?

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

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

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

Malicious package

byteppsPyPI

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

MAL-2024-11548

Immediate action

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

pip uninstall bytepps

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

94.6

Indicators of compromise (SHA-256)

f94f1732be6ca20ca4ccdd3b2f80616e3c89a010917e144fc9c690f4e7143e9b

ce2661d46c44a5e3be1ccb8a5f6f97086dbdfcde7c0199b63a12143402a0d2d9

9aa4ba0120720e5b121a5cbccaa4bd97efb87a5f2fa881edc7a297d33fab3c4f

9184175245ba4ad8807e19c8936d0fbc678a7cd48f25bb69f84a2270dcab8b21

106e433e0de06ba1fc7a5057e4c4ff2ea091d4f308be986b3320f190b9ce5cc5

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

Campaign

RLMA-2024-109942024-11-byted-dastRLUA-2026-00173

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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