Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in class-synth

The npm package class-synth was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-c6cg-h94m-mv67 was published on 2026-07-14.

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

The npm package class-synth 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\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software resulting from the installation.\n\nThis is classified as a critical-severity supply chain attack due to the complete system compromise potential and the need for comprehensive remediation beyond simple package removal.

Indicators of compromise

Packages
  • class-synth

Remediation

  • Immediately isolate any computer that has class-synth installed or running from the network
  • Rotate all secrets, API keys, credentials, and cryptographic keys from a different, uncompromised computer
  • Remove the class-synth package from the affected system
  • Perform a comprehensive security audit and malware scan of the affected system
  • Consider full system reimaging or replacement if complete compromise is suspected
  • Review access logs and audit trails for any unauthorized activity during the period the package was installed
  • Notify any systems or services that may have been accessed from the compromised computer

Sources

  1. GitHub Advisory GHSA-c6cg-h94m-mv67 · GitHub Advisory Database

Cite this entry

"Malware in class-synth." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-class-synth-1vdhcy

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