Malware in sugarball-cli
Malware was distributed via the sugarball-cli npm package, resulting in full system compromise of affected machines. The advisory recommends treating any system with this package as fully compromised and rotating all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with sugarball-cli installed or executed
- Ecosystems
- Attack vectors
- Affected entities
- sugarball-cli
The sugarball-cli npm package contained malware that compromised systems upon installation or execution. According to the GitHub advisory (GHSA-5v79-352p-4p25), any computer running this package should be considered fully compromised.\n\nThe advisory recommends immediate remediation: rotate all secrets and keys from a different, unaffected computer; remove the package from affected systems; and assume that full control of the system may have been granted to an external entity, meaning package removal alone may not eliminate all malicious software.\n\nThis represents a direct supply chain compromise through a malicious package in the npm ecosystem.
Indicators of compromise
- Packages
- sugarball-cli
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, unaffected computer
- Remove the sugarball-cli package from all affected systems
- Assume full system compromise and conduct forensic analysis to identify any additional malware or persistence mechanisms
- Review system logs and network traffic for indicators of compromise
- Consider full system rebuild if critical systems were affected
Sources
- GitHub Advisory GHSA-5v79-352p-4p25 · GitHub Advisory Database
Cite this entry
"Malware in sugarball-cli." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-sugarball-cli-ebqfih
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