Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in test-pkg-yarn

Malware was distributed via the npm package test-pkg-yarn, resulting in full system compromise. All affected systems should be considered fully compromised and all secrets and keys rotated from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • test-pkg-yarn

The npm package test-pkg-yarn contained malware that compromised any system where it was installed or executed. According to the GitHub advisory, computers with this package installed should be considered fully compromised, with potential for complete control by an outside entity.\n\nThe advisory recommends immediate removal of the package and rotation of all secrets and keys from a different, unaffected computer. However, due to the level of system compromise, there is no guarantee that removing the package alone will eliminate all malicious software that may have been installed as a result.\n\nThis incident was disclosed via GitHub Security Advisory GHSA-r653-6655-p467.

Indicators of compromise

Packages
  • test-pkg-yarn

Remediation

  • Remove the test-pkg-yarn package immediately
  • Rotate all secrets, keys, and credentials from a different, unaffected computer
  • Perform a full security audit and malware scan of affected systems
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure
  • Review access logs and monitor for unauthorized activity on systems that had this package installed

Sources

  1. GitHub Advisory GHSA-r653-6655-p467 · GitHub Advisory Database

Cite this entry

"Malware in test-pkg-yarn." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malware-in-test-pkg-yarn-f75zvy

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. containedcritical

    Malicious code in stillm4ddpocs-demo-sprocket (npm)

    The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.

    npmCompromised packageDependency confusion
  3. containedcritical

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

    The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.

    npmCompromised package
  4. containedcritical

    Malware in hydration-dim-kit

    Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package