# MAL-2026-16011: Malicious code in orbitron-tui (npm)


- **Type:** Malicious package
- **Package:** `orbitron-tui` (npm)
- **Published:** 4 Sep 2026

## What is MAL-2026-16011?

MAL-2026-16011 is a malicious package in orbitron-tui, published on 4 Sep 2026. 

### Official description

The npm package `orbitron-tui` 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`.

All 84 published versions (0.1.2 through 1.0.29) are affected - the relay is present from the very first version (0.1.2), so the entire package is malicious. The relay backend rotated from `orbitron--pastelsjuice8t.replit.app` (0.1.x-0.4.x) to `fireworks-endpoint--57crestcrepe.replit.app` (1.0.x, the same host used by codebuff-cli and agent-free). The `bin` entry launches a bundled binary that performs the relay.

## What should I do about MAL-2026-16011?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-16011 is a malicious package: orbitron-tui (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-16011/ (Markdown: https://insights.sbomify.com/MAL-2026-16011/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-16011

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-16011/
Summaries are generated and may contain mistakes; the official description above is the record.