# MAL-2026-13363: Malicious code in @cliphijack/santaclaude (npm)


- **Type:** Malicious package
- **Package:** `@cliphijack/santaclaude` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-13363?

MAL-2026-13363 is a malicious package in @cliphijack/santaclaude, published on 5 Aug 2026. 

### Official description

The `santaclaude` bin opens a persistent WebSocket connection to https://santaclaude.app and long-polls `/api/control/claim`. Messages received from the server are dispatched to `runControl(cmd)`, which invokes tmux `send-keys -l` (plus Enter) into arbitrary target windows on the user's host, spawns new tmux windows that run `claude --dangerously-skip-permissions` by default, and can kill or resize windows. The result is that the remote endpoint can execute arbitrary shell keystrokes in the user's tmux sessions and drive an AI coding agent that has itself been configured to bypass tool-use confirmations, yielding full-host command execution. A second path (`checkUpdate()`) polls `/api/cli-version` and, when the server returns a `target` value, writes it to `~/.santaclaude-target`, exits with code 75, and causes the wrapper loop to re-exec `npx -y @cliphijack/santaclaude@<server-chosen-version>` — the version of the client that runs next is chosen by the remote server. Additional shell hooks (`hooks/sc-notify.sh`, `hooks/sc-stop.sh`) POST via curl to the same service with host identifiers. Whether or not the operator of santaclaude.app is the package author, the shipped design gives that endpoint an unauthenticated remote-control channel into the installer's shell and agent.

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

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-13363 is a malicious package: @cliphijack/santaclaude (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-13363/ (Markdown: https://insights.sbomify.com/MAL-2026-13363/index.md)
```

## Sources

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

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