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

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

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

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

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

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

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

Yes — sextant-cli-darwin-arm64 is associated with the IN-MAL-2026-011364 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-arm64 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-arm64 (version 0.0.1-rc24). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sextant-cli-darwin-arm64 across your stack and pipelines.

Malicious package

sextant-cli-darwin-arm64npm

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

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

MAL-2026-11997

Immediate action

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

npm uninstall sextant-cli-darwin-arm64

What this malware does

The tarball ships a Mach-O Go binary at bin/sxt built from the module github.com/ddos798/claude_control. The binary statically links a WebSocket client (github.com/coder/websocket), a PTY library (github.com/creack/pty), and shell invocations of /bin/sh and /bin/bash, and it connects to a hardcoded C2 endpoint at wss://relay.sextant.top. This is a network-source-to-PTY-sink dataflow: a remote operator at relay.sextant.top can drive an interactive shell on the host running sxt. The binary additionally contains a regex targeting Anthropic API keys (sk-ant-[a-z0-9]+-[A-Za-z0-9_-]{40,}), reads CLAUDE_CONFIG_DIR and ~/.claude, and reaches https://api.anthropic.com/v1/models — targeted theft of Claude credentials from the host. At startup the binary fingerprints the host via http://ip-api.com/json/ (public IP, country, city, timezone) plus os.Hostname and POSTs to https://relay.sextant.top/install. The package mimics the naming convention of a platform-specific optional dependency (like @esbuild/darwin-arm64) so a parent sextant-cli package pulls it as a mandatory arm64 sub-binary, and the package.json license URL points at github.com/ddos798/claude_control — the upstream module is self-describing.

Malicious versions

1 flagged

0.0.1-rc24

Indicators of compromise (SHA-256)

395a381c321ebe4cfb276cf354d97d45a8fde8f9882b2d31471a7d6ac5e74229

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-arm64 (version 0.0.1-rc24). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sextant-cli-darwin-arm64 across your stack and pipelines.
If you installed it — respond
sextant-cli-darwin-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-darwin-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-darwin-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

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

Campaign

IN-MAL-2026-011364

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database