Malicious Code Detected in cli-plugin-ngrok: A Security Alert

cli-plugin-ngrok Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17114: Malicious code in cli-plugin-ngrok (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 cli-plugin-ngrok package is a plugin for the ngrok service, which allows developers to expose local servers to the internet securely. It is commonly used for testing and development purposes. However, this package has been found to contain malicious code, posing a significant security risk to users who rely on it for their development workflows.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the cli-plugin-ngrok package. This code can potentially compromise user systems, leading to unauthorized access, data breaches, or other malicious activities. The presence of such code raises serious concerns about the integrity and security of the package, making it imperative for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall cli-plugin-ngrok

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, users should avoid using the cli-plugin-ngrok package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the cli-plugin-ngrok package poses a serious threat to users. Immediate action is required to mitigate potential risks, including updating to a patched version when available and considering alternative solutions in the meantime.

See every vulnerability recorded for cli-plugin-ngrok →

Share this vulnerability

FAQ

cli-plugin-ngrok is a plugin for the ngrok service that allows developers to expose local servers to the internet securely.

The malicious code can compromise user systems, potentially leading to unauthorized access and data breaches.

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

Currently, there is no patched version available. Users should monitor the official repository for updates.

If you have installed cli-plugin-ngrok, it is recommended to uninstall the package and refrain from using it 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 cli-plugin-ngrok

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