Which versions of vite-binding-js are malicious?

The following npm versions of vite-binding-js are flagged malicious: 7.11.8. Treat any of these as compromised.

How do I remediate vite-binding-js if I installed it?

Remove vite-binding-js 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.

I already installed vite-binding-js — how do I know if it already compromised me?

If vite-binding-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is vite-binding-js part of a known attack campaign?

Yes — vite-binding-js is associated with the RLMA-2025-04725, RLUA-2025-05979 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-binding-js across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vite-binding-js (version 7.11.8).

Malicious package

vite-binding-jsnpm

Advisory published Aug 28, 2025Updated Dec 2, 2025

vite-binding-js is a confirmed malicious npm package (MAL-2025-41613) that executes malicious code on install (malicious version 7.11.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-binding-js (npm)

MAL-2025-41613

Immediate action

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

npm uninstall vite-binding-js

Malicious versions

1 flagged

7.11.8

Indicators of compromise (SHA-256)

0ae7801a118d57e42b1e181db6629d5481184592c5d9c06913708a0a3a764af2

e7c530bd6e48b2e24e7b3c64c7c7312dde166c2e199f059e538507709a4a859f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vite-binding-js (version 7.11.8).
If you installed it — respond
Remove vite-binding-js 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 vite-binding-js was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

RLMA-2025-04725RLUA-2025-05979

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vite-binding-js-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

Explore

All malware advisories How O3 detects malware Vulnerability database