Which versions of vite-manual-chunker are malicious?

The following npm versions of vite-manual-chunker are flagged malicious: 2.0.6. Treat any of these as compromised.

How do I remediate vite-manual-chunker if I installed it?

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

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

Yes — vite-manual-chunker is associated with the GHSA-6hf6-f4cx-42mr, RLMA-2025-05986, RLUA-2025-06528 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-manual-chunker 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-manual-chunker (version 2.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-manual-chunker across your stack and pipelines.

Malicious package

vite-manual-chunkernpm

vite-manual-chunker is a confirmed malicious npm package (MAL-2025-48914) that executes malicious code on install (malicious version 2.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-manual-chunker (npm)

MAL-2025-48914

Immediate action

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

npm uninstall vite-manual-chunker

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

1 flagged

2.0.6

Indicators of compromise (SHA-256)

2466db729b423d58b084a5f99834cfaf8c62af4179350ef30978e32f36b50fa7

c9fe174ff99e491c925603cdbaa9b010da8c86a73fe303e64de65b0da16fc277

81f0f703d47a14a01038494746e3280d4398a85658fc361c8d359326958a6b30

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

Campaign

GHSA-6hf6-f4cx-42mrRLMA-2025-05986RLUA-2025-06528

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks vite-manual-chunker-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