Malicious code in crypto-base58 (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7da752b2532b67e824f8904ffce7618b074a6a58746099b36b4ee547d936c8d) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (49f3c1614d1fdad83e61dbc8708dfa64e8d7837ed13148e124fdd2d464c931d5) 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 'crypto-base58' npm package in versions 1.0.0, 1.0.1, and 1.0.4 has been identified as containing malicious code or relying on a dependency that includes malicious code. This malicious code can fully compromise any computer where the package is installed or running, potentially exposing all stored secrets and keys. The advisory indicates that simply removing the package may not fully remediate the compromise, as the attacker may have established persistent control.
Potential Impact
Systems with the affected versions of 'crypto-base58' installed or running are considered fully compromised. Attackers may have gained full control over the system, risking exposure and theft of sensitive data such as secrets and cryptographic keys. This can lead to severe security breaches and loss of confidentiality and integrity.
Mitigation Recommendations
Immediate removal of the affected 'crypto-base58' package versions (1.0.0, 1.0.1, 1.0.4) is recommended. However, because the system may be fully compromised, all secrets and keys stored on the system should be rotated from a different, secure computer. Additional remediation steps may be necessary to ensure complete eradication of malicious software. No official patch or fix is currently available; users should avoid using these versions.
Malicious code in crypto-base58 (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b7da752b2532b67e824f8904ffce7618b074a6a58746099b36b4ee547d936c8d) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (49f3c1614d1fdad83e61dbc8708dfa64e8d7837ed13148e124fdd2d464c931d5) 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 'crypto-base58' npm package in versions 1.0.0, 1.0.1, and 1.0.4 has been identified as containing malicious code or relying on a dependency that includes malicious code. This malicious code can fully compromise any computer where the package is installed or running, potentially exposing all stored secrets and keys. The advisory indicates that simply removing the package may not fully remediate the compromise, as the attacker may have established persistent control.
Potential Impact
Systems with the affected versions of 'crypto-base58' installed or running are considered fully compromised. Attackers may have gained full control over the system, risking exposure and theft of sensitive data such as secrets and cryptographic keys. This can lead to severe security breaches and loss of confidentiality and integrity.
Mitigation Recommendations
Immediate removal of the affected 'crypto-base58' package versions (1.0.0, 1.0.1, 1.0.4) is recommended. However, because the system may be fully compromised, all secrets and keys stored on the system should be rotated from a different, secure computer. Additional remediation steps may be necessary to ensure complete eradication of malicious software. No official patch or fix is currently available; users should avoid using these versions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6920
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-frf3-wxv2-p559"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4f6c7068715ace4315aa19
Added to database: 07/09/2026, 09:40:00 UTC
Last enriched: 07/09/2026, 10:06:55 UTC
Last updated: 07/31/2026, 04:09:09 UTC
Views: 64
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.
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.