Malicious code in @wrenfield/viem (npm)
-= Per source details. Do not edit below this line.=-
Package @wrenfield/viem impersonates the popular viem library (homepage viem.sh, repo wevm/viem); README and authors fields credit the real viem maintainers but the package itself is published under an unrelated @wrenfield scope. The shipped source under _cjs/ mirrors viem's real code, but package.json rewrites the abitype dependency via npm alias: "abitype": "npm:@wrenfield/abitype@1.2.4". The CommonJS entry _cjs/index.js calls require("abitype") at module load, so any installer who require()s or imports @wrenfield/viem transitively pulls and executes code from @wrenfield/abitype@1.2.4 — a separate package under the same attacker-controlled scope, outside this tarball. The combination of brand impersonation of a top npm package plus a silent dependency redirect to an attacker-controlled namespace is the namespace-abuse / dependency-hijack pattern: the lure package looks legitimate on inspection, while the actual payload is delivered through the redirected dependency at first import.
왜 이 VPI인가 (설명가능 · 실험적)
VPI 산정 기준
| 영향도(기본값(정보 없음)) | 55.00 |
| 악용 신호(추가 악용신호 없음) | ×1.00 |
| VPI | 55.00 |
VPI 공식 vpi-v1 기준