Summary
Togoder Security scanned the npm package @img/sharp-wasm32@0.35.5 on Oct 6, 2026. An AI review of 1 source file 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
Native binary loading
NPS-513BC60AA08C
The module directly requires a prebuilt native binary ('./lib/sharp-wasm32-0.35.5.node') without any validation, checksum verification, or integrity check. While this is a common pattern for native addons, loading an opaque binary means the actual executed code is not auditable from the JavaScript source. If the .node file were tampered with or fetched from an untrusted source, it could contain arbitrary native code (exfiltration, backdoors, etc.) that bypasses JavaScript-level analysis. The version-suffixed filename (sharp-wasm32-0.35.5.node) is also unusual: 'sharp' is a known image-processing library, but this is a WASM-targeted .node binary rather than the typical platform-specific native addon, which is inconsistent with normal sharp packaging.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.cjs | medium | The file only re-exports a prebuilt native .node binary, which is unauditable at the JS level and warrants verification of the binary's origin and integrity. |
Scanned versions of @img/sharp-wasm32
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.35.5 | Needs review | 1 | Oct 6, 2026 |
Frequently asked questions
Is @img/sharp-wasm32 safe to use?
No confirmed malware was found in @img/sharp-wasm32@0.35.5, but the review flagged 1 medium severity finding for risky patterns worth checking before you rely on it.
Does @img/sharp-wasm32 contain malware?
No malware was identified in @img/sharp-wasm32@0.35.5 when Togoder Security scanned it on Oct 6, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @img/sharp-wasm32 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 @img/sharp-wasm32 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 @img/sharp-wasm32@0.35.5, cost nothing.