Malicious code in abina-amugi-amiatanamu (npm)
The npm package abina-amugi-amiatanamu contains malicious code designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The package modifies package.json, changes version numbers, and continuously republishes variants to pollute the npm registry.
- Disclosed
- Last updated
- Blast radius
- Registry pollution; potential installation by developers unaware of malicious intent
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugi-amiatanamunpm package containing malicious autopublish scripts
The npm package abina-amugi-amiatanamu was identified as containing malicious code as part of a broader campaign associated with the tea.xyz token reward initiative. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automatically generate and publish derivative packages with randomized names, primarily using Indonesian-themed naming conventions.
The malicious payload modifies package.json to remove private flags and alter version numbers, enabling continuous republication of variants under different names. This activity is designed to artificially inflate developer reputation scores within the tea protocol ecosystem in exchange for token rewards.
The attack vector involves registry pollution—flooding npm with numerous derivative packages to manipulate reputation metrics. Any developer who installed this package would have had the malicious scripts execute during installation, potentially contributing to the automated republication of malicious variants.
This incident was identified and credited to the OpenSSF's malicious-packages repository, which tracks such campaigns systematically.
Indicators of compromise
- Packages
- abina-amugi-amiatanamu
Remediation
- Remove abina-amugi-amiatanamu and any derivative packages from your project dependencies immediately
- Audit npm audit logs and package-lock.json for any unexpected package installations or version changes
- Review any packages installed during the period this malicious package was available on npm
- Report any suspicious packages to npm security team
- Consider using npm package integrity verification tools to detect unauthorized modifications
Sources
- GitHub Advisory GHSA-jfh9-r9q8-jjjc · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-amiatanamu (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2025; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-abina-amugi-amiatanamu-npm-k8c0an
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