macos-ci-utilsnpm
Malicious code in macos-ci-utils (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On first require of the package, index.js decodes a base64-encoded URL (https://api.ingress-hub.com/cdn/assets/update.pkg) and downloads the response to ~/Library/Application Support/.node_cache/.runtime, chmods it 0755, writes a.lock sentinel for idempotency, and spawns it detached with stdio ignored. There is no hash or signature verification, the destination domain is unrelated to the package's stated publisher, and the staged file uses a hidden dot-name. The dropper code uses obfuscation patterns inconsistent with a legitimate utility: single-letter identifiers (_D, _N, _P, _F, _U, _A), a base64-encoded URL string, a forged Mozilla/5.0 macOS User-Agent, and darwin-only platform gating. The README advertises a passive 'getStatus()' validation API and does not mention any network fetch or binary execution; the code's behavior contradicts the documentation. Any installer that requires this package on macOS executes attacker-controlled bytes from api.ingress-hub.com with full user privileges.
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 macos-ci-utils (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging macos-ci-utils across your stack and pipelines.
If you installed it — respond
Remove macos-ci-utils 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 macos-ci-utils 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 macos-ci-utils 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 macos-ci-utils-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.