Which versions of react-hot-svg are malicious?

The following npm versions of react-hot-svg are flagged malicious: 1.1.4, 1.1.5. Treat any of these as compromised.

How do I remediate react-hot-svg if I installed it?

Remove react-hot-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.

I already installed react-hot-svg — how do I know if it already compromised me?

If react-hot-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.

Is react-hot-svg part of a known attack campaign?

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

Malicious package

react-hot-svgnpm

Malicious code in react-hot-svg (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10439

Immediate action

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

npm uninstall react-hot-svg

What this malware does

index.js in react-hot-svg 1.1.4 hides both a shell command and a package name as base64 strings named svgValidateKey and svgValidatePattern. When any of the exported API surface (getPlugin, setPlugin, validateSvgContent) is invoked, the code decodes svgValidateKey via atob to the string npm install rollup-plugin-polyfill-handler --no-save --silent --no-audit --no-fund, spawns it via child_process.spawn with stdio: 'ignore', and on process exit require()s the base64-decoded module name rollup-plugin-polyfill-handler and immediately invokes its .getPlugin()() function. The --no-save --silent --no-audit --no-fund flags suppress output and prevent the added dependency from appearing in package.json or the lockfile. The obfuscation of both the command and the required module name, the SVG-themed cover identifiers, and the pattern of installing-then-requiring-then-executing an undeclared external package match a dropper that lands and executes attacker-controlled code from a separate npm package on any consumer who uses this library's advertised API.

Malicious versions

2 flagged

1.1.41.1.5

Indicators of compromise (SHA-256)

7c59d0dbdaeea673db1067ec280a93ab744a5fb5f60ba8938698b46fbddcae7c

847fe0ea93982597b0611e6fd23f1b77af40b7162baf338659fbff8deb7fb051

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 react-hot-svg (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-hot-svg across your stack and pipelines.
If you installed it — respond
Remove react-hot-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 react-hot-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 react-hot-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

No. react-hot-svg on npm has been identified as a malicious package (versions 1.1.4, 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010205IN-MAL-2026-010202

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-hot-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.

Malware detection Runtime egress monitoring