Malware in class-weaver
The npm package class-weaver was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All affected systems should be considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- class-weaver
The npm package class-weaver was identified as containing malware. According to the GitHub Advisory (GHSA-jx4m-wmh7-wmhr), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malware grants outside entities full control of affected systems. Immediate action is required to rotate all secrets and keys stored on compromised computers from a different, unaffected system.\n\nWhile the package should be removed, the advisory notes that full control may have been given to an outside entity, meaning there is no guarantee that removing the package alone will remove all malicious software resulting from the installation. A comprehensive security review and remediation of affected systems is necessary.
Indicators of compromise
- Packages
- class-weaver
Remediation
- Immediately isolate any computer with class-weaver installed from the network
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Remove the class-weaver package from all affected systems
- Perform a comprehensive security audit and malware scan of all affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Audit all systems that may have been accessed from compromised machines
Sources
- GitHub Advisory GHSA-jx4m-wmh7-wmhr · GitHub Advisory Database
Cite this entry
"Malware in class-weaver." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-class-weaver-1pjgn2
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- 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 - 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 - 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 - 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