Which versions of vite-svg-parse are malicious?

The following npm versions of vite-svg-parse are flagged malicious: 1.1.3. Treat any of these as compromised.

How do I remediate vite-svg-parse if I installed it?

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

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

Yes — vite-svg-parse is associated with the IN-MAL-2026-016773 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-svg-parse 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-svg-parse (version 1.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-svg-parse across your stack and pipelines.

Malicious package

vite-svg-parsenpm

vite-svg-parse is a confirmed malicious npm package (MAL-2026-13464) that executes malicious code on install (malicious version 1.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-svg-parse (npm)

MAL-2026-13464

Immediate action

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

npm uninstall vite-svg-parse

What this malware does

The package's exported API (getPlugin/setPlugin) decodes two base64 string literals at runtime: the first decodes to npm install node-internal-svg-loader --no-save --silent --no-audit --no-fund, which is passed to child_process.spawn; the second decodes to the module name node-internal-svg-loader, which is then require()'d and whose getPlugin()/setPlugin() are invoked. The fetched package is not declared in package.json dependencies, and both the shell command and the require target are concealed in base64 to evade static inspection. Any consumer that imports this library and calls its documented API causes an undeclared, hidden third-party npm package to be installed and its code executed in the installer's Node.js process.

Malicious versions

1 flagged

1.1.3

Indicators of compromise (SHA-256)

5f6b581f4ab8d027c727649fae10749a9ac9a59af4619f5576362ab9243cb6c6

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

Campaign

IN-MAL-2026-016773

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vite-svg-parse-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