Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in test-dev-sync

Malware was discovered in the npm package test-dev-sync. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

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

The npm package test-dev-sync was found to contain malware. According to the GitHub Advisory (GHSA-c2gc-7pfc-7fjf), any system that has installed or executed this package should be treated as fully compromised.\n\nThe advisory recommends that all secrets and cryptographic keys stored on affected computers be rotated immediately from a different, uncompromised system. While the malicious 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, as the attacker may have gained full control of the system.\n\nUsers should assume complete system compromise and take appropriate incident response measures.

Indicators of compromise

Packages
  • test-dev-sync

Remediation

  • Immediately rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
  • Remove the test-dev-sync package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had this package installed or running
  • Monitor affected systems for signs of persistent malware or unauthorized access
  • Review system logs and network traffic for indicators of compromise
  • Consider full system reimaging if the package was installed on production or sensitive systems

Sources

  1. GitHub Advisory GHSA-c2gc-7pfc-7fjf · GitHub Advisory Database

Cite this entry

"Malware in test-dev-sync." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 1, 2026; last updated August 1, 2026. https://supplychainattack.org/incident/malware-in-test-dev-sync-fjzl5z

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malware in test-dev-exec

    The npm package test-dev-exec contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. resolvedcritical

    Malware in test-dev-link

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

    npmCompromised package
  3. resolvedcritical

    Malware in @moxfive-llc/common

    Malware was discovered in the npm package @moxfive-llc/common. 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
  4. resolvedcritical

    Malware in test-dev-dispatch

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

    npmCompromised package