Malware in tinymask-js
Malware was discovered in the npm package tinymask-js. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with tinymask-js installed or running
- Ecosystems
- Attack vectors
- Affected entities
- tinymask-jsnpm package containing malware
A critical malware incident was identified in the npm package tinymask-js. According to the GitHub Advisory (GHSA-993g-jhvm-h79j), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- tinymask-js
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the tinymask-js package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had tinymask-js installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding or replacing systems that had this package installed, as full removal of malware cannot be guaranteed
Sources
- GitHub Advisory GHSA-993g-jhvm-h79j · GitHub Advisory Database
Cite this entry
"Malware in tinymask-js." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-tinymask-js-80hkkm
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-special-payments (npm)
The npm package sme-rko-finance-front-operations-special-payments contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure upon require(). The package employed obfuscation techniques to evade static analysis and included dual dropper paths in both index.js and lib/telemetry.js.
npmCompromised package - activecritical
Malware in bnpl-blocks-desktop-bnpl-anchor-title
Malware discovered in the npm package bnpl-blocks-desktop-bnpl-anchor-title. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-operations-notifications-models (npm)
The npm package sme-rko-finance-front-operations-notifications-models contained malicious code that acts as a native-binary dropper, downloading and executing platform-specific binaries from attacker-controlled Cloudflare Workers domains and DNS fallback servers upon package require.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-penalty (npm)
The npm package sme-rko-finance-front-operations-penalty contained malicious code that downloads and executes platform-specific binaries on require(). The dropper uses obfuscated string concatenation and DNS fallback channels to retrieve payloads from attacker-controlled infrastructure.
npmCompromised package