0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
wrenfield-viem
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting wrenfield-viem, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-10571 | Unknown | Malicious code in @wrenfield/viem (npm)--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8ef631151a9f361646ced489dc5cc912a455332dee753090cdb89b94ba74f2f7) @wrenfield/viem republishes the viem codebase under an unrelated npm scope while keeping the upstream homepage (https://viem.sh) and repository (wevm/viem) metadata. The package itself contains no install lifecycle hooks and its CJS main is a pure re-export of viem's public API with no top-level side effects, network I/O, eval, child_process, or filesystem access. The notable change versus upstream is in package.json line 172, which rewrite |
| OSV (opens in a new tab) |
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8ef631151a9f361646ced489dc5cc912a455332dee753090cdb89b94ba74f2f7) @wrenfield/viem republishes the viem codebase under an unrelated npm scope while keeping the upstream homepage (https://viem.sh) and repository (wevm/viem) metadata. The package itself contains no install lifecycle hooks and its CJS main is a pure re-export of viem's public API with no top-level side effects, network I/O, eval, child_process, or filesystem access. The notable change versus upstream is in package.json line 172, which rewrite