Malware in gulp-jscrambler
Malware was discovered in the npm package gulp-jscrambler, resulting in full system compromise for any installation. All secrets and keys on affected systems should be rotated immediately from a clean machine.
- Disclosed
- Last updated
- Blast radius
- Any system with gulp-jscrambler installed
- Ecosystems
- Attack vectors
- Affected entities
- gulp-jscrambler
A critical malware incident was identified in the npm package gulp-jscrambler. According to the GitHub Advisory (GHSA-2cjx-v4hm-f5gf), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised machine. 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 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
- gulp-jscrambler
Remediation
- Immediately rotate all secrets, API keys, and credentials from a clean, uncompromised computer
- Remove the gulp-jscrambler package from all affected systems
- Conduct a full security audit and forensic analysis of any system that had gulp-jscrambler installed
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if full compromise is suspected
Sources
- GitHub Advisory GHSA-2cjx-v4hm-f5gf · GitHub Advisory Database
Cite this entry
"Malware in gulp-jscrambler." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-gulp-jscrambler-143s3q
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 angylarjs (npm)
Malicious code was discovered in the angylarjs npm package. The package was identified by the OpenSSF malicious-packages project and reported via GitHub Security Advisory GHSA-qqc2-6x9j-cm25.
npmCompromised package - resolvedcritical
Malware in zaldy-baileys
Malware was discovered in the npm package zaldy-baileys, resulting in full system compromise for any computer with the package installed or running. The advisory recommends treating affected systems as fully compromised and rotating all secrets and keys from a different computer.
npmCompromised package - activecritical
Malware in ssweb-wp
Malware discovered in the npm package ssweb-wp. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in @fhkry/baileys
Malware was discovered in the npm package @fhkry/baileys. The package grants full control of affected systems to an outside entity and compromises all secrets and keys stored on those systems.
npmCompromised package