Malicious code in awesome-terminal (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (379d820ae94a1dd684c187fd2577558795440d8f8cd1fe3cd209c8eb5b303913) [email protected] ships a postinstall script (scripts/install-check.cjs) that resolves a bundle URL from a remote JSON config at https://trabalhos-flax.vercel.app/config/clob-math.json, downloads a tgz archive to a temp directory, extracts it with tar, runs `npm install` inside the extracted tree, then require()s peer-math.js and invokes syncSession(). The fetched payload is unpinned, unsigned, unverified, and executes automatically on `npm install` — a direct install-time remote code execution vector against any machine that installs the package. The advertised purpose (README describes an ASCII mascot library with generate/animate/presets APIs) does not match the shipped code (index.js/kelly.js export Kelly-criterion staking helpers with keywords polymarket, kelly, prediction-markets), and neither surface justifies fetching and executing arbitrary remote code at install time; the mismatch functions as a cover story for the dropper. ## Source: ghsa-malware (16a5e17479fdeb82ccdde67c9494e87fda6817dbd7db8cc0723ebf40109b00fe) 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 npm package [email protected] includes a postinstall script that downloads a tarball from an untrusted remote JSON configuration URL, extracts it, runs npm install within the extracted directory, and then requires and executes a JavaScript module. This process occurs automatically during npm install, providing a direct remote code execution vector. The fetched payload is unpinned, unsigned, and unverified, making it a high-risk supply chain attack. The package's README claims it is an ASCII mascot library, but the actual code exports staking helpers unrelated to the advertised purpose, suggesting the malicious code is disguised as legitimate functionality.
Potential Impact
Any system that installs [email protected] is vulnerable to remote code execution at install time, allowing an attacker to execute arbitrary code with the privileges of the installing user. This can lead to system compromise, data theft, or further malware deployment. The unverified and dynamic nature of the payload increases the risk and unpredictability of the attack.
Mitigation Recommendations
No official patch or remediation is currently available. Users and organizations should avoid installing [email protected]. If already installed, remove the package and audit affected systems for compromise. Monitor vendor advisories for updates or fixes. Due to the nature of the threat, the safest mitigation is to not use this package version.
Malicious code in awesome-terminal (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (379d820ae94a1dd684c187fd2577558795440d8f8cd1fe3cd209c8eb5b303913) [email protected] ships a postinstall script (scripts/install-check.cjs) that resolves a bundle URL from a remote JSON config at https://trabalhos-flax.vercel.app/config/clob-math.json, downloads a tgz archive to a temp directory, extracts it with tar, runs `npm install` inside the extracted tree, then require()s peer-math.js and invokes syncSession(). The fetched payload is unpinned, unsigned, unverified, and executes automatically on `npm install` — a direct install-time remote code execution vector against any machine that installs the package. The advertised purpose (README describes an ASCII mascot library with generate/animate/presets APIs) does not match the shipped code (index.js/kelly.js export Kelly-criterion staking helpers with keywords polymarket, kelly, prediction-markets), and neither surface justifies fetching and executing arbitrary remote code at install time; the mismatch functions as a cover story for the dropper. ## Source: ghsa-malware (16a5e17479fdeb82ccdde67c9494e87fda6817dbd7db8cc0723ebf40109b00fe) 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 npm package [email protected] includes a postinstall script that downloads a tarball from an untrusted remote JSON configuration URL, extracts it, runs npm install within the extracted directory, and then requires and executes a JavaScript module. This process occurs automatically during npm install, providing a direct remote code execution vector. The fetched payload is unpinned, unsigned, and unverified, making it a high-risk supply chain attack. The package's README claims it is an ASCII mascot library, but the actual code exports staking helpers unrelated to the advertised purpose, suggesting the malicious code is disguised as legitimate functionality.
Potential Impact
Any system that installs [email protected] is vulnerable to remote code execution at install time, allowing an attacker to execute arbitrary code with the privileges of the installing user. This can lead to system compromise, data theft, or further malware deployment. The unverified and dynamic nature of the payload increases the risk and unpredictability of the attack.
Mitigation Recommendations
No official patch or remediation is currently available. Users and organizations should avoid installing [email protected]. If already installed, remove the package and audit affected systems for compromise. Monitor vendor advisories for updates or fixes. Due to the nature of the threat, the safest mitigation is to not use this package version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10407
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a54ad9c68715ace438f3cf2
Added to database: 07/13/2026, 09:19:24 UTC
Last enriched: 07/13/2026, 09:27:28 UTC
Last updated: 07/30/2026, 07:29:29 UTC
Views: 28
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.