Malware in chalk-ultra
Malware discovered in the npm package chalk-ultra. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with chalk-ultra installed or running
- Ecosystems
- Attack vectors
- Affected entities
- chalk-ultra
A critical malware incident has been identified in the npm package chalk-ultra. According to the GitHub Advisory (GHSA-vgq4-6c53-5826), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should 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, as the attacker may have gained full control of the system.\n\nAffected users should treat their systems as potentially fully compromised and take comprehensive remediation steps accordingly.
Indicators of compromise
- Packages
- chalk-ultra
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the chalk-ultra package from all affected systems
- Conduct a full security audit and malware scan of all systems that had chalk-ultra installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Monitor for any suspicious activity on accounts and systems that may have been exposed
Sources
- GitHub Advisory GHSA-vgq4-6c53-5826 · GitHub Advisory Database
Cite this entry
"Malware in chalk-ultra." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-chalk-ultra-1x31rr
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 @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - activecritical
Malware in @sdgdfgdfhhhfd/multiviewr
Malware discovered in the npm package @sdgdfgdfhhhfd/multiviewr. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package