Malicious code in @akunsansan0/susu3 (npm)
@akunsansan0/susu3 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, removes private flags, and continuously pollutes the npm registry with variants.
- Disclosed
- Last updated
- Blast radius
- Registry pollution; potential impact on developers who installed the package or its auto-generated derivatives.
- Ecosystems
- Attack vectors
- Affected entities
- @akunsansan0/susu3npm package containing malicious autopublish scripts
@akunsansan0/susu3 is a malicious npm package identified as part of a broader tea.xyz token reward campaign that flooded the npm registry. The package contains autopublish scripts (such as auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and republish derivative packages.
The malicious payload modifies package.json to remove private flags and changes version numbers. It generates random Indonesian-themed package names (with some English variants) and continuously republishes these variants to pollute the npm registry. The goal is to inflate developer reputation scores for tea protocol token rewards.
The package was identified by Amazon Inspector and credited to the OpenSSF's malicious-packages repository. This incident is part of a coordinated campaign involving multiple similar packages on npm.
Indicators of compromise
- Packages
- @akunsansan0/susu3
Remediation
- Remove @akunsansan0/susu3 and any auto-generated derivative packages from your project dependencies
- Audit npm package.json and lock files for any unexpected or unfamiliar packages
- Review npm account activity and publishing history for unauthorized package publications
- Monitor for and remove any derivative packages with randomized or suspicious names that may have been auto-generated
- Consider using npm audit and security scanning tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-h5rh-m63q-9rrx · GitHub Advisory Database
Cite this entry
"Malicious code in @akunsansan0/susu3 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-akunsansan0-susu3-npm-1w3zq8
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit