Malicious code in abina-amugi-amia (npm)
The npm package abina-amugi-amia contains malicious code designed to automatically generate and publish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, removes private flags, 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-amianpm package containing malicious autopublish scripts
The npm package abina-amugi-amia 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 and pollute the npm registry with numerous derivative packages.
The incident was identified through Amazon Inspector and credited to the OpenSSF's malicious-packages repository, which tracks such campaigns. The package represents part of a larger wave of similar malicious packages that exploited the tea.xyz token reward system to generate fraudulent reputation metrics.
Indicators of compromise
- Packages
- abina-amugi-amia
Remediation
- Remove abina-amugi-amia and any derivative packages from npm dependencies immediately
- Audit npm package.json and lock files for any unexpected or unfamiliar packages, particularly those with randomized or unusual names
- Review npm account activity and publishing history for unauthorized package publications
- Monitor tea.xyz token reward campaign packages and cross-reference against OpenSSF malicious-packages list
- Implement automated scanning of npm dependencies against known malicious package registries
Sources
- GitHub Advisory GHSA-hfrh-6g3x-7282 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-amia (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-amia-npm-1csx3a
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