Malware in vxui-react
Malware was discovered in the npm package vxui-react, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with vxui-react installed or running
- Ecosystems
- Attack vectors
- Affected entities
- vxui-react
The npm package vxui-react was found to contain malware. According to the GitHub Advisory (GHSA-783r-3958-xf8p), any computer with 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 from a different, uncompromised 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 the potential for full system access by the attacker.\n\nUsers should assume complete system compromise and take appropriate incident response measures.
Indicators of compromise
- Packages
- vxui-react
Remediation
- Remove the vxui-react package immediately from all systems
- Rotate all secrets, API keys, credentials, and authentication tokens from a clean, uncompromised computer
- Assume full system compromise and conduct forensic analysis
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system rebuild or replacement if the system handles sensitive data
- Audit any systems that may have been accessed from the compromised machine
Sources
- GitHub Advisory GHSA-783r-3958-xf8p · GitHub Advisory Database
Cite this entry
"Malware in vxui-react." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 26, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-vxui-react-7d8hb8
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package