Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in abina-amogoi-anuhui (npm)

The npm package abina-amogoi-anuhui contained malicious autopublish scripts 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.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Registry pollution; potential impact on developers who installed the package and any downstream dependencies
Ecosystems
Attack vectors
Affected entities
  • abina-amogoi-anuhuinpm package containing malicious autopublish scripts

The npm package abina-amogoi-anuhui was identified as containing malicious code in the form of autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js). These scripts were designed to automatically generate and publish derivative packages with randomized names, primarily using Indonesian-themed naming conventions, to the npm registry.

The malicious payload modifies package.json files to remove private flags and alter version numbers, enabling continuous republication of variants. This activity was part of a larger campaign associated with the tea.xyz token reward initiative that resulted in widespread flooding of the npm registry with similar malicious packages.

The attack vector involved compromising the package itself with embedded malicious scripts rather than account takeover or maintainer compromise. The primary goal was registry pollution and reputation score manipulation for tea protocol token rewards rather than direct code execution on target systems.

The incident was identified and credited to the OpenSSF's malicious-packages repository, indicating the package has been cataloged and the threat is understood.

Indicators of compromise

Packages
  • abina-amogoi-anuhui

Remediation

  • Remove abina-amogoi-anuhui and any derivative packages from npm installations
  • Audit npm package.json files for unexpected version changes or private flag modifications
  • Review npm registry activity logs for suspicious package republication patterns
  • Implement npm package verification and scanning in CI/CD pipelines to detect autopublish scripts
  • Monitor for and remove any derivative packages generated by the malicious autopublish scripts

Sources

  1. GitHub Advisory GHSA-45gx-7ppr-vh63 · GitHub Advisory Database

Cite this entry

"Malicious code in abina-amogoi-anuhui (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-amogoi-anuhui-npm-1tuqcl

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 @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. activecritical

    Malware in @sdgdfgdfhhhfd/multiviewr

    Malware discovered in the npm package @sdgdfgdfhhhfd/multiviewr. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  4. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package