Malicious code in sjs-biginteger (npm)
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 (ad825f5a8f4892374c8e1f8a4d1e5e84e28419eb656035667c4c9d8964966f6d) The package sjs-biginteger was found to contain malicious code. ## Source: ghsa-malware (fcae78c041d8a88f2709f71788ac5b4e4e5f5f17862874f05e4a3742e9f4f464) 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.
AI Analysis
Technical Summary
The sjs-biginteger npm package, published by a throwaway account, is a malicious typosquat of the legitimate big.js package. It includes a hidden dependency (sjs-lint-build1) that runs a postinstall script to establish persistent unauthorized SSH access by adding the attacker’s SSH public key to authorized_keys and opening port 22. It then harvests sensitive credentials and configuration files (.env, Solana id.json, config.toml) along with system fingerprints and exfiltrates this information to attacker-controlled C2 servers hosted on Vercel and disguised as Cloudflare services. This results in full system compromise. Removal of the package alone does not guarantee remediation due to potential persistence mechanisms.
Potential Impact
Systems with sjs-biginteger versions 5.0.5 or 5.0.6 installed are fully compromised. The attacker gains persistent SSH access, can open firewall ports, and exfiltrate sensitive credentials and configuration data. This compromises confidentiality, integrity, and potentially availability of the affected systems. All secrets and keys stored on the compromised system should be considered exposed and rotated immediately from a secure environment.
Mitigation Recommendations
Immediate removal of the sjs-biginteger package versions 5.0.5 and 5.0.6 is required. However, because the attacker gains persistent SSH access and collects sensitive data, removal alone may not fully remediate the compromise. All secrets, SSH keys, and credentials stored on the affected system must be rotated from a different, secure machine. Conduct a thorough incident response to identify and remove any additional backdoors or persistence mechanisms. Monitor for suspicious SSH access and network activity. Patch status is not applicable as this is a malicious package, not a vulnerability with an official fix.
Malicious code in sjs-biginteger (npm)
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 (ad825f5a8f4892374c8e1f8a4d1e5e84e28419eb656035667c4c9d8964966f6d) The package sjs-biginteger was found to contain malicious code. ## Source: ghsa-malware (fcae78c041d8a88f2709f71788ac5b4e4e5f5f17862874f05e4a3742e9f4f464) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The sjs-biginteger npm package, published by a throwaway account, is a malicious typosquat of the legitimate big.js package. It includes a hidden dependency (sjs-lint-build1) that runs a postinstall script to establish persistent unauthorized SSH access by adding the attacker’s SSH public key to authorized_keys and opening port 22. It then harvests sensitive credentials and configuration files (.env, Solana id.json, config.toml) along with system fingerprints and exfiltrates this information to attacker-controlled C2 servers hosted on Vercel and disguised as Cloudflare services. This results in full system compromise. Removal of the package alone does not guarantee remediation due to potential persistence mechanisms.
Potential Impact
Systems with sjs-biginteger versions 5.0.5 or 5.0.6 installed are fully compromised. The attacker gains persistent SSH access, can open firewall ports, and exfiltrate sensitive credentials and configuration data. This compromises confidentiality, integrity, and potentially availability of the affected systems. All secrets and keys stored on the compromised system should be considered exposed and rotated immediately from a secure environment.
Mitigation Recommendations
Immediate removal of the sjs-biginteger package versions 5.0.5 and 5.0.6 is required. However, because the attacker gains persistent SSH access and collects sensitive data, removal alone may not fully remediate the compromise. All secrets, SSH keys, and credentials stored on the affected system must be rotated from a different, secure machine. Conduct a thorough incident response to identify and remove any additional backdoors or persistence mechanisms. Monitor for suspicious SSH access and network activity. Patch status is not applicable as this is a malicious package, not a vulnerability with an official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-2527
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-38ww-f26r-f8w7"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c341227e9c797195f7d62
Added to database: 07/06/2026, 23:02:42 UTC
Last enriched: 07/06/2026, 23:17:54 UTC
Last updated: 07/23/2026, 06:07:08 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.