Summary
Togoder Security scanned the npm package debug@4.3.4 on Oct 4, 2026. An AI review of 4 source files produced 1 low severity finding. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings 1
Dynamic regular expression construction
NPS-BBFC6DC26FCA
The enable() function constructs RegExp objects from user-controlled namespace strings without escaping. This could theoretically lead to ReDoS if a malicious namespace is provided, but in the context of the debug package this is expected behavior and not a security vulnerability in itself.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| src/browser.js | safe | No malicious patterns detected; this is the legitimate browser implementation of the debug logging library with only expected browser APIs and a JSON.stringify formatter. |
| src/common.js | safe | This is the legitimate source code for the popular 'debug' npm package; no malicious patterns such as data exfiltration, credential harvesting, obfuscation, or backdoors were detected. |
| src/index.js | safe | No malicious patterns detected |
| src/node.js | safe | This is the standard Node.js implementation of the debug package with no malicious patterns detected. |
Affected version ranges
None of the 5 scanned versions of debug are flagged high or critical. The latest scanned version, 4.4.3, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 4.4.3 | No issues | 1 | 4.4.3 | |
| 4.4.1 | Not scanned | 1 | 4.4.1 | |
| 4.3.7 | No issues | 1 | 4.3.7 | |
| 4.3.5 | Not scanned | 1 | 4.3.5 | |
| 3.2.7 – 4.3.4 | No issues | 2 | >=3.2.7 <=4.3.4 | |
| 2.6.9 | Needs review | 1 | 2.6.9 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of debug
Frequently asked questions
Is debug safe to use?
Our AI source review of debug@4.3.4 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does debug contain malware?
No malware was identified in debug@4.3.4 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 debug checked?
Togoder Security downloaded the published npm package and had an AI model read its 4 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 debug 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 debug@4.3.4, cost nothing.