Which versions of bytesap are malicious?

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

How do I remediate bytesap if I installed it?

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

If bytesap was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is bytesap part of a known attack campaign?

Yes — bytesap 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 bytesap across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bytesap (version 99.7).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

bytesapPyPI

Advisory published Nov 5, 2024Updated Dec 12, 2025

bytesap is a confirmed malicious PyPI package (MAL-2024-10367) that steals credentials and exfiltrates sensitive data (malicious version 99.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bytesap (PyPI)

MAL-2024-10367

Immediate action

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

pip uninstall bytesap

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 'bytesap' @ 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)

02468ca2a6c6786284502b294e1d557b03baf8779034cba7c4df205dc77bd710

27b62bd72c276d049d4db9911bb7328b28efe070719ddc44b8f1aabd0e710bdd

4eec30f2d541d35548fef109eb76c972e92203c749f615aa08f976fb9b0c2a03

686beacf1d7da2468af1104d62aabdba48560976b04eb39b5cb533a67918d000

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bytesap (version 99.7).
If you installed it — respond
bytesap 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 bytesap was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bytesap 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 bytesap-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

Explore

All malware advisories How O3 detects malware Vulnerability database