Which versions of sextant-cli-darwin-amd64 are malicious?

The following npm versions of sextant-cli-darwin-amd64 are flagged malicious: 0.0.1-rc34. Treat any of these as compromised.

How do I remediate sextant-cli-darwin-amd64 if I installed it?

sextant-cli-darwin-amd64 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.

I already installed sextant-cli-darwin-amd64 — how do I know if it already compromised me?

If sextant-cli-darwin-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.

Is sextant-cli-darwin-amd64 part of a known attack campaign?

Yes — sextant-cli-darwin-amd64 is associated with the IN-MAL-2026-011398 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sextant-cli-darwin-amd64 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sextant-cli-darwin-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-darwin-amd64 across your stack and pipelines.

Malicious package

sextant-cli-darwin-amd64npm

sextant-cli-darwin-amd64 is a confirmed malicious npm package (MAL-2026-12028) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1-rc34). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-12028

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sextant-cli-darwin-amd64

What this malware does

The package's sole shipped artifact bin/sxt is a Go binary that opens a WebSocket/WebRTC channel to hardcoded C2 endpoints wss://relay.sextant.top and https://relay.sextant.top/install and spawns a PTY driven by bytes arriving over that channel, providing full remote shell access on the installer's host (imports github.com/creack/pty, github.com/coder/websocket, github.com/pion/webrtc/v4). The binary additionally embeds the regex sk-ant-[a-z0-9]+-[A-Za-z0-9_-]{40,} together with references to CLAUDE_CONFIG_DIR, settings.local, api.anthropic.com/v1/models, and claude.ai, harvesting Anthropic API keys and Claude CLI configuration from the installer's home directory. Host reconnaissance is performed via http://ip-api.com/json/ with a full fields query for geolocation/ISP/proxy profiling, and strings referencing https://claude.ai/install.sh and https://registry.npmjs.org/sextant-cli/latest indicate a self-update / dropper channel that lets the operator swap payloads. package.json declares the license as SEE LICENSE IN https://github.com/ddos798/claude_control, self-identifying the tooling.

Malicious versions

1 flagged

0.0.1-rc34

Indicators of compromise (SHA-256)

4da71f2071285bfe8543d8aa7437f2b82111d95797f78ece2cf7498d02ff9cc1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sextant-cli-darwin-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-darwin-amd64 across your stack and pipelines.
If you installed it — respond
sextant-cli-darwin-amd64 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-darwin-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-darwin-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

No. sextant-cli-darwin-amd64 on npm has been identified as a malicious package (version 0.0.1-rc34 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011398

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sextant-cli-darwin-amd64-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database