Critical Malicious Code Vulnerability in svg-safety-tool Package

svg-safety-tool Updated 13 Mar 2026

Summary

12/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1364: Malicious code in svg-safety-tool (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The svg-safety-tool package is an npm library designed to enhance the safety of SVG files by sanitizing them for web applications. It is commonly used in projects that require SVG manipulation or rendering. However, this package has been compromised, leading to severe security risks for any application utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the svg-safety-tool package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a known malware source, which has been documented in the GitHub Security Advisory (GHSA-5wq3-6mmg-x8x9). The ramifications of this vulnerability are significant, as it could lead to data breaches and loss of control over affected systems.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall svg-safety-tool

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As there is no direct workaround to mitigate the effects of this vulnerability, the best course of action is to uninstall the package and ensure that your system is secure. Regularly monitor your application for any signs of compromise.

Conclusion

The svg-safety-tool package has been compromised with malicious code, posing a significant security risk to any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for svg-safety-tool →

Share this vulnerability

FAQ

svg-safety-tool is an npm package used to sanitize SVG files for safe use in web applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately uninstall the svg-safety-tool package and rotate any secrets or keys stored on the affected machine.

No, there is currently no patched version available for svg-safety-tool. The best action is to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall svg-safety-tool

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback