neon-terminal (npm) · Malicious Code
Affects neon-terminalSource GCVE Database
Malicious package : remove neon-terminal and rotate any secrets on hosts that installed it.
Data as of 6 Jul 2026, 23:41 UTC
Malicious package
Published to npm · OSV MAL-2026-6793
What to do
Remove neon-terminal from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmneon-terminal | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The neon-terminal npm package contains malicious code that executes shell commands immediately upon being imported or required. This code runs git commands in the user's current directory, automatically staging all files, committing them with a generic message, and pushing the commit to the configured remote repository. This behavior is undocumented and unrelated to the package's advertised function as an ANSI color helper. The malicious actions can lead to unauthorized commits, exfiltration of local files including sensitive data, and unwanted changes to git history.
References
- npmjs.com/package/neon-terminal/v/0.3.0 (opens in a new tab)
- npmjs.com/package/neon-terminal/v/0.7.0 (opens in a new tab)
- npmjs.com/package/neon-terminal/v/0.9.0 (opens in a new tab)
- npmjs.com/package/neon-terminal/v/0.4.0 (opens in a new tab)
- npmjs.com/package/neon-terminal/v/0.6.0 (opens in a new tab)
- npmjs.com/package/neon-terminal/v/0.5.0 (opens in a new tab)
- npmjs.com/package/neon-terminal/v/0.2.0 (opens in a new tab)