Malicious code in abina-ami-agu (npm)
The npm package abina-ami-agu contains malicious code designed to automatically generate and republish derivative packages with randomized names. The attack is part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages to inflate developer reputation scores.
- Disclosed
- Last updated
- Blast radius
- npm registry; developers who installed abina-ami-agu and its derivative packages
- Ecosystems
- Attack vectors
- Affected entities
- abina-ami-agunpm package containing malicious autopublish scripts
The npm package abina-ami-agu 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.\n\nThe malicious payload modifies package.json to remove private flags and alter version numbers, enabling continuous republication of variants to the npm registry. The attack's primary objective is to inflate developer reputation scores for tea protocol token rewards by polluting the registry with numerous derivative packages.\n\nThis incident is part of a larger coordinated campaign that flooded npm with similar malicious packages. The attack was identified and credited to the OpenSSF's malicious-packages repository.
Indicators of compromise
- Packages
- abina-ami-agu
Remediation
- Remove abina-ami-agu and any derivative packages from your project dependencies
- Audit your npm install history for any packages with randomized or suspicious names published around the same timeframe
- Review package.json and lock files for unexpected changes or version modifications
- Monitor your npm account for unauthorized package publications
- Report any suspicious packages to npm security team
Sources
- GitHub Advisory GHSA-vx42-9pq5-8pw2 · GitHub Advisory Database
Cite this entry
"Malicious code in abina-ami-agu (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-ami-agu-npm-kuchpb
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