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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bytesap (version 99.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytesap across your stack and pipelines.

Malicious package

bytesapPyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bytesap (version 99.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytesap across your stack and pipelines.
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 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 bytesap 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. 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