Which versions of vite-smart-chunk are malicious?

The following npm versions of vite-smart-chunk are flagged malicious: 2.0.7, 2.0.8, 2.0.9. Treat any of these as compromised.

How do I remediate vite-smart-chunk if I installed it?

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

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

Yes — vite-smart-chunk is associated with the GHSA-3wpx-jqpg-m9h3, RLMA-2025-05997, RLUA-2025-06534 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-smart-chunk 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-smart-chunk (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-smart-chunk across your stack and pipelines.

Malicious package

vite-smart-chunknpm

vite-smart-chunk is a confirmed malicious npm package (MAL-2025-49372) that executes malicious code on install (malicious versions 2.0.7, 2.0.8, 2.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-smart-chunk (npm)

MAL-2025-49372

Immediate action

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

npm uninstall vite-smart-chunk

What this malware does

The package vite-smart-chunk was found to contain malicious code.

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

2.0.72.0.82.0.9

Indicators of compromise (SHA-256)

87ee583206ce0948a7c052ee600515c370f53dffe893e50730ff8ad8f353e279

03c305ef00e7f688f3c3a3f647f19aa629de8f81c0f2d9a2d96ac673edfca0f1

14f198f01d92dd590e6552294037d9dc7f44e5f19ca986accc0d148384135570

a77d916a006e0c8a5efc13099286aa42f7df2f2890f708ed3bf2eab128f9b2e3

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-smart-chunk (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-smart-chunk across your stack and pipelines.
If you installed it — respond
Remove vite-smart-chunk 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-smart-chunk 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-smart-chunk 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-smart-chunk on npm has been identified as a malicious package (versions 2.0.7, 2.0.8, 2.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3wpx-jqpg-m9h3RLMA-2025-05997RLUA-2025-06534

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vite-smart-chunk-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