Which versions of zakuraweb are malicious?

The following PyPI versions of zakuraweb are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zakuraweb if I installed it?

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

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

Yes — zakuraweb is associated with the 2025-11-morosint 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 zakuraweb 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 zakuraweb (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zakuraweb across your stack and pipelines.

Malicious package

zakurawebPyPI

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

MAL-2025-191941

Immediate action

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

pip uninstall zakuraweb

What this malware does

Importing the module starts exfiltrating Discord tokens

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

Campaign: 2025-11-morosint

Reasons (based on the campaign):

exfiltration-browser-data
exfiltration-credentials

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6b16ae376b90b0961ff852408bd5dea69dc3a4af0012282b7680ff7de71e9f98

aa544044c8a113eb904f97650e8132de793d3bab5a7328a3714495e3f6a2283e

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 zakuraweb (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zakuraweb across your stack and pipelines.
If you installed it — respond
zakuraweb 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 zakuraweb 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 zakuraweb 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. zakuraweb on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-11-morosint

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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