Critical Malicious Code Execution Vulnerability in runhelper Package
Summary
MAL-2026-17332: Malicious code in runhelper (npm). Affects runhelper versions 1.0.0. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The runhelper package is an npm module designed to facilitate the execution of shell commands within Node.js applications. It is often used for its ability to spawn child processes and manage command execution. However, this package has been found to contain a severe vulnerability that allows for the execution of malicious code, posing significant risks to applications that rely on it.
Vulnerability Detail
The vulnerability originates from the runhelper package's dependency on imgbundle, which stages a malicious payload file at a disguised location. When runhelper is required, it unconditionally loads this payload, allocates executable memory, and executes the code without any user consent or visibility. This behavior is facilitated through the use of the kernel32 API, which allows the execution of arbitrary code in the context of the application. The implications of this vulnerability are severe, as it can lead to unauthorized access, data breaches, and system compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall runhelperIf 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, you can remove the runhelper package from your project and replace its functionality with alternative packages that do not have known vulnerabilities. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.
Conclusion
The runhelper package contains a critical vulnerability that allows for the execution of malicious code, posing significant risks to applications. It is essential to update the package to a patched version or implement workarounds to mitigate the risks associated with this vulnerability.
See every vulnerability recorded for runhelper →
FAQ
The vulnerability allows for the execution of malicious code through a payload loaded from a disguised file, compromising the security of applications using the package.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The risks include unauthorized code execution, potential data breaches, and the possibility of system compromise, which can lead to severe consequences for affected applications.
You should check the package repository for any updates or patches that address this vulnerability. If available, updating the package is crucial.
If an immediate update is not possible, consider removing the runhelper package and using alternative solutions while monitoring your dependencies for vulnerabilities.
