Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in sextant-cli-linux-amd64 (npm)

The npm package sextant-cli-linux-amd64 contained a malicious Linux amd64 Go binary (bin/sxt) that implements a remote-controlled interactive shell via WebRTC and WebSocket, allowing attackers to execute arbitrary commands on infected systems. The binary connects to a hardcoded relay at https://relay.sextant.top/install and includes host fingerprinting via IP geolocation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system that installed the malicious sextant-cli-linux-amd64 npm package
Ecosystems
Attack vectors
Affected entities
  • sextant-cli-linux-amd64npm package containing malicious Linux amd64 Go binary

The npm package sextant-cli-linux-amd64 shipped a malicious Linux amd64 Go binary at bin/sxt with internal module identifier 'claude_control'. The binary was not disclosed in the package metadata and represents a supply chain compromise via npm's platform-specific binary distribution mechanism.\n\nThe payload implements a remote-controlled interactive shell by statically linking pseudo-terminal spawning (github.com/creack/pty), WebSocket communication (github.com/coder/websocket), and the full WebRTC stack (github.com/pion/webrtc/v4) with datachannel, ICE, DTLS, STUN, and TURN support. The binary connects to a hardcoded relay at https://relay.sextant.top/install, allowing a remote peer that reaches the relay to drive a full TTY on the installer's machine.\n\nThe binary also references http://ip-api.com/json/ to fingerprint the host at startup. The package name does not reference 'claude_control' or the associated GitHub user 'ddos798', obscuring the true nature of the payload.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF malicious-packages project.

Indicators of compromise

Packages
  • sextant-cli-linux-amd64
Domains
  • relay.sextant.top
  • ip-api.com

Remediation

  • Immediately uninstall sextant-cli-linux-amd64 from all systems
  • Audit npm package.json and lock files for any installations of sextant-cli-linux-amd64
  • Assume any system that installed this package has been compromised; perform forensic analysis and credential rotation
  • Monitor for outbound connections to relay.sextant.top and ip-api.com from affected systems
  • Review npm audit logs and consider enabling 2FA on npm accounts
  • Use npm package integrity verification and consider using private registries or package allowlists

Sources

  1. GitHub Advisory GHSA-g6xw-m38g-gq9x · GitHub Advisory Database

Cite this entry

"Malicious code in sextant-cli-linux-amd64 (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-amd64-npm-1b1oyq

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. 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
  2. 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
  3. 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
  4. 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