Critical Malicious Code Vulnerability in shell-exec Package

shell-exec Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191424: Malicious code in shell-exec (npm). Affects shell-exec versions 1.1.3 – 1.1.4. 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 shell-exec package is a Node.js library that allows users to execute shell commands from within JavaScript code. It is commonly used in various applications for automating tasks and managing system processes. However, this package has been compromised, introducing a severe vulnerability that can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm steals tokens and credentials, publishing them to GitHub, and propagates itself to NPM packages owned by the user. It also establishes persistence through GitHub actions and may even destroy the user's home directory. Any system with the compromised package installed is considered fully compromised, necessitating immediate action.

How To Fix

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

npm uninstall shell-exec

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 compromised package and ensuring that your system is secure. It is recommended to monitor your system for any unauthorized access or changes.

Conclusion

The shell-exec package has been compromised by a malicious worm, posing serious risks to any system using it. Immediate removal of the package and rotation of sensitive credentials are essential steps to mitigate the impact of this vulnerability. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for shell-exec →

Share this vulnerability

FAQ

You should immediately uninstall the shell-exec package and rotate any credentials or tokens that may have been compromised.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to your system, potential data loss, and the compromise of sensitive information.

Currently, there are no patched versions available for the compromised shell-exec package. The best course of action is to remove it entirely.

The worm propagates by infecting NPM packages owned by the user and establishing persistence through GitHub actions, making it a significant threat.

How To Fix

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

npm uninstall shell-exec

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