Malicious code in abina-amugui-anucuamai (npm)
The npm package abina-amugui-anucuamai contains malicious code designed to automatically generate and republish derivative packages with randomized names to the npm registry. This package is part of a broader campaign exploiting the tea.xyz token reward system to artificially inflate developer reputation scores.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed this package or its derivative variants
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugui-anucuamainpm package containing malicious autopublish scripts
The npm package abina-amugui-anucuamai was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package includes 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 package names (primarily Indonesian-themed variants, with some English variants) and continuously republishes them to the npm registry. This behavior is designed to pollute the registry and artificially inflate developer reputation metrics for tea protocol token rewards.
The package is part of a larger coordinated campaign that flooded npm with similar malicious packages following the same pattern. Developers who installed this package or any of its derivative variants may have had their systems used to further propagate malicious packages to the registry.
Indicators of compromise
- Packages
- abina-amugui-anucuamai
Remediation
- Immediately uninstall abina-amugui-anucuamai and any derivative packages with randomized or suspicious names from npm
- Audit package.json and lock files for unexpected dependencies or version changes
- Review npm account activity and authentication logs for unauthorized package publications
- Clear npm cache and reinstall legitimate dependencies from a clean state
- Monitor npm account for any unauthorized package publications or modifications
- Report any suspicious packages discovered to npm security team
Sources
- GitHub Advisory GHSA-676c-r2m6-p36p · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugui-anucuamai (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-amugui-anucuamai-npm-1p6939
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