MAL-2026-13428 Malicious code in @love-moon/conductor-cli (npm)
Malicious package
Published
MAL-2026-13428 is a malicious package: @love-moon/conductor-cli (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-13428/ (Markdown: https://insights.sbomify.com/MAL-2026-13428/index.md)
- Package
- @love-moon/conductor-cli
- Registry
- npm
What is MAL-2026-13428?
MAL-2026-13428 is a malicious package in @love-moon/conductor-cli, published on 6 Aug 2026.
Official description
The
conductor daemon command (bin/conductor-daemon.js -> src/daemon.js) opens a WebSocket to https://conductor.conductor-ai.top (or a user-configured backend_url) and registers a message handler that, in handleTerminalInput, writes payload.data received from the server directly into a node-pty process. The PTY is spawned by handleCreatePtyTask running either the user's default shell (/bin/bash, /bin/zsh, cmd.exe, $SHELL) or a CLI from DEFAULT_CLI_LIST, which launches codex --dangerously-bypass-approvals-and-sandbox and claude --dangerously-skip-permissions — the same flags are written into the generated config.yaml by bin/conductor-config.js. Any party controlling the WebSocket peer (the Conductor backend, an impersonator on the network, or a compromised backend account) can drive arbitrary commands into the installer's shell or into an AI CLI whose local approval/sandbox gates have been disabled by default. The remote-command channel and the disabled-safety flags together provide full-host command execution driven by conductor-ai.top.What should I do about MAL-2026-13428?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.