Malicious code in sextant-cli-linux-arm64 (npm)
The npm package sextant-cli-linux-arm64 contained a malicious Linux ARM64 Go binary that establishes a reverse shell to a hardcoded WebSocket relay, harvests AI CLI credentials, and fingerprints the host system. The package was identified by Amazon Inspector and credited to OpenSSF.
- Disclosed
- Last updated
- Blast radius
- Developers and systems installing sextant-cli-linux-arm64 from npm, particularly those on ARM64 Linux systems.
- Ecosystems
- Attack vectors
- Affected entities
- sextant-cli-linux-arm64npm package containing malicious Go binary
The npm package sextant-cli-linux-arm64 was found to contain malicious code in the form of a Linux ARM64 Go executable (sxt). The binary was designed to establish an interactive reverse shell connection to a hardcoded WebSocket relay at wss://relay.sextant.top, allowing remote operators to execute arbitrary commands on infected systems.\n\nThe malicious binary includes multiple capabilities beyond remote shell access. It embeds libraries for PTY spawning (github.com/creack/pty), WebSocket communication (github.com/coder/websocket), and a full WebRTC stack (github.com/pion/webrtc/v4) with DataChannel, DTLS, STUN, and TURN support. The binary also contains hardcoded strings and regex patterns for harvesting AI CLI credentials, specifically targeting Anthropic API keys (prefix sk-ant-) and Google Gemini CLI credentials, along with references to system files like passwd, shadow, and shell history.\n\nAdditional reconnaissance capabilities include IP geolocation fingerprinting via http://ip-api.com/json/, which collects the installer's public IP, country, city, and timezone. The package.json file references a license URL pointing to https://github.com/ddos798/claude_control, indicating the underlying malicious repository.\n\nThe package name sextant-cli-linux-arm64 was designed to appear as a legitimate platform-specific optional dependency shim, making it more likely to be installed without scrutiny. The incident was identified by Amazon Inspector and credited to the OpenSSF malicious packages project.
Indicators of compromise
- Packages
- sextant-cli-linux-arm64
- Domains
- relay.sextant.top
- ip-api.com
Remediation
- Immediately uninstall sextant-cli-linux-arm64 from all systems
- Audit npm package.json and lock files for any installations of sextant-cli-linux-arm64
- Rotate all AI CLI credentials (Anthropic, Google Gemini) that may have been exposed
- Review system logs and network connections for evidence of connections to relay.sextant.top
- Scan systems for the malicious sxt binary and remove any instances
- Monitor for unauthorized shell access or command execution on affected systems
- Review git history and shell history for suspicious activity
- Consider full system reimaging for critical systems that may have been compromised
Sources
- GitHub Advisory GHSA-3w3q-fqgj-f36f · GitHub Advisory Database
Cite this entry
"Malicious code in sextant-cli-linux-arm64 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malicious-code-in-sextant-cli-linux-arm64-npm-17q20e
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in santana-baileys (npm)
Malicious code discovered in santana-baileys npm package that covertly relays WhatsApp messaging data to an attacker-controlled endpoint (https://fiora.nixel.my.id/) via obfuscated character-code reconstruction in the message-send code path.
npmCompromised package - resolvedcritical
Malicious code in elephant-tusk-runner (npm)
The npm package elephant-tusk-runner contained malicious code that exposed a remote shell and remote code execution surface via an unauthenticated Express + WebSocket server binding to 0.0.0.0:4201 with fully open CORS. Any peer able to reach the port could execute arbitrary commands on the host.
npmCompromised package - resolvedcritical
Malicious code in @cats-cdf/browser-metrics-meter (npm)
The npm package @cats-cdf/browser-metrics-meter contained malicious code in its preinstall lifecycle script that exfiltrated system reconnaissance data (username, hostname, public IP) to an OAST collector domain. The package executed this behavior unconditionally on installation without consent or documented purpose.
npmCompromised package - resolvedcritical
Malicious code in @ks-video/kwai-player-web (npm)
The npm package @ks-video/kwai-player-web contained malicious code in its postinstall hook that exfiltrated system reconnaissance data (hostname, username, working directory, network interfaces, environment variable names) over plain HTTP to an unrelated third-party domain. The package has no legitimate relationship to the declared publisher Kwai/@ks-video.
npmCompromised package