Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in abih-poke3 (npm)

The npm package abih-poke3 contains malicious autopublish scripts that automatically generate and republish derivative packages with randomized names to the npm registry. This appears to be part of a tea.xyz token reward campaign designed to inflate developer reputation scores by polluting the registry with numerous variant packages.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Registry-wide pollution; affects any developer who installs abih-poke3 or its auto-generated derivative packages
Ecosystems
npm
Attack vectors
Compromised packageMalicious commit
Affected entities
  • abih-poke3npm package containing autopublish scripts designed to generate and republish derivative packages with randomized names

The npm package abih-poke3 was identified as containing malicious code as part of a broader tea.xyz token reward campaign that flooded the npm registry. The package includes autopublish scripts (such as auto.js, autopublish.js, autopublish2.js, and autopublish3.js) designed to automatically generate and republish derivative packages.\n\nThe malicious payload modifies package.json to remove private flags and change version numbers, then generates random package names (primarily Indonesian-themed variants, with some English variants) and continuously republishes them to the npm registry. This activity is intended to artificially inflate developer reputation scores for tea protocol token rewards.\n\nThe incident was identified by Amazon Inspector and credited to the OpenSSF's malicious-packages repository. The attack represents a supply chain pollution vector that affects the integrity of the npm registry and any developer who installs the affected package or its auto-generated derivatives.

Indicators of compromise

Packages
  • abih-poke3

Remediation

  • Remove abih-poke3 and any derivative packages with randomized names from your dependencies
  • Audit npm package.json and lock files for unexpected or unfamiliar package names, particularly those with Indonesian or random naming patterns
  • Review npm account activity and publishing history for unauthorized package publications
  • Monitor npm registry for derivative packages that may have been auto-generated from this malicious package
  • Use npm audit and security scanning tools to detect similar autopublish malware patterns

Sources

  1. GitHub Advisory GHSA-rpxm-gjm3-5qw6 · GitHub Advisory Database

Cite this entry

"Malicious code in abih-poke3 (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 14, 2026; last updated August 14, 2026. https://supplychainattack.org/incident/malicious-code-in-abih-poke3-npm-2mh2jw

Suggest a correction

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

Related incidents

  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. 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
  3. 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
  4. resolvedcritical

    Malicious code in akamaijs-sensorv1 (npm)

    The npm package akamaijs-sensorv1, which advertises itself as an Akamai Bot Manager sensor generator, contains malicious code that executes hidden dynamic code and fetches remote instructions from a Google Calendar-based command-and-control channel. The package uses invisible Unicode characters to conceal executable code and establishes a covert remote-code execution sink controlled by an attacker-owned email account.

    npmCompromised packageMalicious commit