Malicious code in acidic (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8ef3583eb4d5b190d763cd784f5a40cb2cddaa8f1b6cd81b8a663bb612b51bb7) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (913d08ff323e17e3653281e7b5d5a20df4d503b322939aeb68c851d327e6ca53) 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 'acidic' package in the npm ecosystem is identified as containing malicious code that results in a full compromise of the host system. Installation or execution of this package grants an attacker complete control over the affected computer. Due to the severity of the compromise, it is recommended to consider all secrets and keys on the system as compromised and to rotate them from a secure environment. Removal of the package does not assure eradication of all malicious components introduced by the attacker.
Potential Impact
Full system compromise on any computer with the 'acidic' package installed or running. Potential exposure and loss of all stored secrets and keys. Persistence of malicious software beyond package removal is likely, indicating a deep and severe security breach.
Mitigation Recommendations
Immediately remove the 'acidic' package from all affected systems. Rotate all secrets and keys stored on compromised machines from a separate, secure computer. Assume the affected system is fully compromised and perform a thorough incident response, including system reimaging or replacement if necessary. There is no known patch or official fix; remediation relies on removal and secret rotation.
Malicious code in acidic (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8ef3583eb4d5b190d763cd784f5a40cb2cddaa8f1b6cd81b8a663bb612b51bb7) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (913d08ff323e17e3653281e7b5d5a20df4d503b322939aeb68c851d327e6ca53) 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 'acidic' package in the npm ecosystem is identified as containing malicious code that results in a full compromise of the host system. Installation or execution of this package grants an attacker complete control over the affected computer. Due to the severity of the compromise, it is recommended to consider all secrets and keys on the system as compromised and to rotate them from a secure environment. Removal of the package does not assure eradication of all malicious components introduced by the attacker.
Potential Impact
Full system compromise on any computer with the 'acidic' package installed or running. Potential exposure and loss of all stored secrets and keys. Persistence of malicious software beyond package removal is likely, indicating a deep and severe security breach.
Mitigation Recommendations
Immediately remove the 'acidic' package from all affected systems. Rotate all secrets and keys stored on compromised machines from a separate, secure computer. Assume the affected system is fully compromised and perform a thorough incident response, including system reimaging or replacement if necessary. There is no known patch or official fix; remediation relies on removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10282
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-w85c-pm3f-wmmf"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a54ada768715ace438f4900
Added to database: 07/13/2026, 09:19:35 UTC
Last enriched: 07/13/2026, 09:29:52 UTC
Last updated: 07/31/2026, 00:38:57 UTC
Views: 22
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.