Malicious code in @gleamkit/engine.io (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (008464ca4d7ba15b4b8c6d3a979586c61bd527aef3a209571d28c0ba912403ae) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (89a1d2d57663ad7d9894bb0707c0594e4ae971505ee2e9beed9566fcf769744f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The @gleamkit/engine.io npm package in versions 6.6.3, 6.6.4, and 6.6.5 has been identified as containing malicious code or relying on a dependency that does. This malicious code can lead to full compromise of any computer where the package is installed or running. The advisory warns that simply removing the package may not fully remediate the infection, as the attacker may have established persistent control. Immediate rotation of all secrets and keys stored on the compromised system is recommended to prevent further unauthorized access.
Potential Impact
Systems with the affected versions of @gleamkit/engine.io installed are considered fully compromised. Attackers may have gained full control, potentially exposing all stored secrets and keys. This can lead to unauthorized access, data theft, and further system compromise. The presence of malicious code in a widely used npm package poses a significant risk to the integrity and confidentiality of affected systems.
Mitigation Recommendations
Remove the affected versions (=6.6.3, =6.6.4, =6.6.5) of the @gleamkit/engine.io package immediately. Rotate all secrets and keys stored on the compromised system from a separate, secure device. Because full control may have been given to an attacker, consider rebuilding the system from a known good backup or reinstalling the operating system to ensure complete removal of malicious software.
Malicious code in @gleamkit/engine.io (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (008464ca4d7ba15b4b8c6d3a979586c61bd527aef3a209571d28c0ba912403ae) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (89a1d2d57663ad7d9894bb0707c0594e4ae971505ee2e9beed9566fcf769744f) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The @gleamkit/engine.io npm package in versions 6.6.3, 6.6.4, and 6.6.5 has been identified as containing malicious code or relying on a dependency that does. This malicious code can lead to full compromise of any computer where the package is installed or running. The advisory warns that simply removing the package may not fully remediate the infection, as the attacker may have established persistent control. Immediate rotation of all secrets and keys stored on the compromised system is recommended to prevent further unauthorized access.
Potential Impact
Systems with the affected versions of @gleamkit/engine.io installed are considered fully compromised. Attackers may have gained full control, potentially exposing all stored secrets and keys. This can lead to unauthorized access, data theft, and further system compromise. The presence of malicious code in a widely used npm package poses a significant risk to the integrity and confidentiality of affected systems.
Mitigation Recommendations
Remove the affected versions (=6.6.3, =6.6.4, =6.6.5) of the @gleamkit/engine.io package immediately. Rotate all secrets and keys stored on the compromised system from a separate, secure device. Because full control may have been given to an attacker, consider rebuilding the system from a known good backup or reinstalling the operating system to ensure complete removal of malicious software.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10476
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-gvp7-6g9j-r5c6"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff4a68715ace432efc45
Added to database: 07/14/2026, 09:20:10 UTC
Last enriched: 07/14/2026, 09:24:04 UTC
Last updated: 07/22/2026, 19:20:39 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.