Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in abina-amugi-ai (npm)

The npm package abina-amugi-ai contained malicious code designed to automatically generate and republish derivative packages with randomized names to the npm registry. The attack was part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Registry-wide pollution; affects any developer who installed abina-amugi-ai or its auto-generated derivative packages.
Ecosystems
Attack vectors
Affected entities
  • abina-amugi-ainpm package containing malicious autopublish scripts

The npm package abina-amugi-ai 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 modifies package.json to remove private flags and alter version numbers, enabling continuous republication of variants to pollute the npm registry. This attack was part of a larger coordinated campaign associated with the tea.xyz token reward system, which flooded npm with numerous similar malicious packages intended to inflate developer reputation scores for token rewards.\n\nThe attack vector involved publishing a compromised package directly to npm that contained embedded malicious scripts. Upon installation, these scripts would execute and generate additional malicious packages, creating a cascading pollution effect across the registry.

Indicators of compromise

Packages
  • abina-amugi-ai

Remediation

  • Remove abina-amugi-ai and any derivative packages with randomized Indonesian or English-themed names from your dependencies immediately
  • Audit your npm install history and package-lock.json for any unexpected packages installed during the period when abina-amugi-ai was available
  • Review your npm account for any unauthorized package publications or modifications
  • Monitor your projects for unexpected autopublish or auto-generation scripts in node_modules
  • Consider using npm audit and security scanning tools to detect similar malicious packages
  • Report any suspicious packages to npm security team

Sources

  1. GitHub Advisory GHSA-mm55-6w48-r53j · GitHub Advisory Database

Cite this entry

"Malicious code in abina-amugi-ai (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-ai-npm-s8nl3w

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. 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
  2. resolvedcritical

    Malicious code in @syncraft-labs/core (npm)

    The npm package @syncraft-labs/core contained obfuscated malicious code in its ESM build that executes on import, fetching and executing attacker-controlled payloads from Ethereum blockchain via JSON-RPC endpoints. The CommonJS build was clean, indicating targeted injection into the ESM entry point.

    npmCompromised packageMalicious commit
  3. resolvedcritical

    Malicious code in localize-translate (npm)

    The npm package localize-translate contained malicious code in its postinstall lifecycle script that collected host identifiers and beaconed them to an attacker-controlled endpoint (gigww0v7.instances.poc.jchunt.top) without user consent. The reconnaissance callback fired automatically on every installation, collecting hostname, platform, architecture, Node version, package name, and timestamp.

    npmCompromised packageMalicious commit
  4. containedcritical

    Malicious code in mutex-plus (npm)

    The npm package mutex-plus contains hidden malicious code that enables remote code execution when a callback object with a specific jobId hash is passed to runExclusive(). The payload is encrypted at rest in lib/plusMutex.min.js and decrypted using the jobId as a key, then executed as a detached Node.js process.

    npmCompromised packageMalicious commit