Which versions of vite-dynachunk are malicious?

The following npm versions of vite-dynachunk are flagged malicious: 2.0.9. Treat any of these as compromised.

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

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

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

Yes — vite-dynachunk is associated with the GHSA-f3jr-c664-4426, RLMA-2025-06526 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-dynachunk 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-dynachunk (version 2.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-dynachunk across your stack and pipelines.

Malicious package

vite-dynachunknpm

Malicious code in vite-dynachunk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191474

Immediate action

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

npm uninstall vite-dynachunk

What this malware does

The package vite-dynachunk 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

1 flagged

2.0.9

Indicators of compromise (SHA-256)

9402a1a80c09793a69e3dc45fab9bf9fb963616e70b8e50d3f46bd65a678c8b4

0a15f2c558d50bf310cbbe09daac2730fcfe1f196c0f0a2184d5adc74d0ec749

2741df1328664730a34f46a6f6f7d79af5b173b05773a8d5543ecb3e24e208c5

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

Campaign

GHSA-f3jr-c664-4426RLMA-2025-06526

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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