Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malicious code in abih-poke14 (npm)

The npm package abih-poke14 contained malicious code designed to automatically generate and publish 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 systems running its autopublish scripts.
Ecosystems
Attack vectors
Affected entities
  • abih-poke14npm package containing malicious autopublish scripts

The npm package abih-poke14 was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package included autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) that automatically generated and published derivative packages with randomized names, primarily Indonesian-themed but also English variants.\n\nThe malicious payload modified package.json files to remove private flags and alter version numbers, enabling continuous republication of variants to pollute the npm registry. This activity was part of a larger campaign associated with the tea.xyz token reward initiative that resulted in numerous malicious packages being published to npm.\n\nThe attack vector involved publishing a compromised package directly to the npm registry. Developers who installed abih-poke14 would have had the autopublish scripts execute, potentially generating additional malicious packages and contributing to registry pollution.

Indicators of compromise

Packages
  • abih-poke14

Remediation

  • Remove abih-poke14 from all projects and dependencies
  • Audit npm package.json files for unexpected modifications or version changes
  • Review npm account activity and publishing history for unauthorized package publications
  • Monitor for and remove any derivative packages with randomized names that may have been generated by the autopublish scripts
  • Update to a clean version of any affected projects without the malicious dependency

Sources

  1. GitHub Advisory GHSA-h7mw-fw62-ww2h · GitHub Advisory Database

Cite this entry

"Malicious code in abih-poke14 (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-poke14-npm-1t7pfm

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 bcc-design-icons (npm)

    bcc-design-icons@9999.0.0 on npm contains malicious postinstall script that exfiltrates hostname and package name to attacker-controlled IP 91.201.215.48:8000. The package lacks expected icon-library functionality and exhibits characteristics of a dependency-confusion attack targeting internal/private npm installers.

    npmDependency confusionCompromised package
  2. containedcritical

    Malicious code in runtime-health (npm)

    The npm package runtime-health version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.

    npmCompromised package
  3. resolvedcritical

    Malicious code in core-tailwindcss-utility (npm)

    core-tailwindcss-utility, an npm package falsely advertised as a Tailwind CSS utility, contains malicious code that fetches and executes arbitrary Node.js code from a remote C2 server. The package includes suspicious dependencies for credential theft and remote communication.

    npmCompromised package
  4. resolvedcritical

    Malware in ulebkit

    The npm package ulebkit contained malware that provided full system compromise to attackers. Any computer with the package installed or running should be considered fully compromised.

    npmCompromised package