Which versions of sakuraai are malicious?

The following npm versions of sakuraai are flagged malicious: 0.0.11. Treat any of these as compromised.

How do I remediate sakuraai if I installed it?

Remove sakuraai from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed sakuraai — how do I know if it already compromised me?

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

Yes — sakuraai is associated with the IN-MAL-2026-010764 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 sakuraai across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sakuraai (version 0.0.11).

Malicious package

sakuraainpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

sakuraai is a confirmed malicious npm package (MAL-2026-10746) that executes malicious code on install (malicious version 0.0.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sakuraai (npm)

MAL-2026-10746

Immediate action

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

npm uninstall sakuraai

What this malware does

When the daemon is started (e.g. via sakura daemon start), the package binds an HTTP+WebSocket server on 0.0.0.0 and additionally exposes it via a Tailscale sidecar. The WebSocket handler spawns an interactive OS shell (process.env.SHELL || /bin/zsh on Unix, cmd.exe on Windows) with the -i flag and pipes incoming WebSocket {type:'input', data:...} frames directly into the shell's stdin, streaming stdout/stderr back over the same socket (dist/index.js: spawn(shell, ["-i"],...), writeTerminal(ws, msg.data), server.listen(port, host === "127.0.0.1"? "0.0.0.0": host,...)). Any party with network reachability to the daemon — anyone on the LAN, or anyone with a valid bearer token over the Tailscale tailnet — obtains full-host command execution as the user running the daemon. A separate postinstall script (scripts/download-tsnet.js, scripts/download-onboard.js) fetches sakura-tsnet / sakura-onboard binaries from https://github.com/Nishu0/sakura-tsnet/releases/download/v<version>/... over HTTPS, pinned to the package version but without hash/signature verification; the publishing GitHub account (Nishu0) is a personal account rather than an organization matching the advertised Sakura / sakura.mom publisher identity.

Malicious versions

1 flagged

0.0.11

Indicators of compromise (SHA-256)

d0910c3572d73bd98775851cb79032ba00dbceda2de969b25f04a7a7d1ddfe4e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sakuraai (version 0.0.11).
If you installed it — respond
Remove sakuraai from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If sakuraai 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. sakuraai on npm has been identified as a malicious package (version 0.0.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010764

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sakuraai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database