Critical Malicious Code Vulnerability in @pergel/module-graphql Package

@pergel/module-graphql Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191286: Malicious code in @pergel/module-graphql (npm). Affects @pergel/module-graphql versions 0.6.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 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 @pergel/module-graphql package is an npm library designed for implementing GraphQL functionalities in applications. It provides developers with tools to create efficient and flexible APIs. However, this package has been compromised, making it susceptible to severe security threats that can affect users' data and system integrity.

Vulnerability Detail

The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from users and publish them to GitHub. It can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, the worm has the potential to destroy the user's home directory, leading to significant data loss and security breaches.

How To Fix

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

npm uninstall @pergel/module-graphql

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, it is advisable to remove the @pergel/module-graphql package from your project until a secure version is released. You can do this by running the following command: npm uninstall @pergel/module-graphql.

Conclusion

The @pergel/module-graphql package has been compromised by a malicious worm that poses significant security risks. Users are advised to uninstall the package and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time, ensuring better security practices.

See every vulnerability recorded for @pergel/module-graphql →

Share this vulnerability

FAQ

The vulnerability involves a malicious code injection that can steal sensitive information and potentially destroy user data.

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

If you have installed the @pergel/module-graphql package, it is recommended to uninstall it immediately and monitor for updates regarding a secure version.

Yes, the worm can propagate itself to other npm packages owned by the user, increasing the risk of widespread compromise.

Regularly updating packages, using tools like Vulert for monitoring vulnerabilities, and conducting security audits can help prevent such issues.

How To Fix

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

npm uninstall @pergel/module-graphql

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