Malicious code in abina-amugymi-amamagu (npm)
The npm package abina-amugymi-amamagu contains malicious code designed to automatically generate and publish derivative packages with randomized names to inflate tea protocol token rewards. The payload modifies package.json, removes private flags, and continuously republishes variants to pollute the npm registry.
- Disclosed
- Last updated
- Blast radius
- Registry pollution; potential installation by developers unaware of malicious intent
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugymi-amamagunpm package containing malicious autopublish scripts
The npm package abina-amugymi-amamagu 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, primarily using Indonesian-themed naming conventions with some English variants.
The malicious payload modifies package.json to remove private flags and changes version numbers, enabling continuous republication of variants. This activity was intended to artificially inflate developer reputation scores for tea protocol token rewards.
The incident was identified and documented by the OpenSSF's malicious-packages repository, which tracks such supply chain pollution campaigns. The package represents a form of registry abuse and namespace pollution rather than a traditional code execution vulnerability, but poses a significant threat to registry integrity and developer trust.
Indicators of compromise
- Packages
- abina-amugymi-amamagu
Remediation
- Remove abina-amugymi-amamagu and any derivative packages with randomized Indonesian or English-themed names from your dependencies
- Audit npm package.json and lock files for any unexpected or unfamiliar packages installed during the affected period
- Review npm account activity and publishing history for unauthorized package publications
- Monitor for and block installation of packages from the tea.xyz token reward campaign identified by OpenSSF
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-53c2-6rp8-qwcp · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugymi-amamagu (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-amugymi-amamagu-npm-1w32o3
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 @junofficial/baileys
The npm package @junofficial/baileys contained malware that fully compromised any system with the package installed or running. The malicious package has been identified and removed from distribution.
npmCompromised package - containedcritical
Malware in a.poltoradnev-package-a
The npm package a.poltoradnev-package-a contains malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
npmCompromised package - activecritical
Malware in @zynkit/probe
Malware discovered in the npm package @zynkit/probe. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.
npmCompromised package - activecritical
Malware in club-sauce
Malware discovered in the npm package club-sauce. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package