Which versions of bytep are malicious?

The following PyPI versions of bytep are flagged malicious: 99.7. Treat any of these as compromised.

How do I remediate bytep if I installed it?

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

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

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

Malicious package

bytepPyPI

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

MAL-2024-10411

Immediate action

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

pip uninstall bytep

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

The OpenSSF Package Analysis project identified 'bytep' @ 99.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.7

Indicators of compromise (SHA-256)

32202f0ecea05873b046b19a634f9859ab04311b70e23d6ef827ed7c76cdefe5

ee4ca13e251a5cb7c54799ab2ec8adcfbdad449016fac3810f2ee1bc755caf20

8ab7e80f551a6d38ee9f4ee2163f0cb195257d40fb013074ff8887a8d70111ab

f506c9da071f574a09f59db23563caae752d0ba6dec7418ce9e4b4586a07e21c

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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