Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in abina-amugmi-amanamu (npm)

The npm package abina-amugmi-amanamu contains malicious code designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, removes private flags, and continuously pollutes the npm registry with variants.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Registry pollution; potential installation by developers unaware of malicious intent
Ecosystems
Attack vectors
Affected entities
  • abina-amugmi-amanamunpm package containing malicious autopublish scripts

The npm package abina-amugmi-amanamu was identified as part of a coordinated campaign to flood the npm registry with malicious packages. The package contains autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that execute automatically upon installation.

The malicious payload modifies the package.json file to remove private flags and alter version numbers. It then generates derivative packages with randomized names, many using Indonesian-themed naming conventions, and automatically republishes them to the npm registry. This behavior is designed to artificially inflate developer reputation scores within the tea.xyz token reward protocol.

The attack represents a form of registry pollution that degrades the quality and trustworthiness of the npm ecosystem. Developers who unknowingly install this package would trigger the autopublish mechanism, contributing to the proliferation of malicious variants.

The incident was identified and documented by the OpenSSF's malicious-packages project, which tracks such coordinated supply chain attacks.

Indicators of compromise

Packages
  • abina-amugmi-amanamu

Remediation

  • Remove abina-amugmi-amanamu and any derivative packages from your project dependencies immediately
  • Audit your npm registry and project history for any packages with randomized or suspicious names that may have been auto-published
  • Review package.json and lock files for unexpected changes or version modifications
  • Consider using npm audit and security scanning tools to detect similar malicious packages
  • Report any suspicious packages to npm security team
  • Monitor tea.xyz-related package campaigns and block known malicious patterns

Sources

  1. GitHub Advisory GHSA-qhm4-v9jm-xm49 · GitHub Advisory Database

Cite this entry

"Malicious code in abina-amugmi-amanamu (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-amanamu-npm-1k46j1

Suggest a correction

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

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

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. 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