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 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-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?

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

Malicious package

vite-linting-jsnpm

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-linting-js (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-linting-js across your stack and pipelines.
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 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-linting-js 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-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