Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in dom-weave

Malware was discovered in the npm package dom-weave, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with dom-weave installed or running
Ecosystems
Attack vectors
Affected entities
  • dom-weave

A critical malware incident was identified in the npm package dom-weave. According to the GitHub Advisory (GHSA-wx59-xwhx-3mmv), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately from a different, unaffected computer. 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\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.

Indicators of compromise

Packages
  • dom-weave

Remediation

  • Remove the dom-weave package immediately
  • Rotate all secrets, API keys, and credentials from a different, unaffected computer
  • Assume full system compromise and conduct thorough security audit
  • Consider rebuilding affected systems from clean media if possible
  • Monitor for signs of persistent malware or unauthorized access

Sources

  1. GitHub Advisory GHSA-wx59-xwhx-3mmv · GitHub Advisory Database

Cite this entry

"Malware in dom-weave." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-dom-weave-dn1bb4

Suggest a correction

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

  1. containedcritical

    Malware in @logdna-web/styles

    Malware was discovered in the npm package @logdna-web/styles. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. activecritical

    Malware in @flex-ng/filter-pipe

    Malware discovered in the npm package @flex-ng/filter-pipe. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. activecritical

    Malware in @idms-corp/auth-ui

    Malware discovered in the npm package @idms-corp/auth-ui. Systems with this package installed are considered fully compromised, with potential for complete system takeover.

    npmCompromised package
  4. activecritical

    Malware in salesforce-vscode-slds

    Malware was discovered in the npm package salesforce-vscode-slds. Any system with this package installed is considered fully compromised and poses a critical risk to stored secrets and keys.

    npmCompromised package