@ccfly/setup-darwin-arm64
Affected
- Versions:
0.1.10,0.1.13,0.1.14,0.1.2,0.1.20,0.1.5,0.1.7,0.1.8,0.1.9
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @ccfly/setup-darwin-arm64 (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (4d5a88a77e76664c9050d9bad333214c053469264fff83ba56e2a68eaecfdfaa)
The tarball ships a single 6.4 MB Go binary at bin/ccfly-setup for darwin/arm64. The binary links github.com/gorilla/websocket and github.com/creack/pty and contains hardcoded strings 'wss://', 'ws://ccfly', and host 'cc.hn' alongside os/exec.Command and PTY handling — bytes received from the remote WebSocket endpoint are written into a local PTY, giving whoever controls cc.hn command execution on the host running the binary. Additional binary strings ('anthropic.com', 'claude.ai', '127.0.0.1:443', '.zshrc', '.bash_profile', 'export', 'approveccfly-*/redeem', 'https://cc.hn') show the binary also stands up a local 127.0.0.1:443 listener and writes export lines into ~/.zshrc and ~/.bash_profile so that the installer's shell routes Anthropic/Claude API requests — carrying the user's Anthropic API key or session tokens and prompt content — through the operator-controlled cc.hn infrastructure. The Chinese pairing prompt '请在网页上点「批准这台电脑」完成配对' confirms the flow is remote pairing of the host to the operator's console. The package itself declares no scripts, main, or bin entry, so the binary is not invoked by npm install alone; the harm fires when the parent @ccfly/setup CLI invokes it. The mechanism is nevertheless a full-host remote-control channel plus credential/prompt relay whose destination (cc.hn) is hardcoded and not caller-configured.
Not rated by the source.
0.1.10, 0.1.13, 0.1.14, 0.1.2, 0.1.20, 0.1.5, 0.1.7, 0.1.8, 0.1.9None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0