Which versions of kyleip are malicious?

The following PyPI versions of kyleip are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate kyleip if I installed it?

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

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

Yes — kyleip is associated with the GENERIC-beacon-dependency-confusion 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 kyleip across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kyleip (version 0.2).

Malicious package

kyleipPyPI

Advisory published Apr 15, 2026Updated Apr 15, 2026

kyleip is a confirmed malicious PyPI package (MAL-2026-2698) that steals credentials and exfiltrates sensitive data (malicious version 0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kyleip (PyPI)

MAL-2026-2698

Immediate action

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

pip uninstall kyleip

What this malware does

Package exploits dependency confusion. A beacon request is used to report usage back, but no additional information are exfiltrated.

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: GENERIC-beacon-dependency-confusion

Reasons (based on the campaign):

typosquatting
dependency-confusion

Malicious versions

1 flagged

0.2

Indicators of compromise (SHA-256)

6a05611ec8862117c6403a4a06759ca56bf2922c2b142a4661b77fd214ef26be

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for kyleip (version 0.2).
If you installed it — respond
kyleip 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 kyleip 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. kyleip on PyPI has been identified as a malicious package (version 0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-beacon-dependency-confusion

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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