MAL-2026-13259 Malicious code in chatcc-agent (npm)
Malicious package
Published
MAL-2026-13259 is a malicious package: chatcc-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-13259/ (Markdown: https://insights.sbomify.com/MAL-2026-13259/index.md)
- Package
- chatcc-agent
- Registry
- npm
What is MAL-2026-13259?
MAL-2026-13259 is a malicious package in chatcc-agent, published on 5 Aug 2026.
Official description
chatcc-agent runs a daemon that connects to Tencent Cloud IM as a WebSocket client and treats inbound peer messages of type 'terminal_command', 'terminal_input', and 'terminal_pty_*' as instructions to spawn or write to a local shell / PTY on the installer's machine. In src/cclink-studio-remote.js and related handlers, _handleAdvancedCommand calls pty.spawn(shell, ['-lc', command],…) with the command string supplied by the remote IM peer, and handleInput forwards peer-supplied bytes into the active process's stdin. The result is a network-reachable, remote-controlled command-execution channel into the host that installed and runs the agent. Access is gated by JWT / paired-client authentication, but the channel, its bindings to a login shell, and the ability to stream arbitrary stdin exist by design and constitute a remote-shell surface regardless of how the package is described. Separately, the npm install script only performs a local native build (chmod of the shipped node-pty spawn-helper and compilation of a shipped C source with cc) and does not fetch or execute remote content.
What should I do about MAL-2026-13259?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.