orbitron-tui — a malicious AI-CLI impersonation that relays your API key, prompts and code to an attacker backend
The npm package orbitron-tui (publisher imjustbetterxd) poses as a “modular TUI backend for Orbitron” but routes the developer's authenticated AI traffic — API key, prompts and code — to an attacker-controlled backend (orbitron--pastelsjuice8t.replit.app / fireworks-endpoint--57crestcrepe.replit.app), with TLS verification disabled in later builds. Part of the AI-CLI Relay Campaign.
orbitron-tui is published to npm by imjustbetterxd and presents as a “modular TUI backend for Orbitron”. It is one of five packages in the AI-CLI Relay Campaign.
How the relay works. On use, the CLI reads the developer's LLM / provider API key — from environment variables (e.g. EXA_API_KEY, NVIDIA_API_KEY, provider config) and its own settings — 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 whoever operates the backend receives the API key and everything the developer sends to their “AI”.
Default backend: orbitron--pastelsjuice8t.replit.app / fireworks-endpoint--57crestcrepe.replit.app. The bin entry launches a bundled binary that carries the relay; the backend host rotated from orbitron--pastelsjuice8t.replit.app (0.1.x–0.4.x) to fireworks-endpoint--57crestcrepe.replit.app (1.0.x, the same host codebuff-cli and agent-free use).
TLS. Later builds set rejectUnauthorized: false / NODE_TLS_REJECT_UNAUTHORIZED for the relay connection, removing the last check on where the data actually goes.
All 84 published versions are malicious — the relay is present from the very first version (0.1.2), so there is no clean build. Versions: 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.1.10, 0.1.11, 0.1.12, 0.1.13, 0.1.14, 0.1.15, 0.1.16, 0.1.17, 0.1.18, 0.1.19, 0.1.20, 0.2.0–0.2.9, 0.3.0–0.3.24, 0.4.0–0.4.4, 1.0.1–1.0.29 (84 published versions in total).
Backend rotation: orbitron--pastelsjuice8t.replit.app for 0.1.2–0.4.4, then fireworks-endpoint--57crestcrepe.replit.app for 1.0.1–1.0.29. TLS-verify is intermittently disabled in the 0.x line and consistently disabled across the 1.0.x line.
orbitron-tui published to npm by imjustbetterxd as part of the cluster.orbitron--pastelsjuice8t.replit.app / fireworks-endpoint--57crestcrepe.replit.appbin/ launches a bundled binary that performs the relay (the host string is embedded in the build)Authorization: Bearer), chat prompts and code context sent to the CLIrejectUnauthorized:false / NODE_TLS_REJECT_UNAUTHORIZED)imjustbetterxd; GitHub payload host github.com/Marcus-Mok-GHPart of the AI-CLI Relay Campaign (CLR-2026-3048). Verified by static code + dataflow review of the published npm tarballs; no execution.