Critical Malicious Code Vulnerability in @pergel/cli Package

@pergel/cli Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191284: Malicious code in @pergel/cli (npm). Affects @pergel/cli versions 0.11.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @pergel/cli package is a command-line interface tool designed for various utility functions in Node.js applications. It is widely used in the npm ecosystem for its ease of integration and functionality. However, it has recently been compromised, exposing users to significant security risks due to malicious code embedded within the package.

Vulnerability Detail

The vulnerability stems from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which has infected version 0.11.1 of the @pergel/cli package. This malicious payload is capable of stealing user tokens and credentials, subsequently publishing them to GitHub. Additionally, it can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The worm poses a severe threat as it may also delete the user's home directory, leading to potential data loss.

How To Fix

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

npm uninstall @pergel/cli

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, users can remove the compromised package from their project by executing the following command: npm uninstall @pergel/cli. It is advisable to avoid using the package until a secure version is confirmed.

Conclusion

The @pergel/cli package has been compromised by a malicious worm that poses serious security risks. Users are urged to take immediate action by updating or uninstalling the package to protect their systems and data. Regular monitoring of dependencies is crucial to prevent future vulnerabilities.

See every vulnerability recorded for @pergel/cli →

Share this vulnerability

FAQ

The malicious code is designed to steal user tokens and credentials, and it can also delete files from the user's home directory.

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

If you have installed version 0.11.1 of @pergel/cli, you should uninstall it immediately and check for any unauthorized access to your accounts.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

Failure to address this vulnerability can lead to unauthorized access to sensitive information, data loss, and further propagation of the malicious code to other packages.

How To Fix

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

npm uninstall @pergel/cli

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