Critical Malicious Code Vulnerability in with-shadcn Package

with-shadcn Updated 02 Oct 2025

Summary

04/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5739: Malicious code in with-shadcn (npm). Affects with-shadcn versions >= 55.3.1. 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 with-shadcn package is an npm library designed for building user interfaces with a focus on simplicity and flexibility. It allows developers to create components that can be easily integrated into various applications. However, this package has been identified as containing malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the with-shadcn package. This code can compromise the security of any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. The ramifications of this vulnerability are severe, as it can lead to full system compromise, data breaches, and loss of control over the affected systems.

How To Fix

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

npm uninstall with-shadcn

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

Currently, there are no specific workarounds to mitigate the risks associated with the with-shadcn package. The best course of action is to remove the package entirely and monitor your system for any signs of compromise.

Conclusion

The with-shadcn package contains malicious code that poses a significant security threat. Immediate removal of the package is essential to protect your system from potential compromise. Regular monitoring and updating of your dependencies are crucial to maintaining security.

See every vulnerability recorded for with-shadcn →

Share this vulnerability

FAQ

The with-shadcn package is an npm library used for building user interfaces, but it has been found to contain malicious code.

If you have the with-shadcn package installed, your system is likely compromised. It is recommended to remove it immediately.

Rotate all secrets and keys stored on your computer from a secure device and monitor for any unauthorized access.

As of now, there is no patch available. The only solution is to remove the package.

Vulert monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file, allowing you to stay informed about potential risks.

How To Fix

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

npm uninstall with-shadcn

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