Which versions of bytepilot are malicious?

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

How do I remediate bytepilot if I installed it?

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

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

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

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

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

Malicious package

bytepilotPyPI

Advisory published Nov 6, 2024Updated Dec 12, 2025

bytepilot is a confirmed malicious PyPI package (MAL-2024-10426) 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 bytepilot (PyPI)

MAL-2024-10426

Immediate action

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

pip uninstall bytepilot

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

587ad26f6449c01cdcc8fa5dfff06575e300a391b70a0f27f69e31eeec44f873

8532d66e351a22ea9aa5c2e5f60b752fa2722d13c667e04f5d1a0ac74264da38

c0d90c01bceedad5b420353d56d8b0d29f6571169ab91d9cda129f242e66c40b

66401a910fceedd29d3d65ce68e672921d721862fd2ca82bb00e7b11d4640fce

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bytepilot (version 99.7).
If you installed it — respond
bytepilot 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 bytepilot 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. bytepilot 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 bytepilot-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