Which versions of vite-svg-config are malicious?

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

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

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

If vite-svg-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is vite-svg-config part of a known attack campaign?

Yes — vite-svg-config is associated with the IN-MAL-2026-018172 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-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vite-svg-config (version 1.1.0).

Malicious package

vite-svg-confignpm

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

Malicious code in vite-svg-config (npm)

MAL-2026-14140

Immediate action

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

npm uninstall vite-svg-config

What this malware does

The package's exported getPlugin/setPlugin functions decode two base64 constants (svgValidateKey, svgValidatePattern) at runtime. svgValidateKey decodes to the shell command npm install node-internal-svg-loader --no-save --silent --no-audit --no-fund, which is spawned with stdio:'ignore', windowsHide:true, and shell:true on Windows. svgValidatePattern decodes to the package name node-internal-svg-loader, which is then dynamically required and whose getPlugin() export is invoked. The command and target package name are both hidden behind base64 constants and misleading identifiers framed as SVG validation. Silencing flags (--silent, --no-audit, --no-fund, windowsHide) suppress user-visible output of the install. The result is that any consumer calling the package's advertised plugin API pulls and executes a separate npm package, whose contents are controlled by whoever owns that name, on the caller's machine.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

38e61dd39d0c1d39a3b80b7138582b334480c2fb89e990a2b64e6c59050a998f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vite-svg-config (version 1.1.0).
If you installed it — respond
Remove vite-svg-config 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-config was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. vite-svg-config on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018172

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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