Malicious code in abina-amougoi-anuhi (npm)
The npm package abina-amougoi-anuhi contains malicious code designed to automatically generate and publish derivative packages with randomized names to the npm registry. The package is part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages.
- Disclosed
- Last updated
- Blast radius
- Registry pollution; potential impact on developers who installed the package and any downstream dependencies
- Ecosystems
- Attack vectors
- Affected entities
- abina-amougoi-anuhinpm package containing malicious autopublish scripts
The npm package abina-amougoi-anuhi was identified as containing malicious code by Amazon Inspector and credited to the OpenSSF malicious-packages repository. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automatically execute upon installation.\n\nThe malicious payload modifies package.json to remove private flags, alters version numbers, and generates random package names (primarily Indonesian-themed variants, with some English variants) to create derivative packages. These variants are then continuously republished to the npm registry, causing significant registry pollution.\n\nThis package is part of a larger coordinated campaign associated with the tea.xyz token reward protocol, which flooded npm with similar malicious packages designed to inflate developer reputation scores for token rewards. The attack leverages the npm autopublish mechanism to propagate variants autonomously.\n\nThe package has been identified and cataloged by the OpenSSF malicious-packages project (MAL-2025-151364).
Indicators of compromise
- Packages
- abina-amougoi-anuhi
Remediation
- Remove abina-amougoi-anuhi and any derivative packages from npm installations immediately
- Audit npm package.json files for unexpected version changes or private flag modifications
- Review npm account activity and access logs for unauthorized package publications
- Monitor for and remove any derivative packages with randomized or Indonesian-themed names published from affected accounts
- Implement npm package signature verification and integrity checks
- Report the package and associated accounts to npm security team
Sources
- GitHub Advisory GHSA-8h5w-pqh9-p3c9 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amougoi-anuhi (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-amougoi-anuhi-npm-jetl40
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