# MAL-2026-10746: Malicious code in sakuraai (npm)


- **Type:** Malicious package
- **Package:** `sakuraai` (npm)
- **Published:** 16 Jul 2026

## What is MAL-2026-10746?

MAL-2026-10746 is a malicious package in sakuraai, published on 16 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-10746?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10746 is a malicious package: sakuraai (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10746/ (Markdown: https://insights.sbomify.com/MAL-2026-10746/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10746

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10746/
Summaries are generated and may contain mistakes; the official description above is the record.