Malicious Code Vulnerability in @ks-cqc/h5-sig4 Package

@ks-cqc/h5-sig4 Updated 24 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16524: Malicious code in @ks-cqc/h5-sig4 (npm). Affects @ks-cqc/h5-sig4 versions 2.99.99. 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 @ks-cqc/h5-sig4 package is an npm library designed for handling digital signatures in web applications. It provides functionalities that allow developers to integrate signature verification and management into their projects. However, this package has been identified as containing malicious code, which poses a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the @ks-cqc/h5-sig4 package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data or enable other malicious activities within the affected systems. The origin of this vulnerability is linked to the package's version 2.99.99, which has been flagged by security researchers for its harmful behavior.

How To Fix

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

npm uninstall @ks-cqc/h5-sig4

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

If immediate updating is not possible, consider removing the @ks-cqc/h5-sig4 package from your project until a fix is applied. You can do this by running the command: npm uninstall @ks-cqc/h5-sig4.

Conclusion

The @ks-cqc/h5-sig4 package has been compromised with malicious code, posing a serious threat to applications that utilize it. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for @ks-cqc/h5-sig4 →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive information or enable other harmful actions within the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

As a temporary measure, you should uninstall the @ks-cqc/h5-sig4 package from your project until a secure version is available.

The vulnerability was identified by security researchers who monitor malicious packages in the npm ecosystem, specifically through the efforts of ReversingLabs.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to their latest secure versions.

How To Fix

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

npm uninstall @ks-cqc/h5-sig4

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