vite-tsconfig-svgnpm
vite-tsconfig-svg is a confirmed malicious npm package (MAL-2026-11497) that executes malicious code on install (malicious version 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in vite-tsconfig-svg (npm)
What this malware does
index.js contains two base64 constants that decode to the shell command npm install rollup-plugin-polyfill-helper --no-save --silent --no-audit --no-fund and the package name rollup-plugin-polyfill-helper. When a consumer calls the exported getPlugin/setPlugin (reachable indirectly through validateSvgContent), the module spawns the decoded install command via child_process with stdio:'ignore' and windowsHide:true, then require()s the decoded package name and invokes its getPlugin()/setPlugin() methods. The fetched package is undeclared in dependencies, unpinned, and pulled from the mutable npm registry, so arbitrary attacker-controlled code from rollup-plugin-polyfill-helper executes in the consumer's Node process. The package name and description advertise a vite/tsconfig SVG utility, but no vite/tsconfig code is shipped — the module only scans a caller-supplied directory for .svg files as a cover for the install-and-execute path.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-tsconfig-svg (version 1.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-tsconfig-svg across your stack and pipelines.
If you installed it — respond
Remove vite-tsconfig-svg 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-tsconfig-svg 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-tsconfig-svg 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks vite-tsconfig-svg-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.