Critical Malicious Code Vulnerability in @shije/new-qs Package
Summary
MAL-2026-528: Malicious code in @shije/new-qs (npm). Affects @shije/new-qs versions 1.0.0 – 1.0.1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @shije/new-qs package is a Node.js library available via npm, designed to facilitate query string manipulation. It is commonly used in web applications to parse and stringify query strings. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @shije/new-qs package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that any computer running this package is at risk of being fully compromised, potentially leading to data breaches and loss of control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @shije/new-qsIf 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 and ensuring that all sensitive information is secured and rotated.
Conclusion
The @shije/new-qs package contains malicious code that poses a severe security risk to any system using it. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @shije/new-qs →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.
Failure to address this vulnerability can lead to unauthorized access, data breaches, and loss of control over your systems.
While the npm ecosystem is generally reliable, it is essential to remain vigilant and utilize tools like Vulert to monitor for vulnerabilities.
