Malicious code in abina-amugi-ani (npm)
The npm package abina-amugi-ani contains malicious code designed to automatically generate and publish derivative packages with randomized names to inflate developer reputation scores for tea protocol token rewards. The payload modifies package.json, removes private flags, changes versions, and continuously republishes variants to pollute the npm registry.
- Disclosed
- Last updated
- Blast radius
- Registry-wide pollution; affects developers who install this package and any derivative packages it generates
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugi-aninpm package containing malicious autopublish scripts
The npm package abina-amugi-ani was identified as part of a coordinated campaign to flood the npm registry with malicious packages. The package contains autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that execute automatically upon installation.
The malicious payload modifies package.json to remove private flags and alter version numbers. It then generates random package names, many with Indonesian themes, and automatically publishes these derivative packages back to the npm registry. This mechanism creates a self-propagating attack that pollutes the registry and generates numerous variants.
The underlying motivation is to artificially inflate developer reputation scores within the tea.xyz token reward campaign. By creating and publishing many derivative packages, the attacker aims to accumulate token rewards based on inflated metrics.
This incident was identified and credited to the OpenSSF's malicious-packages repository, which tracks such coordinated supply chain attacks.
Indicators of compromise
- Packages
- abina-amugi-ani
Remediation
- Remove abina-amugi-ani and any derivative packages from your project dependencies immediately
- Audit your npm account for any unauthorized package publications or modifications
- Review package.json and lock files for unexpected changes or new dependencies
- Check npm audit logs for suspicious activity during the period this package was installed
- Report any derivative packages generated by this malicious code to npm security team
- Consider using npm package signature verification and integrity checking tools
Sources
- GitHub Advisory GHSA-6c9j-746j-9jqc · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-ani (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-ani-npm-19d2zx
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
Malware in sui-move-graphql
Malware was discovered in the npm package sui-move-graphql. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
npmCompromised package - resolvedcritical
Malicious code in bcc-design (npm)
bcc-design@9999.0.0 on npm is a dependency-confusion beacon package with no legitimate functionality. Its postinstall script exfiltrates the installer's hostname and system metadata to an attacker-controlled IP endpoint.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in core-tailwindcss-utility (npm)
core-tailwindcss-utility, an npm package falsely advertised as a Tailwind CSS utility, contains malicious code that fetches and executes arbitrary Node.js code from a remote C2 server. The package includes suspicious dependencies for credential theft and remote communication.
npmCompromised package - containedcritical
Malware in blastradar
Malware was discovered in the npm package blastradar, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package