Which versions of @ccfly/setup-darwin-x64 are malicious?

The following npm versions of @ccfly/setup-darwin-x64 are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate @ccfly/setup-darwin-x64 if I installed it?

@ccfly/setup-darwin-x64 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @ccfly/setup-darwin-x64 — how do I know if it already compromised me?

If @ccfly/setup-darwin-x64 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.

Is @ccfly/setup-darwin-x64 part of a known attack campaign?

Yes — @ccfly/setup-darwin-x64 is associated with the IN-MAL-2026-014797 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ccfly/setup-darwin-x64 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ccfly/setup-darwin-x64 (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ccfly/setup-darwin-x64 across your stack and pipelines.

Malicious package

@ccfly/setup-darwin-x64npm

@ccfly/setup-darwin-x64 is a confirmed malicious npm package (MAL-2026-12313) that steals credentials and exfiltrates sensitive data (malicious version 0.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ccfly/setup-darwin-x64 (npm)

MAL-2026-12313

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ccfly/setup-darwin-x64

What this malware does

The package ships a prebuilt darwin/x64 Mach-O binary containing a Go agent (module github.com/ccfly/rescue) that, when executed, connects to a hardcoded remote broker at cc.hn / ccfly over WebSocket (ws://ccfly, wss://, https://cc.hn) using github.com/gorilla/websocket, spawns a pseudo-terminal via github.com/creack/pty, and pipes the WebSocket stream into that PTY. Symbols include agent.serve, agent.startPTY, agent.waitAuthorized, agent.wsBase and unixPTY.Read/Write/Resize/Close, giving the remote party interactive shell control of the host. A second stage (setup.downloadCcfly, setup.fetchAndExtract, setup.npmTarballURL, setup.extractFromTarGz, setup.runCcflyInstall, setup.redeemEnrollToken, setup.(*brokerClient).escalateToRescue, with a rodata reference to https://registry.npmjs.org) fetches and executes a further ccfly npm tarball after the broker approves an enrollment token — the additional code executed on the host is chosen by the remote broker, not the installer. The binary also inspects shell RC files and /etc/hosts (setup.scanShellProfilesForProxy, setup.checkProxyResidue, setup.checkHostsResidue, setup.runEnvChecks, setup.envReport) and POSTs an environment report back to the broker (setup.(*brokerClient).post; rodata latest.zshrc, export.ccfly).

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

409d11825a61bed068425296e83dcc0c87427579f7b5d724ec52e5e87465f2b5

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ccfly/setup-darwin-x64 (version 0.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ccfly/setup-darwin-x64 across your stack and pipelines.
If you installed it — respond
@ccfly/setup-darwin-x64 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @ccfly/setup-darwin-x64 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-darwin-x64 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

No. @ccfly/setup-darwin-x64 on npm has been identified as a malicious package (version 0.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014797

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ccfly/setup-darwin-x64-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database