Which versions of @vitets/vite-ts are malicious?

The following npm versions of @vitets/vite-ts are flagged malicious: 1.5.10. Treat any of these as compromised.

How do I remediate @vitets/vite-ts if I installed it?

@vitets/vite-ts is a typosquat — you almost certainly intended a legitimately-named package. Remove @vitets/vite-ts, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

If @vitets/vite-ts 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 @vitets/vite-ts part of a known attack campaign?

Yes — @vitets/vite-ts is associated with the IN-MAL-2026-010365 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 @vitets/vite-ts 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 @vitets/vite-ts (version 1.5.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vitets/vite-ts across your stack and pipelines.

Malicious package

@vitets/vite-tsnpm

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

MAL-2026-10528

Immediate action

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

npm uninstall @vitets/vite-ts

What this malware does

Package is published as @vitets/vite-ts and copies the legitimate Vite project's author (Evan You), README, homepage (vitejs.dev), and repository (github.com/vitejs/vite) to impersonate the real vite / @vitejs/* packages, and declares a bin entry named vite so consumers who install it and run the vite CLI execute the package's bin/vite.js. After ~5KB of whitespace padding, bin/vite.js contains an obfuscated payload that uses a custom string-scramble routine to hide identifiers (require, child_process, spawn, eval, hostnames, HTTP/JSON-RPC method names) as numeric indices into a reconstructed string table, defeating static IOC scanning. The decoded routine performs an HTTPS GET and a JSON-RPC POST to remote hosts, XORs the response with a key fetched from a second endpoint, runs eval(r) on the result, and additionally child_process.spawns a detached background process to execute it (with detached:true, windowsHide:true). This gives the publisher arbitrary code execution on the developer's machine every time the vite CLI is invoked, with no integrity check on the fetched code. The package's dist/ bundle also contains base64+Buffer decode primitives consistent with additional obfuscated payload handling.

Malicious versions

1 flagged

1.5.10

Indicators of compromise (SHA-256)

8fe093d0d0fa83ab20aa57e9d9c8500e03a25ead578ff351fdc3609118cf5ecf

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @vitets/vite-ts (version 1.5.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vitets/vite-ts across your stack and pipelines.
If you installed it — respond
@vitets/vite-ts is a typosquat — you almost certainly intended a legitimately-named package. Remove @vitets/vite-ts, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @vitets/vite-ts 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 @vitets/vite-ts 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. @vitets/vite-ts on npm has been identified as a malicious package (version 1.5.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010365

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @vitets/vite-ts-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.

Malware detection Runtime egress monitoring