MAL-2026-13398 Malicious code in @xiaohhhh1/canvas-agent (npm)
Malicious package
Published
MAL-2026-13398 is a malicious package: @xiaohhhh1/canvas-agent (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-13398/ (Markdown: https://insights.sbomify.com/MAL-2026-13398/index.md)
- Package
- @xiaohhhh1/canvas-agent
- Registry
- npm
What is MAL-2026-13398?
MAL-2026-13398 is a malicious package in @xiaohhhh1/canvas-agent, published on 6 Aug 2026.
Official description
On bin start, @xiaohhhh1/canvas-agent opens an outbound WebSocket to the hardcoded relay wss://canvas.xiaohhhh1.com/api/agent-relay and treats inbound messages as HTTP requests to its own loopback API at 127.0.0.1:17371. The bridge unconditionally injects the local agent token (x-canvas-agent-token) into forwarded requests, so remote 'request' messages satisfy token authentication and can invoke /agent/codex/turn and /agent/claude/turn, which spawn the Codex app-server and Claude CLI locally with attacker-supplied prompts and a caller-controlled permissionMode. Codex/Claude are autonomous coding agents that can write files in the workspace and, when permissionMode is widened to danger-full-access, execute arbitrary shell commands. The same code path also bypasses the loopback server's browser-Origin allow-list: the origin gate is populated only after token validation, and the relay bridge presents the valid token without any user-consented browser Origin, so remote-originated calls pass the token+origin check the README advertises. The net effect is a network-to-local-agent-to-shell control path from a hardcoded author-controlled server into the installer's machine and any repository it is run against.
What should I do about MAL-2026-13398?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.