Malicious Code Detected in com.unity.shadergraph - Security Alert

com.unity.shadergraph Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17363: Malicious code in com.unity.shadergraph (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package com.unity.shadergraph is a widely used library in the npm ecosystem, primarily utilized for creating and managing shaders in Unity applications. It offers developers tools to enhance graphics rendering and visual effects. However, recent findings have uncovered a serious security vulnerability within this package, exposing users to potential risks.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the com.unity.shadergraph package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that utilize this package. The issue was introduced in version 0 and has been identified as a significant threat to developers and users alike.

How To Fix

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

npm uninstall com.unity.shadergraph

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 a temporary workaround, consider removing the com.unity.shadergraph package from your project until a secure version is released. You can do this using the command: npm uninstall com.unity.shadergraph.

Conclusion

The discovery of malicious code in the com.unity.shadergraph package poses a significant threat to developers and users. Immediate action is required to mitigate risks, including updating or removing the package. Stay informed about updates and utilize tools like Vulert for ongoing monitoring.

See every vulnerability recorded for com.unity.shadergraph →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or lead to other harmful actions within applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

Currently, the vulnerability affects all versions starting from 0. It is essential to monitor the official repository for updates on a secure version.

Ignoring this vulnerability could lead to severe security breaches, data loss, or unauthorized access to your applications and user data.

How To Fix

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

npm uninstall com.unity.shadergraph

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