Malicious code in abina-amugi-anuhabuai (npm)
The npm package abina-amugi-anuhabuai 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 campaign to inflate developer reputation scores for tea protocol token rewards by polluting the registry with auto-published variants.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed this package and any derivative packages it auto-published
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugi-anuhabuaimalicious npm package
The npm package abina-amugi-anuhabuai was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package appears to be part of the tea.xyz token reward campaign that resulted in widespread pollution of the npm registry.
The malicious payload includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automatically execute upon installation. These scripts modify package.json to remove private flags, alter version numbers, and generate random package names—primarily Indonesian-themed variants, with some English-language variants—which are then continuously republished to the npm registry.
The attack vector is designed to artificially inflate developer reputation scores within the tea protocol ecosystem by creating numerous derivative packages. This represents a supply chain attack that compromises the integrity of the npm registry and affects any developer who installs the malicious package or its auto-generated derivatives.
The incident has been documented in the OpenSSF malicious-packages repository (MAL-2025-151376) and is tracked under GitHub Advisory GHSA-vm29-7946-8v3g.
Indicators of compromise
- Packages
- abina-amugi-anuhabuai
Remediation
- Remove abina-amugi-anuhabuai and any derivative packages it may have auto-published from your project dependencies immediately
- Audit npm install logs and package-lock.json for any unexpected package installations or version changes
- Review and revoke any npm tokens or credentials that may have been exposed if the malicious package was installed in a CI/CD environment
- Monitor your npm account for unauthorized package publications or modifications
- Report any derivative packages generated by this malicious package to npm security for removal
Sources
- GitHub Advisory GHSA-vm29-7946-8v3g · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-anuhabuai (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-amugi-anuhabuai-npm-1xq29g
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @syncraft-labs/core (npm)
The npm package @syncraft-labs/core contained obfuscated malicious code in its ESM build that executes on import, fetching and executing attacker-controlled payloads from Ethereum blockchain via JSON-RPC endpoints. The CommonJS build was clean, indicating targeted injection into the ESM entry point.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in localize-translate (npm)
The npm package localize-translate contained malicious code in its postinstall lifecycle script that collected host identifiers and beaconed them to an attacker-controlled endpoint (gigww0v7.instances.poc.jchunt.top) without user consent. The reconnaissance callback fired automatically on every installation, collecting hostname, platform, architecture, Node version, package name, and timestamp.
npmCompromised packageMalicious commit - containedcritical
Malicious code in mutex-plus (npm)
The npm package mutex-plus contains hidden malicious code that enables remote code execution when a callback object with a specific jobId hash is passed to runExclusive(). The payload is encrypted at rest in lib/plusMutex.min.js and decrypted using the jobId as a key, then executed as a detached Node.js process.
npmCompromised packageMalicious commit