Critical Malicious Code Vulnerability in sysverify Package

sysverify Updated 23 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16404: Malicious code in sysverify (npm). Affects sysverify versions 1.0.9 – 2.0.9. 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

The sysverify package is a Node.js library designed for system verification tasks, allowing developers to validate system configurations and ensure compliance with specified standards. However, it has been found to contain malicious code, posing significant security risks to users and their systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the sysverify package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of the code has been confirmed through multiple sources, indicating that systems running this package should be considered fully compromised. Immediate action is required to mitigate potential damage.

How To Fix

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

npm uninstall sysverify

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 measure, users can isolate the affected systems from the network to prevent further compromise while they assess the situation. Additionally, it is advisable to rotate all secrets and keys stored on the compromised system from a secure, unaffected environment.

Conclusion

The sysverify package has been identified as containing malicious code, posing serious security threats to users. Immediate removal of the package and rotation of sensitive information is crucial. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for sysverify →

Share this vulnerability

FAQ

The sysverify package is a Node.js library used for verifying system configurations and ensuring compliance with standards.

If you have the sysverify package installed, your system may be compromised. Use tools like Vulert to check for vulnerabilities in your application.

Immediately remove the sysverify package from your system and rotate any sensitive information stored on it.

Currently, there is no patch available. Users are advised to remove the package until a secure version is released.

Vulert monitors open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts without requiring code access.

How To Fix

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

npm uninstall sysverify

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