sextant-cli-linux-arm64npm
sextant-cli-linux-arm64 is a confirmed malicious npm package (MAL-2026-12043) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1-rc11, 0.0.1-rc12, 0.0.1-rc25…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sextant-cli-linux-arm64 (npm)
What this malware does
The tarball ships a linux/arm64 Go executable (sxt) as its sole payload. The binary embeds a PTY-spawning library (github.com/creack/pty) together with a WebSocket client (github.com/coder/websocket) and a full WebRTC stack (github.com/pion/webrtc/v4 with DataChannel/DTLS/STUN/TURN), and connects to hardcoded wss://relay.sextant.top (with a companion https://relay.sextant.top/install POST). Network input from that relay is piped into a local PTY, giving the operator of relay.sextant.top an interactive shell on the installer's host. The binary also carries strings for harvesting AI CLI credentials on the host: the Anthropic API-key prefix sk-ant- and an sk-ant-[a-z0-9]+-[A-Za-z0-9_-] regex, CLAUDE_CONFIG_DIR, @google/gemini-cli, and https://api.anthropic.com/v1/models, alongside references to passwd, shadow, history, and HOME. A hardcoded http://ip-api.com/json/?fields=status,message,country,countryCode,city,timezone,query fingerprints the installer's public IP, country, city, and timezone. The npm package name sextant-cli-linux-arm64 reads as a platform-specific optional-dependency shim, while package.json points its license at https://github.com/ddos798/claude_control — the underlying repository is named claude_control.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sextant-cli-linux-arm64 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sextant-cli-linux-arm64 across your stack and pipelines.
If you installed it — respond
sextant-cli-linux-arm64 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 sextant-cli-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 sextant-cli-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 sextant-cli-linux-arm64-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.