orbit-nebula-editor (npm) · Malicious Code
Affects orbit-nebula-editorSource GCVE Database
Malicious package : remove orbit-nebula-editor and rotate any secrets on hosts that installed it.
Data as of 18 Nov 2026, 02:15 UTC
Malicious package
Published to npm · OSV MAL-2025-190777
What to do
Remove orbit-nebula-editor 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 |
|---|---|---|
| npmorbit-nebula-editor | 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 npm package orbit-nebula-editor version 1.0.2 contains malicious code introduced by the Sha1-Hulud: The Second Coming NPM worm. This malware steals tokens and credentials, publishes them to GitHub, propagates itself to other NPM packages owned by the user, and establishes persistence via a GitHub action. It may also destroy the user's home directory. Any system with this package installed should be considered fully compromised.
References
- github.com/advisories/GHSA-3x7w-5rj2-h2gj (opens in a new tab)
- aikido.dev/blog/shai-hulud-strikes-again-hitting-zapier-ensdomains (opens in a new tab)
- wiz.io/blog/shai-hulud-2-0-ongoing-supply-chain-attack (opens in a new tab)
- stepsecurity.io/blog/sha1-hulud-the-second-coming-zapier-ens-domains-and-other-prominent-npm-packages-compromised (opens in a new tab)