awesome-terminalnpm
awesome-terminal is a confirmed malicious npm package (MAL-2026-10407) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in awesome-terminal (npm)
What this malware does
[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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for awesome-terminal (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging awesome-terminal across your stack and pipelines.
If you installed it — respond
Remove awesome-terminal from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If awesome-terminal was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks awesome-terminal before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks awesome-terminal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.