sjs-lint-build1 (npm) · Malicious Code
Affects sjs-lint-build1Source GCVE Database
Malicious package : remove sjs-lint-build1 and rotate any secrets on hosts that installed it.
Data as of 7 Jul 2026, 12:28 UTC
Malicious package
Published to npm · OSV MAL-2026-2528
What to do
Remove sjs-lint-build1 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 |
|---|---|---|
| npmsjs-lint-build1 | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
sjs-biginteger typosquats big.js on npm. Published April 7, 2026 by throwaway account vanes.s.p.orit.a, the package ships legitimate big.js source and hides its payload in a dependency: sjs-lint-build1. On install, the dependency’s postinstall hook fetches the attacker’s SSH public key from a C2 server, appends it to ~/.ssh/authorized_keys, opens firewall port 22, then collects SSH keys, environment variables, config files (.env, Solana id.json, config.toml), and system fingerprints. It exfiltrates the collected data to two Vercel-hosted C2 domains disguised as Cloudflare services. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cba6ed57b1eb82592650453ea703d44d9294be1c1c3316f4562ff4f197e6c0f6) The package sjs-lint-build1 was found to contain malicious code. ## Source: ghsa-malware (fc8bd742b46dcad52a23f2cef1c0c23ede56a1f36828c95a07b23ebef5c47715) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.