Summary
Togoder Security scanned the npm package yauzl@3.4.0 on Oct 4, 2026. An AI review of 3 source files 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 |
|---|---|---|
| crc32.js | safe | Cleared by Jev triage; no further analysis needed |
| fd-slicer.js | safe | No malicious patterns detected; the code is a standard file descriptor and buffer slicing utility with no data exfiltration, credential harvesting, obfuscation, or suspicious behavior. |
| index.js | safe | No malicious patterns detected; the code is a legitimate ZIP file parsing library (yauzl) with no data exfiltration, credential harvesting, obfuscation, backdoors, or suspicious network/process activity. |
Frequently asked questions
Is yauzl safe to use?
Our AI source review of yauzl@3.4.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does yauzl contain malware?
No malware was identified in yauzl@3.4.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 yauzl 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 yauzl 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 yauzl@3.4.0, cost nothing.