Which versions of vite-linting-js are malicious?

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

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

Remove vite-linting-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-linting-js — how do I know if it already compromised me?

If vite-linting-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-linting-js part of a known attack campaign?

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

Search your lockfiles and build artifacts for vite-linting-js (version 1.0.1).

Malicious package

vite-linting-jsnpm

Advisory published Sep 26, 2025Updated Dec 2, 2025

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

Malicious code in vite-linting-js (npm)

MAL-2025-47741

Immediate action

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

npm uninstall vite-linting-js

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

503ad078882e68f288a86f57cb260fad0c1e886875c8ac81425bc06ad5954c89

2fe86c4c7bd4713c8bb70ad88c5953233cf1ee7ab936011c58470172226dfb32

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vite-linting-js (version 1.0.1).
If you installed it — respond
Remove vite-linting-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-linting-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-linting-js on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05191RLUA-2025-05985

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vite-linting-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