Summary
Togoder Security scanned the npm package @img/sharp-linux-arm@0.35.5 on Oct 6, 2026. An AI review of 1 source file 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
Dynamic native module loading
NPS-DF6D13B75D15
The file loads a platform-specific native binary (sharp-linux-arm-0.35.5.node) at import time. While this is standard for the 'sharp' image processing library's prebuilt binary distribution, loading native modules carries inherent risk because the binary cannot be audited as JavaScript and executes with full process privileges.
Conditional optional dependency resolution
NPS-A2235740F0FD
The try/catch block attempts to resolve '@img/sharp-libvips-linux-arm/binary' but silently swallows any errors. This is a common pattern for optional platform-specific dependencies, but silently ignoring resolution failures can mask tampering or missing dependency issues.
Top-level code execution at import
NPS-48C84512760D
Both the require.resolve call and the native module load execute at import time (top-level code). The native binary is loaded immediately when the module is required, meaning any consumer of this package triggers binary execution without explicit opt-in.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| index.cjs | medium | This appears to be a standard platform-specific entry point for the 'sharp' image library that loads a native ARM binary at import time; no overt malicious patterns (exfiltration, shell spawning, obfuscation) are present, but native binary loading warrants moderate caution. |
Scanned versions of @img/sharp-linux-arm
| Version | Verdict | Files | Scanned |
|---|---|---|---|
| 0.35.5 | Needs review | 1 | Oct 6, 2026 |
Frequently asked questions
Is @img/sharp-linux-arm safe to use?
No confirmed malware was found in @img/sharp-linux-arm@0.35.5, but the review flagged 1 medium, 2 low severity findings for risky patterns worth checking before you rely on it.
Does @img/sharp-linux-arm contain malware?
No malware was identified in @img/sharp-linux-arm@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-linux-arm 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-linux-arm 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-linux-arm@0.35.5, cost nothing.