Summary
Togoder Security scanned the npm package qs@6.14.0 on Oct 4, 2026. An AI review of 6 source files produced 1 medium severity finding. The overall verdict is medium: the findings flag risky but common patterns (dynamic code, unsafe defaults, broad file or network access) rather than confirmed malware.
Findings 1
Prototype pollution
NPS-AB498894CF85
The merge function recursively merges source object properties into a target object. When options.plainObjects or options.allowPrototypes is not used, __proto__, constructor, or prototype keys passed in source may be merged into target and potentially alter Object.prototype behavior in consuming applications. This is a known security-sensitive pattern in qs/querystring-like utility code.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| lib/utils.js | medium | No obvious malicious behavior, but the merge utility has prototype pollution risk that should be assessed in the context of how callers sanitize input. |
| dist/qs.js | safe | No malicious patterns detected; the code is a legitimate bundled copy of the qs library with no exfiltration, credential harvesting, obfuscated payloads, or suspicious behavior. |
| lib/formats.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/index.js | safe | Cleared by Jev triage; no further analysis needed |
| lib/parse.js | safe | No malicious patterns detected; this is the standard qs query string parser implementation. |
| lib/stringify.js | safe | Cleared by Jev triage; no further analysis needed |
Affected version ranges
None of the 3 scanned versions of qs are flagged high or critical. The latest scanned version, 6.16.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 6.16.0 | No issues | 1 | 6.16.0 | |
| 6.14.0 | Needs review | 1 | 6.14.0 | Prototype pollution |
| 6.13.0 | Not scanned | 1 | 6.13.0 | |
| 6.11.0 | No issues | 1 | 6.11.0 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of qs
Frequently asked questions
Is qs safe to use?
No confirmed malware was found in qs@6.14.0, but the review flagged 1 medium severity finding for risky patterns worth checking before you rely on it.
Does qs contain malware?
No malware was identified in qs@6.14.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was qs checked?
Togoder Security downloaded the published npm package and had an AI model read its 6 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan qs together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in qs@6.14.0, cost nothing.