Malicious code in abina-amibn-aguha (npm)
The npm package abina-amibn-aguha contains malicious code designed to automatically generate and republish derivative packages with randomized names to the npm registry. The attack is part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages.
- Disclosed
- Last updated
- Blast radius
- Registry-wide pollution; affects any developer who installed this package or its auto-generated derivatives
- Ecosystems
- Attack vectors
- Affected entities
- abina-amibn-aguhanpm package containing malicious autopublish scripts
The npm package abina-amibn-aguha 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 automatically execute upon installation.
The malicious payload modifies package.json to remove private flags and alter version numbers, then generates derivative packages with randomized Indonesian-themed and English names. These variants are continuously republished to the npm registry, polluting it with numerous malicious copies.
This package is part of a coordinated campaign associated with the tea.xyz token reward protocol, which has flooded npm with similar malicious packages designed to inflate developer reputation scores for financial gain.
Developers who installed this package or any of its auto-generated derivatives may have had their npm credentials or registry access compromised, and their own packages may have been republished without authorization.
Indicators of compromise
- Packages
- abina-amibn-aguha
Remediation
- Immediately remove abina-amibn-aguha and any packages with randomized Indonesian or English names from your dependencies
- Audit npm account activity and access logs for unauthorized package publications
- Rotate npm authentication tokens and API keys
- Review all published packages for unauthorized modifications or versions
- Check package.json files in your projects for unexpected changes to private flags or version numbers
- Monitor npm registry for any derivative packages generated from your account
- Report the package to npm security team if not already done
Sources
- GitHub Advisory GHSA-4jjw-xr87-93m3 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amibn-aguha (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed January 1, 2025; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-abina-amibn-aguha-npm-lthbip
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