Malicious code in abina-amugi-anupmai (npm)
The npm package abina-amugi-anupmai 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 package modifies package.json, removes private flags, and continuously republishes variants to pollute the npm registry.
- Disclosed
- Last updated
- Blast radius
- Registry-wide pollution; affects npm ecosystem integrity and developer trust
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugi-anupmaiMalicious npm package containing autopublish scripts
The npm package abina-amugi-anupmai was identified as containing malicious code as part of a broader tea.xyz token reward campaign that flooded the npm registry. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names, many using Indonesian-themed naming conventions.
The malicious payload modifies package.json to remove private flags and changes version numbers, enabling continuous republication of variants. This activity is intended to artificially inflate developer reputation scores within the tea protocol ecosystem in exchange for token rewards.
The attack represents a form of registry pollution and supply chain compromise, leveraging the npm package manager to distribute code that further compromises the integrity of the registry itself. The OpenSSF has documented this incident as part of a broader malicious package campaign.
Remediation includes removal of the package from npm, revocation of associated accounts, and implementation of stronger controls to prevent similar autopublish-based attacks.
Indicators of compromise
- Packages
- abina-amugi-anupmai
Remediation
- Remove abina-amugi-anupmai and all derivative packages from npm registry
- Revoke npm accounts associated with the malicious package publication
- Audit npm for other packages following the same autopublish pattern (auto.js, autopublish.js variants)
- Implement registry-level detection for packages that modify package.json and republish automatically
- Review and strengthen npm's account security and package publication controls
- Notify developers who may have installed this package to audit their dependencies
Sources
- GitHub Advisory GHSA-8qw9-6p95-phv7 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugi-anupmai (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-anupmai-npm-1o2l89
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malware in ulebkit
The npm package ulebkit contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.
npmCompromised package - activecritical
Malware in celonix-otp-react
Malware discovered in the npm package celonix-otp-react. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - 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 - containedcritical
Malicious code in bcc-design-icons (npm)
bcc-design-icons@9999.0.0 on npm contains malicious postinstall script that exfiltrates hostname and package name to attacker-controlled IP 91.201.215.48:8000. The package lacks expected icon-library functionality and exhibits characteristics of a dependency-confusion attack targeting internal/private npm installers.
npmDependency confusionCompromised package