Which versions of pixsvg are malicious?

The following npm versions of pixsvg are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate pixsvg if I installed it?

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

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

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

Malicious package

pixsvgnpm

pixsvg is a confirmed malicious npm package (MAL-2026-17313) that executes malicious code on install (malicious version 0.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pixsvg (npm)

MAL-2026-17313

Immediate action

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

npm uninstall pixsvg

What this malware does

The pixsvg module exports fetchDataFromSvg(svgData), which scans the input SVG for a comment of the form , reassembles the binary-encoded 1/0 sequence into a JavaScript string via binaryToData (parseInt(chunk,2) + String.fromCharCode), and passes the reconstructed string to eval(). The helper is exported on the package's public surface (module.exports.fetchDataFromSvg) but is not documented in the README and is unrelated to the advertised SVG image pipeline. Any consumer application that feeds externally-supplied SVG content through this exported function will execute attacker-controlled JavaScript in the host process. The binary-encoding-then-eval shape is a deliberate covert execution channel with no legitimate role in an image-processing library.

Malicious versions

1 flagged

0.2.0

Indicators of compromise (SHA-256)

23f6989954f196f485ff049ef7dc22bb800a57187e6bdc8bd0e002ed4bbc1db7

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 pixsvg (version 0.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pixsvg across your stack and pipelines.
If you installed it — respond
Remove pixsvg 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 pixsvg 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 pixsvg 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. pixsvg on npm has been identified as a malicious package (version 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020794

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pixsvg-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