Which versions of node-internal-svg-loader are malicious?

The following npm versions of node-internal-svg-loader are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate node-internal-svg-loader if I installed it?

node-internal-svg-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed node-internal-svg-loader — how do I know if it already compromised me?

If node-internal-svg-loader 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 node-internal-svg-loader part of a known attack campaign?

Yes — node-internal-svg-loader is associated with the GHSA-9rgf-6m2p-q73f, IN-MAL-2026-017427, IN-MAL-2026-017510 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 node-internal-svg-loader 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 node-internal-svg-loader (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-internal-svg-loader across your stack and pipelines.

Malicious package

node-internal-svg-loadernpm

node-internal-svg-loader is a confirmed malicious npm package (MAL-2026-13766) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-internal-svg-loader (npm)

MAL-2026-13766

Immediate action

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

npm uninstall node-internal-svg-loader

What this malware does

Package advertises itself as an SVG loader using well-known CDN providers, but exported functions getPlugin, setPlugin, and getPluginExten build a request to https://rest-icon-handler.store/icons/<token> and pass the response body directly to eval(JSON.parse(body)). The destination host is not one of the CDNs the README references (Cloudflare/Fastly/Akamai/CloudFront/KeyCDN/Gcore), is not caller-configurable, and is assembled from separate protocol/subdomain/domain/path constants rather than a literal string. A benign-looking setDefaultModule that talks to cdnjs sits alongside the eval path as cover. Any consumer invoking these APIs executes arbitrary JavaScript returned by whoever controls rest-icon-handler.store, on the consumer's Node.js process with full ambient credentials and filesystem access.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

6c3711f6de8ebdff01d531213eb77e942dcf6f34c7b5468b9da67fa12b893b3d

ea179fb3670844db867458418a68b3eb69dfd983ebe1fe96b2a4b41601266fc4

590b09ed2b0a02c3b98af19f3845e01ac205d214afa5a8c06bb0128e55442847

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-internal-svg-loader (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-internal-svg-loader across your stack and pipelines.
If you installed it — respond
node-internal-svg-loader is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If node-internal-svg-loader 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 node-internal-svg-loader 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. node-internal-svg-loader on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9rgf-6m2p-q73fIN-MAL-2026-017427IN-MAL-2026-017510

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-internal-svg-loader-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database