Malicious code in abina-amugmi-amamgu (npm)
The npm package abina-amugmi-amamgu contains malicious autopublish scripts designed to automatically generate and republish derivative packages with randomized names to the npm registry. This is part of a broader tea.xyz token reward campaign that floods npm with malicious packages to inflate developer reputation scores.
- Disclosed
- Last updated
- Blast radius
- Registry-wide pollution; affects developers who install this package and any derivative packages it auto-publishes
- Ecosystems
- Attack vectors
- Affected entities
- abina-amugmi-amamgunpm package containing autopublish malicious scripts
The npm package abina-amugmi-amamgu was identified as containing malicious code as part of the tea.xyz token reward campaign. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automatically generate and publish derivative packages with randomized names, primarily using Indonesian-themed naming conventions.
The malicious payload modifies package.json to remove private flags and alter version numbers, enabling continuous republication of variants to pollute the npm registry. The attack is designed to artificially inflate developer reputation scores for tea protocol token rewards.
This incident was identified by the OpenSSF's malicious-packages project and represents part of a coordinated campaign flooding npm with similar malicious packages. Installation of this package triggers the autopublish mechanism, which then generates additional malicious packages on the registry.
Indicators of compromise
- Packages
- abina-amugmi-amamgu
Remediation
- Remove abina-amugmi-amamgu and any derivative packages from your dependencies immediately
- Audit your npm registry and project dependencies for other packages from the tea.xyz token reward campaign
- Review package.json and lock files for unexpected changes or new dependencies
- Monitor your npm account for unauthorized package publications
- Report any suspicious packages to npm security team
- Consider using npm audit and supply chain security tools to detect similar malicious packages
Sources
- GitHub Advisory GHSA-x4gh-44cm-wj2w · GitHub Advisory Database
Cite this entry
"Malicious code in abina-amugmi-amamgu (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-amugmi-amamgu-npm-1qlxvx
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in pfp-forms-sme-loan (npm)
The npm package pfp-forms-sme-loan contains malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under well1.site. Any system that imported this package should be considered compromised.
npmCompromised packageMalicious commit - containedcritical
Malicious code in akamaijs-sensor (npm)
The npm package akamaijs-sensor contained malicious code that executed arbitrary JavaScript via hidden Unicode-encoded bytes and established a command-and-control channel through a Google Calendar dead-drop. The package was designed to run attacker-authored code in the consumer's Node process when the sensor() API was called.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in twilio-hackerone-poc-afe6937c (npm)
The npm package twilio-hackerone-poc-afe6937c contained malicious preinstall/postinstall scripts that exfiltrate host metadata and environment variables to an external webhook, spawn a persistent daemon process, and attempt cross-tenant code injection in shared environments.
npmCompromised packageMalicious commit - containedcritical
Malicious code in @wololasod/tiny-id (npm)
The npm package @wololasod/tiny-id contained obfuscated malicious code that downloads and executes platform-specific remote executables on Windows and Linux systems. The dropper was embedded in both the main entry point (dist/index.cjs) and the TypeScript types file (dist/index.d.ts), disguised as a tiny ID generator.
npmCompromised packageMalicious commit