Critical Malicious Code Vulnerability in node-gyp-runtime Package

node-gyp-runtime Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17684: Malicious code in node-gyp-runtime (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

node-gyp-runtime is an npm package that facilitates the building of native add-ons for Node.js. It is widely used in various applications that require native bindings. However, this package has been compromised, leading to severe security risks for any system that has it installed. The malicious code embedded in this package can potentially grant unauthorized access to sensitive data and system controls.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the node-gyp-runtime package, identified as GHSA-v64f-f8pp-4qx2. This code can fully compromise any computer running the package, allowing attackers to access secrets and keys stored on the system. The implications of this vulnerability are severe, as it can lead to data breaches and unauthorized control over the affected systems. Users are advised to treat any system with this package installed as compromised.

How To Fix

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

npm uninstall node-gyp-runtime

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 and securing your system. Ensure that all sensitive information is rotated and that the system is monitored for any unusual activity.

Conclusion

The node-gyp-runtime package has been compromised with malicious code, posing a significant risk to any system that has it installed. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for node-gyp-runtime →

Share this vulnerability

FAQ

Immediately remove the node-gyp-runtime package and rotate all secrets and keys stored on the affected system.

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

Failing to address this vulnerability can lead to unauthorized access to sensitive data, data breaches, and potential control over your system by malicious actors.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure that you only install packages from trusted sources.

If immediate removal is not possible, ensure that you secure your system and monitor for any suspicious activity until you can remove the package.

How To Fix

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

npm uninstall node-gyp-runtime

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