Malicious code in next-bignumber.js (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (cac4f683d978bbfcebc9eb96a314e21c97d5d7874f023377d78c51697ea8c074) 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 next-bignumber.js npm package version 1.0.0 is identified as containing malicious code. Installation or execution of this package results in a full compromise of the host system, allowing an attacker to gain control. Due to the severity of the compromise, all sensitive credentials stored on the system should be considered exposed and must be rotated from a different, secure environment. Simply removing the package does not ensure complete remediation, as the attacker may have deployed additional persistent malicious components.
Potential Impact
Full system compromise on any computer with next-bignumber.js version 1.0.0 installed or running. All secrets and keys stored on the system are at risk of exposure. The attacker may maintain persistent access beyond the presence of the malicious package itself.
Mitigation Recommendations
Remove the next-bignumber.js package version 1.0.0 immediately. Rotate all secrets and keys from a separate, uncompromised system. Conduct a thorough investigation and remediation of the affected system, as removal of the package alone does not guarantee elimination of all malicious artifacts.
Malicious code in next-bignumber.js (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (cac4f683d978bbfcebc9eb96a314e21c97d5d7874f023377d78c51697ea8c074) 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 next-bignumber.js npm package version 1.0.0 is identified as containing malicious code. Installation or execution of this package results in a full compromise of the host system, allowing an attacker to gain control. Due to the severity of the compromise, all sensitive credentials stored on the system should be considered exposed and must be rotated from a different, secure environment. Simply removing the package does not ensure complete remediation, as the attacker may have deployed additional persistent malicious components.
Potential Impact
Full system compromise on any computer with next-bignumber.js version 1.0.0 installed or running. All secrets and keys stored on the system are at risk of exposure. The attacker may maintain persistent access beyond the presence of the malicious package itself.
Mitigation Recommendations
Remove the next-bignumber.js package version 1.0.0 immediately. Rotate all secrets and keys from a separate, uncompromised system. Conduct a thorough investigation and remediation of the affected system, as removal of the package alone does not guarantee elimination of all malicious artifacts.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6855
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-8vr6-7cjp-qgrj"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c343327e9c797195fa8f5
Added to database: 07/06/2026, 23:03:15 UTC
Last enriched: 07/06/2026, 23:24:57 UTC
Last updated: 07/29/2026, 20:33:59 UTC
Views: 31
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.