Which versions of nayzakishere are malicious?

The following PyPI versions of nayzakishere are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate nayzakishere if I installed it?

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

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

Yes — nayzakishere is associated with the 2025-08-k7eel 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 nayzakishere across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nayzakishere (version 0.1.3).

Part of a larger attack: 2025-08-k7eel published 31 malicious packages. See the full campaign →

Malicious package

nayzakisherePyPI

Advisory published Sep 3, 2025Updated Dec 3, 2025

nayzakishere is a confirmed malicious PyPI package (MAL-2025-191800) that steals credentials and exfiltrates sensitive data (malicious version 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nayzakishere (PyPI)

MAL-2025-191800

Immediate action

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

pip uninstall nayzakishere

What this malware does

Importing the module downloads and executes widely recognized malware

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

2c4ab5dad4e0c5793a25d453433bc7114c06ff2e8f7251f555d87c905001eb66

448aef468d12fea1df0793a00d8a0e55788dcebd3033ed1ec515012020538b6b

Detection & response playbook

Credential / info stealer

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

Campaign

2025-08-k7eel

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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