Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in abih-poke6 (npm)

The npm package abih-poke6 contains malicious code designed to automatically generate and publish derivative packages with randomized names to the npm registry. The package is part of a broader campaign to inflate developer reputation scores for tea protocol token rewards.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Registry-wide pollution; affects developers who install this package and any systems running its autopublish scripts
Ecosystems
Attack vectors
Affected entities
  • abih-poke6npm package containing malicious autopublish scripts

The npm package abih-poke6 was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automatically generate and republish derivative packages with randomized names, primarily Indonesian-themed but also English variants.\n\nThe malicious payload modifies package.json to remove private flags and change version numbers, enabling continuous republication of variants to pollute the npm registry. This activity is part of a larger campaign associated with the tea.xyz token reward initiative that flooded npm with similar malicious packages.\n\nThe attack vector involves compromised or intentionally malicious package publication, designed to artificially inflate developer reputation scores within the tea protocol ecosystem. Any developer who installed this package would have had the autopublish scripts execute, potentially contributing to registry pollution and unauthorized package generation.

Indicators of compromise

Packages
  • abih-poke6

Remediation

  • Remove abih-poke6 and any derivative packages it may have generated from your project dependencies
  • Audit npm package.json and lock files for unexpected or unfamiliar packages that may have been auto-generated
  • Review npm account activity and publishing history for unauthorized package publications
  • Monitor npm registry for any packages with randomized or suspicious names that may have been published by this malicious script
  • Update to a clean version of your project dependencies from a known-good state
  • Consider using npm audit and supply chain security tools to detect similar malicious packages

Sources

  1. GitHub Advisory GHSA-vxxx-g3fh-cfrh · GitHub Advisory Database

Cite this entry

"Malicious code in abih-poke6 (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-poke6-npm-0gx47o

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 rust-testing-utils (npm)

    The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.

    npmCompromised packageMalicious commit
  2. resolvedcritical

    Malicious code in @syncraft-labs/core (npm)

    The npm package @syncraft-labs/core contained obfuscated malicious code in its ESM build that executes on import, fetching and executing attacker-controlled payloads from Ethereum blockchain via JSON-RPC endpoints. The CommonJS build was clean, indicating targeted injection into the ESM entry point.

    npmCompromised packageMalicious commit
  3. resolvedcritical

    Malicious code in localize-translate (npm)

    The npm package localize-translate contained malicious code in its postinstall lifecycle script that collected host identifiers and beaconed them to an attacker-controlled endpoint (gigww0v7.instances.poc.jchunt.top) without user consent. The reconnaissance callback fired automatically on every installation, collecting hostname, platform, architecture, Node version, package name, and timestamp.

    npmCompromised packageMalicious commit
  4. containedcritical

    Malicious code in mutex-plus (npm)

    The npm package mutex-plus contains hidden malicious code that enables remote code execution when a callback object with a specific jobId hash is passed to runExclusive(). The payload is encrypted at rest in lib/plusMutex.min.js and decrypted using the jobId as a key, then executed as a detached Node.js process.

    npmCompromised packageMalicious commit