Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in abina-amib-agu (npm)

The npm package abina-amib-agu 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-amib-agu or its auto-generated derivative packages
Ecosystems
Attack vectors
Affected entities
  • abina-amib-agunpm package containing malicious autopublish scripts

The npm package abina-amib-agu 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 coordinated campaign associated with the tea.xyz token reward protocol, which flooded npm with numerous similar malicious packages intended to inflate developer reputation scores.\n\nThe attack vector involved publishing a compromised package directly to npm that would execute malicious scripts upon installation, triggering automated generation and publication of additional malicious packages. This created a cascading pollution effect across the registry.

Indicators of compromise

Packages
  • abina-amib-agu

Remediation

  • Remove abina-amib-agu and any derivative packages with randomized or Indonesian-themed names from your dependencies
  • Audit npm install logs and package-lock.json for any unexpected package installations from the affected time period
  • Review npm account activity for unauthorized package publications
  • Update to a clean version of your dependency tree and verify all packages are from trusted sources
  • Monitor for similar patterns of malicious packages associated with tea.xyz token campaigns

Sources

  1. GitHub Advisory GHSA-jg5q-9cmm-pv57 · GitHub Advisory Database

Cite this entry

"Malicious code in abina-amib-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-amib-agu-npm-1llwq4

Suggest a correction

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

  1. activecritical

    Malware in gator-client

    The npm package gator-client contains malware that grants full system compromise to an outside entity. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

    npmCompromised package
  2. activecritical

    Malware in @ai-vertical/ai-agent

    Malware was discovered in the npm package @ai-vertical/ai-agent. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

    npmAI agents & skillsCompromised package
  3. 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
  4. 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