Malicious code in @aster110/cc2wechat (npm)
The npm package @aster110/cc2wechat contains malicious code that establishes a remote shell interface via WeChat messages. When the daemon is started, it polls Tencent's iLink Bot API and forwards incoming WeChat messages to locally-hosted AI agents (Claude or Codex) configured with safety gates disabled, allowing arbitrary shell and filesystem operations.
- Disclosed
- Last updated
- Blast radius
- Any system running the @aster110/cc2wechat daemon with access to a linked WeChat account.
- Ecosystems
- Attack vectors
- Affected entities
- @aster110/cc2wechatnpm package containing malicious code
The @aster110/cc2wechat npm package contains intentionally malicious code designed to create a remote command execution vector. The package runs a daemon that continuously polls Tencent's iLink Bot API (ilinkai.weixin.qq.com) for incoming WeChat messages directed at a linked account.\n\nIncoming message text is forwarded directly into locally-hosted AI agent CLIs—either Claude or Codex—that are explicitly configured with safety and sandbox restrictions disabled (--dangerously-skip-permissions and --dangerously-bypass-approvals-and-sandbox). The messages are injected via tmux session manipulation using load-buffer, paste-buffer, and send-keys commands.\n\nBecause these AI CLIs are configured to auto-execute shell commands and filesystem operations without user prompts when safety flags are disabled, any party able to send a WeChat message to the linked account can drive arbitrary shell and file operations on the host machine. The malicious surface materializes when the operator launches the daemon via the cc2wechat start CLI command, not during package installation or require().\n\nThe package documentation acknowledges the full-host access risk and recommends running it only in a disposable VM. The incident was identified by the OpenSSF malicious-packages project.
Indicators of compromise
- Packages
- @aster110/cc2wechat
- Domains
- ilinkai.weixin.qq.com
Remediation
- Immediately uninstall @aster110/cc2wechat from all systems
- Audit any systems where the cc2wechat daemon was previously running for unauthorized shell commands or file modifications
- Review WeChat message logs for the linked account during the period the daemon was active
- Rotate credentials and API keys that may have been exposed on affected systems
- Do not install or run this package; use alternative legitimate tools for WeChat integration if needed
Sources
- GitHub Advisory GHSA-3j3w-m5jm-4w97 · GitHub Advisory Database
Cite this entry
"Malicious code in @aster110/cc2wechat (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-aster110-cc2wechat-npm-o673y0
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in @ai-vertical/ai-agent
Malware was discovered in the npm package @ai-vertical/ai-agent. Systems with this package installed or running should be considered fully compromised and require immediate remediation.
npmAI agents & skillsCompromised package - resolvedcritical
Malicious code in mangomind-agent (npm)
The npm package mangomind-agent contained malicious code that established a persistent WebSocket connection to a hardcoded relay server, enabling remote code execution and AI-agent-driven filesystem access on any host running the package. The vulnerability was discovered and reported by the OpenSSF.
npmAI agents & skillsCompromised packageMalicious commit - resolvedcritical
Malicious code in zyr-agent (npm)
zyr-agent (npm) shipped with malicious code that enables remote command execution through a hardcoded preview-slug endpoint controlled by the package author. The AI agent auto-executes tool calls (including bash commands) returned by the remote endpoint without user confirmation.
npmAI agents & skillsMalicious commitCompromised package - resolvedcritical
Malicious code in @lyxa.ai/core (npm)
The npm package @lyxa.ai/core contained malicious code that unconditionally routes all application events through author-controlled cloud infrastructure (CloudAMQP, Redis Cloud, GCP) using embedded credentials, and ships live private keys for GCP and Firebase services, allowing the author to intercept, modify, and trigger arbitrary handlers in any installer's process.
npmAI agents & skillsCompromised packageMalicious maintainer