sextant-cli-linux-amd64npm
sextant-cli-linux-amd64 is a confirmed malicious npm package (MAL-2026-12029) that opens a backdoor for remote access (malicious version 0.0.1-rc34). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in sextant-cli-linux-amd64 (npm)
What this malware does
The package ships a single Linux x64 Go binary at bin/sxt that connects to a hardcoded operator relay at wss://relay.sextant.top, negotiates a WebRTC peer connection (pion), spawns a local PTY (github.com/creack/pty) against /bin/sh or /bin/bash, and pipes bytes received from the remote peer into that shell. This is a full interactive remote-shell backdoor: any host that installs and runs the binary is under shell-level control of whoever operates the relay. The package.json license field points at github.com/ddos798/claude_control, matching the internal Go module path 'claude_control' embedded in the binary, tying the shipped binary to the operator-controlled project.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sextant-cli-linux-amd64 (version 0.0.1-rc34). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sextant-cli-linux-amd64 across your stack and pipelines.
If you installed it — respond
sextant-cli-linux-amd64 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sextant-cli-linux-amd64 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-amd64 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-amd64-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.