Malicious code in bs58-12 (npm)
The npm package bs58-12 masquerades as the legitimate bs58 base58 library but is a thin wrapper that depends on another suspicious package, base65-12x. While bs58-12 itself does not contain direct malicious code such as exfiltration or destructive scripts, the risk depends on the behavior of base65-12x, which has not been analyzed here. Security sources warn that any system with bs58-12 installed should be considered fully compromised, recommending immediate secret and key rotation and removal of the package. Complete remediation cannot be guaranteed by removal alone due to potential persistent compromise.
AI Analysis
Technical Summary
The bs58-12 npm package impersonates the popular bs58 library by copying its README and advertising installation similarly, but its code merely requires the base65-12x package. The package bs58-12 itself does not perform direct malicious actions during install or runtime, but the dependency base65-12x is suspicious and unexamined. Security advisories classify bs58-12 as malicious, advising that systems with it installed are fully compromised and require secret/key rotation and package removal. No CVSS score or detailed technical exploit data is available.
Potential Impact
Systems with bs58-12 installed are considered fully compromised, implying that attackers may have gained full control. All secrets and keys stored on such systems should be rotated immediately from a separate, trusted environment. Removing the package is necessary but may not fully remove all malicious components or backdoors introduced by the dependency base65-12x or other payloads.
Mitigation Recommendations
Remove the bs58-12 package immediately. Rotate all secrets, credentials, and keys from a different, uncompromised system. Because full compromise is likely, consider rebuilding affected systems from known good backups or reinstalling the operating system. Monitor for any suspicious activity that may indicate persistent threats. Patch status is not confirmed; no official fix or update is indicated. Check vendor advisories or npm security notices for updates on remediation.
Malicious code in bs58-12 (npm)
Description
The npm package bs58-12 masquerades as the legitimate bs58 base58 library but is a thin wrapper that depends on another suspicious package, base65-12x. While bs58-12 itself does not contain direct malicious code such as exfiltration or destructive scripts, the risk depends on the behavior of base65-12x, which has not been analyzed here. Security sources warn that any system with bs58-12 installed should be considered fully compromised, recommending immediate secret and key rotation and removal of the package. Complete remediation cannot be guaranteed by removal alone due to potential persistent compromise.
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 bs58-12 npm package impersonates the popular bs58 library by copying its README and advertising installation similarly, but its code merely requires the base65-12x package. The package bs58-12 itself does not perform direct malicious actions during install or runtime, but the dependency base65-12x is suspicious and unexamined. Security advisories classify bs58-12 as malicious, advising that systems with it installed are fully compromised and require secret/key rotation and package removal. No CVSS score or detailed technical exploit data is available.
Potential Impact
Systems with bs58-12 installed are considered fully compromised, implying that attackers may have gained full control. All secrets and keys stored on such systems should be rotated immediately from a separate, trusted environment. Removing the package is necessary but may not fully remove all malicious components or backdoors introduced by the dependency base65-12x or other payloads.
Mitigation Recommendations
Remove the bs58-12 package immediately. Rotate all secrets, credentials, and keys from a different, uncompromised system. Because full compromise is likely, consider rebuilding affected systems from known good backups or reinstalling the operating system. Monitor for any suspicious activity that may indicate persistent threats. Patch status is not confirmed; no official fix or update is indicated. Check vendor advisories or npm security notices for updates on remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13759
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-x9c8-g63x-mh7q"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b4dbf8831d539cdd75e
Added to database: 08/12/2026, 16:11:57 UTC
Last enriched: 08/12/2026, 17:00:07 UTC
Last updated: 08/12/2026, 17:00:07 UTC
Views: 2
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.