Malicious code in abina-amugi-amiataamu (npm)
The npm package abina-amugi-amiataamu contains malicious code 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 installation by developers unaware of malicious intent
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugi-amiataamunpm package containing malicious autopublish scripts
The npm package abina-amugi-amiataamu was identified as part of a coordinated campaign to flood the npm registry with malicious packages tied to the tea.xyz token reward program. The package contains autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that execute automatically upon installation.
The malicious payload modifies package.json to remove private flags and alter version numbers, then generates random Indonesian-themed and English-themed package names. These derivative packages are continuously republished to the npm registry, creating a pollution attack designed to inflate developer reputation scores for tea protocol token rewards.
This incident was identified by Amazon Inspector and credited to the OpenSSF's malicious-packages repository. The attack represents a systematic attempt to manipulate the npm ecosystem through automated registry pollution rather than direct code execution on end-user systems.
Developers who installed this package may have unknowingly contributed to the generation and publication of malicious derivative packages.
Indicators of compromise
- Packages
- abina-amugi-amiataamu
Remediation
- Remove abina-amugi-amiataamu and any derivative packages from your project dependencies immediately
- Audit your npm account for any unauthorized package publications or modifications
- Review package-lock.json and yarn.lock for any unexpected package variants
- Report any suspicious packages to npm security team
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-v793-fr2x-69xx · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-amiataamu (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2026; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-abina-amugi-amiataamu-npm-1ikgro
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