@wrenfield/viemnpm
@wrenfield/viem is a confirmed malicious npm package (MAL-2026-10571) that executes malicious code on install (malicious versions 2.53.1, 2.53.2, 2.53.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @wrenfield/viem (npm)
What this malware does
@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 rewrites the abitype dependency to npm:@wrenfield/[email protected] — a load-bearing transitive substituted with a same-scope sibling package. Consumers who install @wrenfield/viem (whether by name confusion against the legitimate viem package or via social engineering) silently pull in @wrenfield/abitype in place of the legitimate abitype, giving the @wrenfield scope owner control over a core ABI-encoding dependency used throughout viem. The conveyance shape (verbatim upstream code + sibling-scope dependency redirection + retained upstream branding) is the namespace-abuse pattern, but the actual payload, if any, lives in @wrenfield/abitype rather than this package. Routing to human review so a reviewer can inspect @wrenfield/abitype and decide whether to publish a coordinated advisory.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wrenfield/viem (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wrenfield/viem across your stack and pipelines.
If you installed it — respond
Remove @wrenfield/viem from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @wrenfield/viem was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @wrenfield/viem before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @wrenfield/viem-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.