Malware in @gleamkit/engine.io
Malware discovered in the npm package @gleamkit/engine.io. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @gleamkit/engine.io
A malicious package named @gleamkit/engine.io was published to npm and contains malware. According to the GitHub Advisory (GHSA-gvp7-6g9j-r5c6), any computer that has 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, uncompromised computer. 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 package installation.\n\nGiven the severity of the compromise, affected users should assume complete system takeover and treat the affected machines as potentially hostile until thoroughly remediated.
Indicators of compromise
- Packages
- @gleamkit/engine.io
Remediation
- Immediately remove the @gleamkit/engine.io package from all systems
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Assume complete system compromise and perform full forensic analysis
- Consider the affected system(s) as potentially hostile and plan for complete rebuild or replacement
- Audit all systems that may have been accessed from the compromised machine(s)
- Monitor for any unauthorized access or lateral movement from affected systems
Sources
- GitHub Advisory GHSA-gvp7-6g9j-r5c6 · GitHub Advisory Database
Cite this entry
"Malware in @gleamkit/engine.io." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 13, 2026; last updated July 13, 2026. https://supplychainattack.org/incident/malware-in-gleamkit-engine-io-l9r64x
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