Critical Malicious Code Vulnerability in system-driver Package

system-driver Updated 08 Oct 2026

Summary

08/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17685: Malicious code in system-driver (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The system-driver package is an npm module that provides a way to interact with system-level drivers in a Node.js environment. It is commonly used for applications that require direct communication with hardware or system resources. However, this package has been identified as containing malicious code, which poses a significant security risk to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the system-driver package. This code can compromise the entire system, allowing unauthorized access to sensitive information, including secrets and keys stored on the affected machine. The malicious nature of this code is classified under CWE-506, indicating that it embeds harmful functionalities that can lead to severe security breaches.

How To Fix

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

npm uninstall system-driver

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 due to the nature of the malicious code. The only recommended action is to uninstall the package and secure your system.

Conclusion

The system-driver package has been identified as containing malicious code that compromises the security of any system it is installed on. Immediate action is required to uninstall the package and secure sensitive information. Utilizing tools like Vulert can help prevent future vulnerabilities by providing real-time alerts.

See every vulnerability recorded for system-driver →

Share this vulnerability

FAQ

You should uninstall the system-driver package immediately and rotate any sensitive information stored on the affected system.

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

Keeping the system-driver package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

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

CWE-506 indicates that the product contains embedded malicious code, which is a serious security concern as it can lead to complete system compromise.

How To Fix

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

npm uninstall system-driver

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