Which versions of @vite-js/ui are malicious?

The following npm versions of @vite-js/ui are flagged malicious: 7.15.16. Treat any of these as compromised.

How do I remediate @vite-js/ui if I installed it?

@vite-js/ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @vite-js/ui — how do I know if it already compromised me?

If @vite-js/ui 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.

Is @vite-js/ui part of a known attack campaign?

Yes — @vite-js/ui is associated with the IN-MAL-2026-008609 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @vite-js/ui across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @vite-js/ui (version 7.15.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vite-js/ui across your stack and pipelines.

Malicious package

@vite-js/uinpm

Malicious code in @vite-js/ui (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-7021

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @vite-js/ui

What this malware does

Package @vite-js/[email protected] impersonates the legitimate vite package: it copies the author name, homepage (vitejs.dev), README, and exposes a bin named vite, but publishes under an unrelated scope. Its bin/vite.js contains the legitimate Vite launcher followed by an appended obfuscated IIFE that uses a seeded permutation cipher and placeholder-swap encoding to reconstruct the Function constructor name and a decoded payload string, then invokes Function(...) with the decoded body — an eval-equivalent RCE primitive that fires whenever a developer runs the vite CLI provided by this package. The obfuscation shape (custom character-shuffle descrambler, hex/comma-obfuscated string tables) is combined with runtime dependencies uncharacteristic of a build tool (@solana/web3.js, axios, socket.io-client, form-data), consistent with the wallet-stealer / exfiltration family seen in prior npm typosquat incidents. Running npx vite or the installed vite bin from this package executes attacker-controlled code on the developer's machine.

Malicious versions

1 flagged

7.15.16

Indicators of compromise (SHA-256)

914257e4d1eecae3fc48e98c8a2a406ed8021ed159c4a43a96c57453d0a1f320

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @vite-js/ui (version 7.15.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vite-js/ui across your stack and pipelines.
If you installed it — respond
@vite-js/ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @vite-js/ui 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 @vite-js/ui 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

No. @vite-js/ui on npm has been identified as a malicious package (version 7.15.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008609

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @vite-js/ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring