Malicious code in abina-amoavugoi-anunhi (npm)
The npm package abina-amoavugoi-anunhi contains malicious code designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The payload modifies package.json, removes private flags, and continuously pollutes the npm registry with variants.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed this package and any derivative packages it generated
- Ecosystems
- Attack vectors
- Affected entities
- abina-amoavugoi-anunhinpm package containing malicious autopublish scripts
The npm package abina-amoavugoi-anunhi was identified as containing malicious code as part of a broader tea.xyz token reward campaign that flooded the npm registry. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names.
The malicious payload modifies package.json to remove private flags and changes version numbers, then generates random Indonesian-themed package names (with some English variants) and continuously republishes them to pollute the npm registry. The goal is 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, which tracks such supply chain attacks on npm.
Indicators of compromise
- Packages
- abina-amoavugoi-anunhi
Remediation
- Remove abina-amoavugoi-anunhi and any derivative packages it generated from your project dependencies
- Audit npm install logs to identify if this package or its variants were installed
- Review and revoke any npm tokens that may have been exposed
- Monitor your npm account for unauthorized package publications
- Use npm audit to check for other malicious packages from the tea.xyz campaign
Sources
- GitHub Advisory GHSA-8gjm-95mg-7fvv · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amoavugoi-anunhi (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-amoavugoi-anunhi-npm-i8d0qa
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