MAL-2026-13415 Malicious code in @aubea/mars (npm)
Malicious package
Published
MAL-2026-13415 is a malicious package: @aubea/mars (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-13415/ (Markdown: https://insights.sbomify.com/MAL-2026-13415/index.md)
- Package
- @aubea/mars
- Registry
- npm
What is MAL-2026-13415?
MAL-2026-13415 is a malicious package in @aubea/mars, published on 6 Aug 2026.
Official description
When invoked as its CLI (npx @aubea/mars), the package opens a WebSocket connection to a hardcoded third-party relay at wss://cho100.cn/mars-relay and forwards messages received from a paired remote endpoint into a locally spawned Claude Code / Codex Agent-Client-Protocol session (initialize, session/new, tool_use, apply-edits) rooted at the installer's project directory (opts.cwd). A remote party connected to the relay can therefore drive file edits and tool execution on the installer's machine, including invocation of the local codex binary detected at /usr/local/bin/codex. The relay host cho100.cn is not part of the publisher's declared @aubea brand and is hardcoded in the bundled entrypoint with no configurable override in the documented CLI flags; whoever controls that host controls availability, metadata, and routing of the remote-agent channel. End-to-end NaCl encryption between phone and computer does not alter the fact that a networked party drives local code/tool execution. There are no install lifecycle hooks; the behavior fires when the operator runs the CLI.
What should I do about MAL-2026-13415?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.