Malicious Code Detected in cli-plugin-graphiql: A Critical Vulnerability

cli-plugin-graphiql Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17111: Malicious code in cli-plugin-graphiql (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 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 cli-plugin-graphiql package is an npm plugin designed to enhance GraphiQL, a graphical interactive in-browser GraphQL IDE. This package allows developers to easily test and explore GraphQL APIs. However, it has been found to contain malicious code, posing a significant risk to users who integrate it into their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the cli-plugin-graphiql package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall cli-plugin-graphiql

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 can remove the cli-plugin-graphiql package from their project until a secure version is released. This can be done with the command: 'npm uninstall cli-plugin-graphiql'.

Conclusion

The discovery of malicious code in the cli-plugin-graphiql package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability.

See every vulnerability recorded for cli-plugin-graphiql →

Share this vulnerability

FAQ

cli-plugin-graphiql is an npm package that enhances the functionality of GraphiQL, a tool for testing GraphQL APIs.

The malicious code was identified by security researchers from Amazon Inspector, who reported it as a vulnerability.

Using the affected package can lead to security breaches, unauthorized access to sensitive data, and potential exploitation of your application.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall cli-plugin-graphiql

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