Critical Malicious Code Vulnerability in qq-console Package

qq-console Updated 06 Mar 2026

Summary

06/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1271: Malicious code in qq-console (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

The qq-console package is a Node.js library used for various console-related functionalities in applications. It is often utilized by developers to enhance the user interface and experience in command-line applications. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the qq-console package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The malicious nature of this code poses significant risks, as it may not only affect the immediate application but also the entire system, potentially leading to data breaches and loss of control over the environment.

How To Fix

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

npm uninstall qq-console

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 entirely. Ensure to monitor your system for any unusual activity following the removal.

Conclusion

The qq-console package has been identified as containing malicious code that poses a significant security risk. Immediate removal of the package and rotation of any sensitive information is necessary to mitigate the threat. Utilizing tools like Vulert can help monitor and alert for future vulnerabilities.

See every vulnerability recorded for qq-console →

Share this vulnerability

FAQ

You should remove the qq-console package immediately and rotate any secrets or keys stored on the affected machine.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to remove the package may result in unauthorized access to your system, leading to potential data breaches and loss of sensitive information.

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

While many npm packages are safe, it's essential to review their code and monitor for vulnerabilities regularly to ensure security.

How To Fix

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

npm uninstall qq-console

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