Which versions of vite-jsconfig are malicious?

The following npm versions of vite-jsconfig are flagged malicious: 0.3.2, 0.3.3, 0.3.4. Treat any of these as compromised.

How do I remediate vite-jsconfig if I installed it?

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

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

Yes — vite-jsconfig is associated with the GHSA-rr36-42fh-3rq5, RLMA-2025-05190, RLUA-2025-05551, RLUA-2025-05984 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-jsconfig 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-jsconfig (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-jsconfig across your stack and pipelines.

Malicious package

vite-jsconfignpm

vite-jsconfig is a confirmed malicious npm package (MAL-2025-47507) that executes malicious code on install (malicious versions 0.3.2, 0.3.3, 0.3.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-jsconfig (npm)

MAL-2025-47507

Immediate action

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

npm uninstall vite-jsconfig

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

3 flagged

0.3.20.3.30.3.4

Indicators of compromise (SHA-256)

f03bb7808458e6fe8226e85f4870698a47c60f6b846bd9f95283b27800b215ce

36504ee9e0d14e1f5980982d2cd08e28bdba9fe0d3e2037b7b855fa5b27f95f7

91489dacd93bd83b44c18ddbc4f5a00240d7d3595cf7298f0884fd9c2a3cce48

286d71ca0b6b275bce9ed6c18f2a7d1c5c5ee3ce830fe6f9d2a35f97857b2bfb

d4048464355d44b57966d70cb2f09c08bc925dcd777d654d84d51cff3968f670

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-jsconfig (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-jsconfig across your stack and pipelines.
If you installed it — respond
Remove vite-jsconfig 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-jsconfig 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-jsconfig 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-jsconfig on npm has been identified as a malicious package (versions 0.3.2, 0.3.3, 0.3.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rr36-42fh-3rq5RLMA-2025-05190RLUA-2025-05551RLUA-2025-05984

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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