Malicious code in abina-amugi-amiau (npm)
The npm package abina-amugi-amiau contained malicious code designed to automatically generate and publish derivative packages with randomized names to the npm registry. The package was part of a broader campaign to inflate developer reputation scores for tea protocol token rewards.
- 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
- abina-amugi-amiaunpm package containing malicious autopublish script
The npm package abina-amugi-amiau was identified as containing malicious code as part of the tea.xyz token reward campaign that flooded npm with similar packages. The malicious payload included autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages.
The malicious behavior modified package.json to remove private flags, altered version numbers, and generated random Indonesian-themed package names (with some English variants). The script continuously republished variants to pollute the npm registry and inflate developer reputation metrics.
The package was identified and credited to the OpenSSF's malicious-packages repository, which tracks such threats. The attack vector involved publishing a compromised package directly to npm rather than compromising an existing legitimate package.
Indicators of compromise
- Packages
- abina-amugi-amiau
Remediation
- Remove abina-amugi-amiau and any auto-generated derivative packages from npm installations
- Audit npm package.json files for unexpected dependencies on this package or its variants
- Review npm account activity for unauthorized package publications
- Monitor for similar patterns of registry pollution from tea.xyz token campaign packages
- Use npm audit to identify and remove malicious packages from project dependencies
Sources
- GitHub Advisory GHSA-32vv-rfcv-29g4 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-amiau (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed January 1, 2025; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-abina-amugi-amiau-npm-1ycmdr
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 svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package