Critical Malicious Code Vulnerability in varshade Package

varshade Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6667: Malicious code in varshade (npm). Affects varshade versions 4.5.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The varshade package is a Node.js library used for various functionalities in web applications, including data manipulation and processing. It is popular among developers for its ease of use and flexibility. However, a recent vulnerability has been identified that allows malicious code execution, posing a significant risk to applications utilizing this package.

Vulnerability Detail

The vulnerability, identified as MAL-2025-6667, originates from a malicious code injection in version 4.5.0 of the varshade package. This malicious code can lead to unauthorized access, data breaches, and potential system compromise. The issue was discovered by ReversingLabs and is documented in their malicious packages database. The technical implications include the possibility of remote code execution, which can severely impact the integrity and security of affected systems.

How To Fix

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

npm uninstall varshade

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, you can remove the varshade package from your project until a secure version is confirmed. To uninstall the package, use the command: npm uninstall varshade. This will prevent any potential exploitation of the vulnerability while you assess the situation.

Conclusion

The varshade package has a critical vulnerability that allows for malicious code execution, posing significant risks to applications. It is crucial to update to the latest version or uninstall the package until a secure version is confirmed. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for varshade →

Share this vulnerability

FAQ

varshade is a Node.js library used for data manipulation and processing in web applications.

This vulnerability involves malicious code injection that can lead to unauthorized access and system compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

As a temporary measure, consider uninstalling the varshade package to prevent exploitation until a secure version is available.

The vulnerability was discovered by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

How To Fix

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

npm uninstall varshade

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