Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in player-theming

The npm package player-theming was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-j229-wx6p-5j43 was published on 2026-06-29.

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

The npm package player-theming was identified as containing malware. According to the GitHub Security Advisory, any computer that has this package installed or running should be considered fully compromised.\n\nImmediate remediation steps include rotating all secrets and keys stored on affected computers from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nThe advisory was published on 2026-06-29 and assigned identifier GHSA-j229-wx6p-5j43.

Indicators of compromise

Packages
  • player-theming

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the player-theming package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had the package installed
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-j229-wx6p-5j43 · GitHub Advisory Database

Cite this entry

"Malware in player-theming." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-player-theming-1ordh1

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 test2221 (npm)

    The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.

    npmCompromised package
  2. containedcritical

    Malware in n8n-nodes-trust-me-im-totally-safe

    Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  3. activecritical

    Malware in litespeed-cache

    Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

    npmCompromised package
  4. containedcritical

    Malware in open-worker-cli

    Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

    npmCompromised package