Malware in dolyame-boxy-atom-icon-loader
Malware discovered in the npm package dolyame-boxy-atom-icon-loader. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- dolyame-boxy-atom-icon-loader
The npm package dolyame-boxy-atom-icon-loader has been identified as containing malware. According to the GitHub Advisory (GHSA-5j2m-28q8-4955), 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 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 package's execution, given the potential for full system compromise.\n\nUsers should treat any system that has run this package as potentially containing persistent malware and take appropriate containment and recovery measures.
Indicators of compromise
- Packages
- dolyame-boxy-atom-icon-loader
Remediation
- Immediately remove the dolyame-boxy-atom-icon-loader package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume full system compromise and perform forensic analysis or complete system rebuild
- Monitor affected systems for signs of persistent malware or unauthorized access
- Review system logs and network traffic for indicators of compromise
- Consider complete system reimaging if sensitive data or systems were affected
Sources
- GitHub Advisory GHSA-5j2m-28q8-4955 · GitHub Advisory Database
Cite this entry
"Malware in dolyame-boxy-atom-icon-loader." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-dolyame-boxy-atom-icon-loader-sa9gjz
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - 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 - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - 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