Malicious code in abina-amugmi-amamu (npm)
The npm package abina-amugmi-amamu contained malicious code designed to automatically generate and republish derivative packages with randomized names to the npm registry. The package was part of a broader campaign to inflate developer reputation scores for tea protocol token rewards.
- Disclosed
- Last updated
- Blast radius
- npm registry; potential impact on any developer who installed this package or its auto-generated derivatives
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugmi-amamunpm package containing malicious autopublish scripts
The npm package abina-amugmi-amamu was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package included 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.\n\nThe malicious payload modified package.json files to remove private flags and alter version numbers, enabling continuous republication of variants to pollute the npm registry. This activity was part of a larger tea.xyz token reward campaign that flooded npm with similar malicious packages, each designed to inflate developer reputation scores for token rewards.\n\nThe attack vector involved publishing a compromised package directly to npm that contained self-replicating functionality, allowing it to spawn multiple derivative packages without direct maintainer intervention for each variant.
Indicators of compromise
- Packages
- abina-amugmi-amamu
Remediation
- Remove abina-amugmi-amamu and any derivative packages from npm installations
- Audit npm package.json files for unexpected modifications or version changes
- Review npm account activity and access logs for unauthorized package publications
- Monitor for and remove any auto-generated derivative packages with randomized or Indonesian-themed names published during the affected timeframe
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-6qr7-2c65-h2hm · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugmi-amamu (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-amugmi-amamu-npm-13hcch
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 - 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 - 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
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. 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