Malicious Code Detected in vercel-internal Package - MAL-2025-6322

vercel-internal Updated 02 Oct 2025

Summary

24/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6322: Malicious code in vercel-internal (npm). Affects vercel-internal versions >= 10.0.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 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 vercel-internal package is a component used within the npm ecosystem, primarily designed for internal operations related to Vercel deployments. It facilitates various functionalities that enhance the development and deployment processes. However, this package has been identified as having a vulnerability that allows it to communicate with a domain associated with malicious activity, posing a risk to users and their applications.

Vulnerability Detail

The vulnerability in the vercel-internal package originates from version 10.0.1, where it has been found to communicate with a domain linked to malicious activities. This could lead to unauthorized data access, potential data breaches, or the execution of harmful code within applications that utilize this package. The implications of this vulnerability are severe, as it compromises the integrity and security of the applications relying on vercel-internal.

How To Fix

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

npm uninstall vercel-internal

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 measure, you can remove the vercel-internal package from your project until a secure version is available. This can be done using the command: 'npm uninstall vercel-internal'. Alternatively, consider using a different package that provides similar functionality without the associated risks.

Conclusion

The vercel-internal package has a significant vulnerability that allows communication with a malicious domain, posing risks to applications. Users are advised to update the package to a secure version or consider alternative solutions to mitigate potential threats.

See every vulnerability recorded for vercel-internal →

Share this vulnerability

FAQ

The vercel-internal package is an npm package used for internal operations related to Vercel deployments, enhancing development and deployment processes.

The vulnerability allows the package to communicate with a domain associated with malicious activity, potentially leading to data breaches or unauthorized access.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring access to the code.

Yes, updating the vercel-internal package to a patched version will resolve the vulnerability. Use 'npm update vercel-internal' to update.

As a workaround, consider uninstalling the vercel-internal package or using an alternative package until a secure version is released.

How To Fix

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

npm uninstall vercel-internal

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