Summary
Togoder Security scanned the npm package @walletconnect/logger@2.1.2 on Oct 4, 2026. An AI review of 3 source files produced 1 medium, 2 low severity findings. 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 3
Data collection and logging
NPS-92B8CDB8B698
The module implements a custom logger that collects logs in memory, including potentially sensitive context data (via context field in child loggers). The logs can be downloaded as a Blob. While not inherently malicious, this could facilitate data exfiltration if the library is used in a context where logs contain sensitive information and are automatically downloaded or transmitted.
File download / browser file generation
NPS-6EB572356ECD
The downloadLogsBlobInBrowser method creates a Blob from collected log data and programmatically triggers a download in the browser via an anchor element. While this is a common logging utility pattern, it could potentially be abused to exfiltrate sensitive data if the logs contain secrets and the download is triggered without user interaction or consent. The filename includes walletconnect-logs- and a timestamp.
Dynamic code execution / eval-like behavior
NPS-0790D900945F
The code uses JSON.parse(e) on log messages when they are strings. If log messages contain untrusted input, this could lead to parsing errors or potentially prototype pollution, though it's not direct code execution. It is a minor risk.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/index.es.js | medium | The code is a legitimate logging utility for WalletConnect, but contains patterns that could be misused for data exfiltration through log collection and browser-based download functionality; no direct malicious behavior was detected. |
| dist/index.cjs.js | safe | No malicious patterns detected; the code is a legitimate logging utility using pino and safe-json with no exfiltration, obfuscation, or dangerous operations. |
| dist/index.umd.js | safe | No malicious patterns detected; the code is a legitimate logging library with browser and server support, containing no exfiltration, credential harvesting, obfuscation, or other suspicious behavior. |
Affected version ranges
None of the 2 scanned versions of @walletconnect/logger are flagged high or critical. The latest scanned version, 3.0.2, is medium risk. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 2.1.2 – 3.0.2 | Needs review | 2 | >=2.1.2 <=3.0.2 | Data collection and logging |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of @walletconnect/logger
Frequently asked questions
Is @walletconnect/logger safe to use?
No confirmed malware was found in @walletconnect/logger@2.1.2, but the review flagged 1 medium, 2 low severity findings for risky patterns worth checking before you rely on it.
Does @walletconnect/logger contain malware?
No malware was identified in @walletconnect/logger@2.1.2 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 @walletconnect/logger checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 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 @walletconnect/logger 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 @walletconnect/logger@2.1.2, cost nothing.