Which versions of bytekafka-0-15 are malicious?

The following PyPI versions of bytekafka-0-15 are flagged malicious: 98.7, 99.7. Treat any of these as compromised.

How do I remediate bytekafka-0-15 if I installed it?

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

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

Yes — bytekafka-0-15 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 bytekafka-0-15 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 bytekafka-0-15 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytekafka-0-15 across your stack and pipelines.

Malicious package

bytekafka-0-15PyPI

Malicious code in bytekafka-0-15 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10357

Immediate action

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

pip uninstall bytekafka-0-15

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 'bytekafka-0-15' @ 99.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

98.799.7

Indicators of compromise (SHA-256)

5ed583a5499eedc41f305bc194ebf9b3abbaa80df363f15f5793126c0d40fdc4

55bc38a643c4e7d9c6a5bf2b4f7af6607b72e6a9c9be717bec9266f1fc41f137

5080a4abcce26e927e9647316733cd5313eb9422fbdcd3f971e539e62f9ccfb2

6ed1b1c3203b8ef4e8b829755d78fecab7e4e6d088668dba36be5ab14a6e4d29

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 bytekafka-0-15 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bytekafka-0-15 across your stack and pipelines.
If you installed it — respond
bytekafka-0-15 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 bytekafka-0-15 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 bytekafka-0-15 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. bytekafka-0-15 on PyPI has been identified as a malicious package (versions 98.7, 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 bytekafka-0-15-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