Malicious code in ai-node-agent (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2dcf100385d43e4bb2e48489a99d1fc2d4f919953963fa0339966bd5270f61b3) All published JavaScript in dist/ (index.js, client.js, server.js, react.js, and sibling chunks) is heavily obfuscated using javascript-obfuscator (declared as a devDependency) with the hex-identifier and shuffled string-array dispatcher style. The package declares no preinstall/install/postinstall lifecycle hooks; no fetch-and-execute against remote hosts, no reads of installer-secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser profiles), no enumeration of process.env, and no hardcoded credentials or attacker-controlled C2 endpoints were observed in the entry points reviewed. The 'ping/GET/id' keyword co-occurrence flagged in dist/server.js fires inside the obfuscated bundle and is not corroborated by any reachable exfiltration path in the files read. Obfuscation of the entire shipped surface makes the code unauditable and is a legitimate transparency concern for an 'ai-node-agent' library — reviewers should weigh maintainer trust before adopting — but on its own does not meet the threshold for a published block. ## Source: ghsa-malware (0730db02e46f4cfb224880f60bcdcdd43ed4d1bc97c68ee404428f7c592445cb) 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 'ai-node-agent' npm package ships with heavily obfuscated JavaScript code using javascript-obfuscator, making code auditing impractical. While no explicit malicious behaviors such as remote code execution, credential theft, or command-and-control communication were directly observed in the entry points, the obfuscation itself is a significant transparency risk. Security advisories classify this package as malicious, warning that installation likely results in full system compromise, necessitating secret rotation and removal of the package. No lifecycle hooks or direct network exfiltration paths were identified, but the overall risk is high due to the obfuscation and classification by trusted sources.
Potential Impact
Systems with the 'ai-node-agent' package installed or running should be considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Removal of the package alone does not guarantee eradication of malicious software introduced. Immediate secret and key rotation from a separate, uncompromised system is required to mitigate potential damage.
Mitigation Recommendations
No official patch or remediation is available. The package should be removed immediately. All secrets and keys on the affected system must be rotated from a different, trusted computer. Due to the potential full compromise, consider rebuilding or restoring the system from a known good backup.
Malicious code in ai-node-agent (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (2dcf100385d43e4bb2e48489a99d1fc2d4f919953963fa0339966bd5270f61b3) All published JavaScript in dist/ (index.js, client.js, server.js, react.js, and sibling chunks) is heavily obfuscated using javascript-obfuscator (declared as a devDependency) with the hex-identifier and shuffled string-array dispatcher style. The package declares no preinstall/install/postinstall lifecycle hooks; no fetch-and-execute against remote hosts, no reads of installer-secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser profiles), no enumeration of process.env, and no hardcoded credentials or attacker-controlled C2 endpoints were observed in the entry points reviewed. The 'ping/GET/id' keyword co-occurrence flagged in dist/server.js fires inside the obfuscated bundle and is not corroborated by any reachable exfiltration path in the files read. Obfuscation of the entire shipped surface makes the code unauditable and is a legitimate transparency concern for an 'ai-node-agent' library — reviewers should weigh maintainer trust before adopting — but on its own does not meet the threshold for a published block. ## Source: ghsa-malware (0730db02e46f4cfb224880f60bcdcdd43ed4d1bc97c68ee404428f7c592445cb) 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 'ai-node-agent' npm package ships with heavily obfuscated JavaScript code using javascript-obfuscator, making code auditing impractical. While no explicit malicious behaviors such as remote code execution, credential theft, or command-and-control communication were directly observed in the entry points, the obfuscation itself is a significant transparency risk. Security advisories classify this package as malicious, warning that installation likely results in full system compromise, necessitating secret rotation and removal of the package. No lifecycle hooks or direct network exfiltration paths were identified, but the overall risk is high due to the obfuscation and classification by trusted sources.
Potential Impact
Systems with the 'ai-node-agent' package installed or running should be considered fully compromised. Attackers may have gained full control, risking exposure of all stored secrets and keys. Removal of the package alone does not guarantee eradication of malicious software introduced. Immediate secret and key rotation from a separate, uncompromised system is required to mitigate potential damage.
Mitigation Recommendations
No official patch or remediation is available. The package should be removed immediately. All secrets and keys on the affected system must be rotated from a different, trusted computer. Due to the potential full compromise, consider rebuilding or restoring the system from a known good backup.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6517
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-w537-2cgp-4x64"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a3ef7b127e9c79719ffb92d
Added to database: 06/26/2026, 22:05:37 UTC
Last enriched: 07/09/2026, 10:48:34 UTC
Last updated: 07/31/2026, 00:57:11 UTC
Views: 46
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.