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

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

Malicious package

nayzakisherePyPI

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

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