Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedhigh

Malicious code in abina-amugi-anuhabumai (npm)

The npm package abina-amugi-anuhabumai contains malicious autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The payload 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-amugi-anuhabumainpm package containing autopublish scripts

The npm package abina-amugi-anuhabumai 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 upon installation.

The malicious payload modifies package.json to remove private flags and alter version numbers, then generates random Indonesian-themed and English-themed package names. These derivative packages are automatically republished to the npm registry, creating a cascade of polluted packages.

The underlying motivation is to artificially inflate developer reputation scores within the tea.xyz token reward campaign, allowing attackers to claim unearned protocol tokens. This represents a supply chain attack that compromises registry integrity and wastes developer resources.

The package was identified by Amazon Inspector and credited to the OpenSSF malicious-packages repository.

Indicators of compromise

Packages
  • abina-amugi-anuhabumai

Remediation

  • Remove abina-amugi-anuhabumai and any derivative packages from npm environments immediately
  • Audit npm package.json files and lock files for unexpected or unfamiliar packages, particularly those with randomized or unusual names
  • Review npm account activity and token usage for any unauthorized package publications
  • Monitor npm registry for additional packages from the same campaign using OpenSSF malicious-packages database
  • Implement package allowlisting and automated scanning in CI/CD pipelines to prevent installation of known malicious packages

Sources

  1. GitHub Advisory GHSA-cr72-xvxp-c3q5 · GitHub Advisory Database

Cite this entry

"Malicious code in abina-amugi-anuhabumai (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-anuhabumai-npm-1ka2io

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 pfp-forms-sme-loan (npm)

    The npm package pfp-forms-sme-loan contains malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under well1.site. Any system that imported this package should be considered compromised.

    npmCompromised packageMalicious commit
  2. containedcritical

    Malicious code in akamaijs-sensor (npm)

    The npm package akamaijs-sensor contained malicious code that executed arbitrary JavaScript via hidden Unicode-encoded bytes and established a command-and-control channel through a Google Calendar dead-drop. The package was designed to run attacker-authored code in the consumer's Node process when the sensor() API was called.

    npmCompromised packageMalicious commit
  3. resolvedcritical

    Malicious code in @velliajs/discord (npm)

    @velliajs/discord, a malicious npm package masquerading as a discord.js clone, contained two hostile mechanisms: an unpinned private git dependency with embedded GitHub PAT enabling arbitrary code injection on install, and a hidden runtime kill-switch that gates bot functionality based on a remote allow-list. Two live GitHub Personal Access Tokens were hardcoded in the package.

    npmCompromised packageMalicious commit
  4. resolvedcritical

    Malicious code in twilio-hackerone-poc-afe6937c (npm)

    The npm package twilio-hackerone-poc-afe6937c contained malicious preinstall/postinstall scripts that exfiltrate host metadata and environment variables to an external webhook, spawn a persistent daemon process, and attempt cross-tenant code injection in shared environments.

    npmCompromised packageMalicious commit