Malicious code in abina-amiab-agu (npm)
The npm package abina-amiab-agu contained malicious code designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The package modified package.json, changed version numbers, and continuously republished variants to pollute the npm registry.
- Disclosed
- Last updated
- Blast radius
- npm registry; potential impact on any developer who installed this package
- Ecosystems
- Attack vectors
- Affected entities
- abina-amiab-agunpm package containing malicious autopublish scripts
The npm package abina-amiab-agu was identified as containing malicious code as part of a broader campaign associated with the tea.xyz token reward initiative. The package included autopublish scripts (such as auto.js, autopublish.js, autopublish2.js, and autopublish3.js) designed to automatically generate and publish derivative packages with randomized names.
The malicious payload modified package.json files to remove private flags and alter version numbers. It then generated random package names, many with Indonesian themes, and continuously republished variants to pollute the npm registry. This activity was intended to artificially inflate developer reputation scores for tea protocol token rewards.
The incident was identified and documented by the OpenSSF's malicious-packages repository, which tracks such supply chain attacks. The package has been flagged and removed from active circulation.
Indicators of compromise
- Packages
- abina-amiab-agu
Remediation
- Remove abina-amiab-agu and any derivative packages from your project dependencies
- Audit your npm registry account for any unauthorized package publications
- Review package.json and lock files for unexpected changes or new dependencies
- Monitor your npm account for suspicious activity related to token reward campaigns
- Use npm audit to identify and remove other malicious packages from the tea.xyz campaign
Sources
- GitHub Advisory GHSA-3g79-w6xg-fv9j · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amiab-agu (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-amiab-agu-npm-1alqvu
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