orbitron-cli

{"modified":"2026-09-04T00:00:00Z","published":"2026-09-04T00:00:00Z","schema_version":"1.7.4","id":"MAL-2026-16012","summary":"Malicious code in orbitron-cli (npm)","details":"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`.\n\nThe 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.","affected":[{"package":{"ecosystem":"npm","name":"orbitron-cli"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"}]}]}],"references":[{"type":"ADVISORY","url":"https://research.codelake.dev/advisories/clr-2026-3050-orbitron-cli"},{"type":"ADVISORY","url":"https://research.codelake.dev/advisories/clr-2026-3048-ai-cli-relay-campaign"}],"credits":[{"name":"codelake Research","type":"FINDER","contact":["https://research.codelake.dev/advisories/clr-2026-3050-orbitron-cli"]}],"database_specific":{"iocs":{"domains":["orbitron--pastelsjuice8t.replit.app"]}}}