Which versions of orbitron-cli are malicious?

Every published version of orbitron-cli on npm is considered malicious. Remove the package entirely.

How do I remediate orbitron-cli if I installed it?

orbitron-cli 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 orbitron-cli — how do I know if it already compromised me?

If orbitron-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find orbitron-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for orbitron-cli (all published versions).

Malicious package

orbitron-clinpm

Advisory published Sep 4, 2026Updated Sep 11, 2026

orbitron-cli is a confirmed malicious npm package (MAL-2026-16012) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in orbitron-cli (npm)

MAL-2026-16012

Immediate action

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

npm uninstall orbitron-cli

What this malware does

The npm package orbitron-cli is malicious. It is one of five AI-coding-CLI impersonations published to npm by imjustbetterxd (a coordinated campaign). On use, the CLI reads the developer's LLM/provider API key - from environment variables (e.g. EXA_API_KEY, NVIDIA_API_KEY) and its own config - and routes the authenticated AI requests to an attacker-controlled default backend instead of the legitimate provider. Each request carries the user's Authorization: Bearer <apiKey> together with the chat prompt and code context, so the backend operator receives the API key and everything the developer sends to their assistant. Later builds set rejectUnauthorized: false / NODE_TLS_REJECT_UNAUTHORIZED for the relay connection. Payloads/updates are hosted on the GitHub account Marcus-Mok-GH.

The single published version (1.0.1) is affected. It is a bun launcher: bin/orbitron imports dist/index.js, which uses dist/backend-client.js (holds the API key) and a bundled dist/orbitron binary; the relay backend is orbitron--pastelsjuice8t.replit.app. dist/update.js auto-updates from orbitron-tui's npm latest and spawns the bundled binary - the cluster is self-linked.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for orbitron-cli (all published versions).
If you installed it — respond
orbitron-cli 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 orbitron-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. orbitron-cli on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

codelake Research · finder

Detect & block this

O3 blocks orbitron-cli-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