Critical Malicious Code Vulnerability in Pergel Package

pergel Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191138: Malicious code in pergel (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

Pergel is an npm package designed for [insert functionality here, e.g., web development, data processing]. It offers features such as [insert key attributes, e.g., modular architecture, ease of use]. However, it has been identified as containing malicious code, posing a significant risk to systems that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the Pergel package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications are severe, as it may lead to full control of the compromised system by an external entity. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall pergel

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you monitor your systems for any signs of compromise after removal.

Conclusion

The discovery of malicious code in the Pergel npm package poses a serious threat to users. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for pergel →

Share this vulnerability

FAQ

Immediately uninstall the Pergel package using 'npm uninstall pergel' and rotate any sensitive information stored on the affected system.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to remove Pergel can lead to unauthorized access to your system, potentially compromising sensitive data and allowing attackers to take control of your machine.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to issues in real-time without requiring access to your code.

Yes, but ensure that you regularly check for vulnerabilities in all your dependencies and keep them updated to minimize risks.

How To Fix

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

npm uninstall pergel

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