Malicious Code Vulnerability in libjs-cqs Package

libjs-cqs Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1770: Malicious code in libjs-cqs (npm). Affects libjs-cqs versions 90.9.0. 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

libjs-cqs is a JavaScript library available through npm, designed to facilitate certain functionalities in web applications. It is widely used due to its ease of integration and lightweight nature. However, like many open-source packages, it can be susceptible to vulnerabilities, particularly when malicious code is introduced into its ecosystem.

Vulnerability Detail

The vulnerability identified as MAL-2026-1770 involves the presence of malicious code within the libjs-cqs package. This issue originated from a compromised version of the package (version 90.9.0), which was reported by ReversingLabs. The malicious code can lead to unauthorized access or manipulation of the application using this package, potentially compromising sensitive data and application integrity.

How To Fix

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

npm uninstall libjs-cqs

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 workaround, you may consider removing the libjs-cqs package from your project until a secure version is available. You can do this by running: npm uninstall libjs-cqs. Alternatively, you can replace it with a different library that offers similar functionality without the associated risks.

Conclusion

The libjs-cqs package has been identified with a serious vulnerability due to malicious code. It is crucial for developers using this package to take immediate action by updating or removing it to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for libjs-cqs →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to application data and may manipulate the application's behavior.

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

Yes, it is advisable to update to a patched version of the libjs-cqs package as soon as it is available.

Consider removing the libjs-cqs package or replacing it with an alternative library until a secure version is released.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

How To Fix

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

npm uninstall libjs-cqs

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