Summary
Togoder Security scanned the npm package string_decoder@1.1.1 on Oct 4, 2026. An AI review of 1 source file produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| lib/string_decoder.js | safe | No malicious patterns detected; this is the standard Node.js string_decoder module with only a dependency on safe-buffer for buffer allocation. |
Affected version ranges
None of the 2 scanned versions of string_decoder are flagged high or critical. The latest scanned version, 1.3.0, is clean. Only versions we have scanned are listed; unscanned versions between them are not covered.
| Versions | Verdict | Count | Range | Top findings |
|---|---|---|---|---|
| 1.1.1 – 1.3.0 | No issues | 2 | >=1.1.1 <=1.3.0 | |
| 0.10.31 | Not scanned | 1 | 0.10.31 |
Full list, including published versions not scanned yet: version ranges API.
Scanned versions of string_decoder
Frequently asked questions
Is string_decoder safe to use?
Our AI source review of string_decoder@1.1.1 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does string_decoder contain malware?
No malware was identified in string_decoder@1.1.1 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 string_decoder checked?
Togoder Security downloaded the published npm package and had an AI model read its 1 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 string_decoder 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 string_decoder@1.1.1, cost nothing.