Malicious code in abina-amugi-anui (npm)
The npm package abina-amugi-anui contained malicious code designed to automatically generate and publish derivative packages with randomized names to inflate tea protocol token rewards. The package modified package.json, altered version numbers, and continuously republished variants to pollute the npm registry.
- 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-anuinpm package containing malicious autopublish scripts
The npm package abina-amugi-anui was identified as part of a coordinated campaign to flood the npm registry with malicious packages. The package contained autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names, primarily using Indonesian-themed naming conventions.
The malicious payload modified package.json files to remove private flags and change version numbers, enabling continuous republication of variants. This activity was intended to artificially inflate developer reputation scores within the tea.xyz token reward campaign, thereby polluting the npm registry with numerous derivative packages.
The incident was identified and credited to the OpenSSF's malicious-packages repository, which tracks such supply chain attacks. The package has been cataloged under identifier MAL-2025-151380.
Indicators of compromise
- Packages
- abina-amugi-anui
Remediation
- Remove abina-amugi-anui and any derivative packages from npm installations
- Audit npm package.json files for unexpected version changes or private flag modifications
- Review npm account activity for unauthorized package publications
- Monitor for and remove any auto-generated derivative packages with randomized or Indonesian-themed names published from affected accounts
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-4rww-24v7-q447 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-anui (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-anui-npm-iovpfs
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