Malware in axl-ui
Malware was discovered in the npm package axl-ui, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with axl-ui installed or running
- Ecosystems
- Attack vectors
- Affected entities
- axl-ui
The npm package axl-ui was found to contain malware. According to the GitHub Advisory (GHSA-f4w9-3fvx-q5xw), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory warns that all secrets and keys stored on affected computers should be rotated immediately from a different, unaffected system. 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 initial compromise, given that the attacker may have gained full control of the system.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems that installed or ran the affected package.
Indicators of compromise
- Packages
- axl-ui
Remediation
- Immediately remove the axl-ui package from all affected systems
- Rotate all secrets, API keys, and credentials from a different, unaffected computer
- Assume full system compromise and conduct forensic analysis to identify any additional malicious software
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Audit all systems that may have been accessed using credentials stored on compromised machines
Sources
- GitHub Advisory GHSA-f4w9-3fvx-q5xw · GitHub Advisory Database
Cite this entry
"Malware in axl-ui." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 25, 2026. https://supplychainattack.org/incident/malware-in-axl-ui-1oosou
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit