velabuild (npm) · Malicious Code
Affects velabuildSource GCVE Database
Malicious package : remove velabuild and rotate any secrets on hosts that installed it.
Data as of 7 Aug 2026, 15:41 UTC
Malicious package
Published to npm · OSV MAL-2026-13493
What to do
Remove velabuild 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 |
|---|---|---|
| npmvelabuild | 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 velabuild npm package contains embedded malicious code that includes a base64-encoded RSA private key used to establish SSH connections to an attacker's server. This private key is identical for every installer, granting anyone who installs the package valid SSH credentials to the attacker's server. While the package does not execute attacker-controlled code during installation or modify the installer's filesystem beyond a temporary key file, it enables remote command execution via SSH when specific subcommands are invoked. The package's signup and login commands transmit user credentials over this SSH tunnel. Systems with this package installed should be considered fully compromised.
References
- github.com/advisories/GHSA-q7w3-723m-252j (opens in a new tab)
- npmjs.com/package/velabuild/v/2.1.1 (opens in a new tab)
- npmjs.com/package/velabuild/v/1.0.1 (opens in a new tab)
- npmjs.com/package/velabuild/v/2.0.0 (opens in a new tab)
- npmjs.com/package/velabuild/v/1.0.0 (opens in a new tab)
- npmjs.com/package/velabuild/v/1.0.3 (opens in a new tab)
- npmjs.com/package/velabuild/v/1.0.2 (opens in a new tab)
- npmjs.com/package/velabuild/v/2.2.0 (opens in a new tab)
- npmjs.com/package/velabuild/v/2.1.0 (opens in a new tab)