MAL-2026-10571: Malicious code in @wrenfield/viem (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fa26048a977a00adcd1ffc42ccf06110e3807bb2a3145a01fd01318dcfe79771) 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/[email protected]"`. The CommonJS entry `_cjs/index.js` calls `require("abitype")` at module load, so any installer who `require()`s or `import`s `@wrenfield/viem` transitively pulls and executes code from `@wrenfield/[email protected]` — 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.
AI Analysis
Technical Summary
The malicious package @wrenfield/viem mimics the popular viem library's code and metadata but is published under the @wrenfield scope, which is unrelated to the original maintainers. Its package.json uses an npm alias to redirect the abitype dependency to @wrenfield/[email protected], an attacker-controlled package outside the main tarball. When the CommonJS entry point is loaded, it requires this aliased abitype package, causing execution of attacker-controlled code. This technique combines brand impersonation with dependency hijacking to deliver malicious code stealthily upon import or require.
Potential Impact
Users who install and import or require @wrenfield/[email protected] will unknowingly execute malicious code from the attacker-controlled @wrenfield/abitype package. This can lead to arbitrary code execution within the context of the importing application, potentially compromising the system or data depending on the environment where the package is used.
Mitigation Recommendations
No official patch or fix is currently documented. Users should avoid installing or using the @wrenfield/viem package, especially version 2.53.4. Verify package provenance carefully and prefer the official viem package from the legitimate maintainers. Monitor vendor advisories for updates or official remediation guidance.
MAL-2026-10571: Malicious code in @wrenfield/viem (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fa26048a977a00adcd1ffc42ccf06110e3807bb2a3145a01fd01318dcfe79771) 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/[email protected]"`. The CommonJS entry `_cjs/index.js` calls `require("abitype")` at module load, so any installer who `require()`s or `import`s `@wrenfield/viem` transitively pulls and executes code from `@wrenfield/[email protected]` — 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The malicious package @wrenfield/viem mimics the popular viem library's code and metadata but is published under the @wrenfield scope, which is unrelated to the original maintainers. Its package.json uses an npm alias to redirect the abitype dependency to @wrenfield/[email protected], an attacker-controlled package outside the main tarball. When the CommonJS entry point is loaded, it requires this aliased abitype package, causing execution of attacker-controlled code. This technique combines brand impersonation with dependency hijacking to deliver malicious code stealthily upon import or require.
Potential Impact
Users who install and import or require @wrenfield/[email protected] will unknowingly execute malicious code from the attacker-controlled @wrenfield/abitype package. This can lead to arbitrary code execution within the context of the importing application, potentially compromising the system or data depending on the environment where the package is used.
Mitigation Recommendations
No official patch or fix is currently documented. Users should avoid installing or using the @wrenfield/viem package, especially version 2.53.4. Verify package provenance carefully and prefer the official viem package from the legitimate maintainers. Monitor vendor advisories for updates or official remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10571
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff5068715ace432eff20
Added to database: 07/14/2026, 09:20:16 UTC
Last enriched: 07/14/2026, 09:25:20 UTC
Last updated: 07/14/2026, 09:27:51 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.