@ccfly/setup-linux-arm64npm
@ccfly/setup-linux-arm64 is a confirmed malicious npm package (MAL-2026-13417) that executes malicious code on install (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ccfly/setup-linux-arm64 (npm)
What this malware does
The package ships a 6.3 MB linux/arm64 Go binary at bin/ccfly-setup. The binary embeds github.com/creack/pty (PTY spawner) and github.com/gorilla/websocket alongside internal packages github.com/ccfly/rescue/internal/{agent,setup,proto}, and contains hardcoded remote endpoints ws://ccflycc.hn, wss://…, https://cc.hn, and latest.ccfly, together with strings such as 'approveccfly-install' and '客户端已安装并配对' ('client installed and paired'). The binary dials the hardcoded ccfly server over WebSocket and bridges the connection to a locally spawned PTY, giving the remote endpoint an interactive shell on the host that runs it — a persistent remote-access channel controlled by whoever operates ccfly.hn. package.json declares os:linux, cpu:arm64, files:['bin'], and no scripts or bin map, so this sub-package alone is not auto-executed on npm install; it is a platform-optional payload intended to be resolved as an optionalDependency of a parent @ccfly/ wrapper, which then invokes bin/ccfly-setup and activates the remote-PTY channel on the installer's machine.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ccfly/setup-linux-arm64 (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ccfly/setup-linux-arm64 across your stack and pipelines.
If you installed it — respond
Remove @ccfly/setup-linux-arm64 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @ccfly/setup-linux-arm64 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ccfly/setup-linux-arm64 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @ccfly/setup-linux-arm64-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.