Malicious code in bjs-biginteger (npm)
big.js typosquat campaign - SSH backdoor implantation, credential and crypto wallet theft --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ce3bc89babfc42de2e7df569ebf26d41dcc13469a19895aa4144c2625ddbd87b) The package bjs-biginteger was found to contain malicious code. ## Source: ghsa-malware (fa9a45f5b0c330db1b8359e0dc4dfe9151c922ee47424de29c565cbd5e2fc3d0) 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 bjs-biginteger npm package, specifically versions 5.0.5 and 5.0.6, was identified as containing malicious code as part of a typosquatting campaign mimicking the legitimate big.js package. The malicious payload includes implantation of an SSH backdoor and theft of credentials and cryptocurrency wallets. Due to the nature of the compromise, systems with this package installed are considered fully compromised, and removing the package alone may not eliminate all malicious components.
Potential Impact
Systems with the affected versions of bjs-biginteger installed are at risk of full compromise, including unauthorized remote access via an SSH backdoor and theft of sensitive credentials and cryptocurrency wallets. This can lead to loss of control over the system and significant data and asset theft.
Mitigation Recommendations
Remove the bjs-biginteger package versions 5.0.5 and 5.0.6 immediately. Rotate all secrets, credentials, and cryptographic keys from a separate, trusted system to prevent further unauthorized access. Treat any affected system as fully compromised and consider rebuilding or thoroughly cleaning the environment to ensure removal of all malicious artifacts.
Malicious code in bjs-biginteger (npm)
Description
big.js typosquat campaign - SSH backdoor implantation, credential and crypto wallet theft --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ce3bc89babfc42de2e7df569ebf26d41dcc13469a19895aa4144c2625ddbd87b) The package bjs-biginteger was found to contain malicious code. ## Source: ghsa-malware (fa9a45f5b0c330db1b8359e0dc4dfe9151c922ee47424de29c565cbd5e2fc3d0) 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 bjs-biginteger npm package, specifically versions 5.0.5 and 5.0.6, was identified as containing malicious code as part of a typosquatting campaign mimicking the legitimate big.js package. The malicious payload includes implantation of an SSH backdoor and theft of credentials and cryptocurrency wallets. Due to the nature of the compromise, systems with this package installed are considered fully compromised, and removing the package alone may not eliminate all malicious components.
Potential Impact
Systems with the affected versions of bjs-biginteger installed are at risk of full compromise, including unauthorized remote access via an SSH backdoor and theft of sensitive credentials and cryptocurrency wallets. This can lead to loss of control over the system and significant data and asset theft.
Mitigation Recommendations
Remove the bjs-biginteger package versions 5.0.5 and 5.0.6 immediately. Rotate all secrets, credentials, and cryptographic keys from a separate, trusted system to prevent further unauthorized access. Treat any affected system as fully compromised and consider rebuilding or thoroughly cleaning the environment to ensure removal of all malicious artifacts.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-2879
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-jjf3-wfhw-qhx4"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c343227e9c797195fa7d6
Added to database: 07/06/2026, 23:03:14 UTC
Last enriched: 07/07/2026, 00:06:41 UTC
Last updated: 07/18/2026, 17:27:21 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.