Malware in quoting
The npm package 'quoting' was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-x8q6-66jr-wmp3 was published on 2026-06-30.
- Disclosed
- Last updated
- Blast radius
- Any system with the quoting package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- quoting
The npm package 'quoting' was identified as containing malware. According to the GitHub Security Advisory GHSA-x8q6-66jr-wmp3, any computer that has this package installed or running should be considered fully compromised.
The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.
This represents a critical supply chain attack through a compromised package in the npm ecosystem. Systems administrators and developers should immediately audit their environments for the presence of this package and take appropriate remediation steps.
Indicators of compromise
- Packages
- quoting
Remediation
- Immediately identify all systems with the quoting package installed
- Rotate all secrets, API keys, and credentials from a separate, uncompromised computer
- Remove the quoting package from all affected systems
- Conduct a full security audit of affected systems for additional malware or persistence mechanisms
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
- Consider full system reimaging if the compromise is suspected to be extensive
Sources
- GitHub Advisory GHSA-x8q6-66jr-wmp3 · GitHub Advisory Database
Cite this entry
"Malware in quoting." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-quoting-jq395p
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