Malicious code in solidity-hold (npm)
Description
The npm package [email protected] impersonates the popular pino logger by copying its README badges and source tree but replaces a key module with a heavily obfuscated ~4 MB payload. This payload executes automatically when the package is required, while the advertised middleware export is a no-op. The package also declares an unnecessary axios dependency, enabling potential network communication. The publisher metadata is unrelated to the genuine pino project, indicating malicious intent to deceive users and deliver hidden code execution.
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 solidity-hold package version 2.0.1 on npm is a malicious package that impersonates the widely used pino logger by copying its branding and source structure. However, it replaces the lib/config.js file with a large, obfuscated JavaScript bundle (~4 MB) that executes immediately upon requiring the package. This obfuscated payload uses techniques such as hex string arrays, control-flow flattening, and a rotating decoder loop to evade detection. The package also includes an axios dependency, which is unnecessary for a logger and may enable network egress. The publisher information is unrelated to the legitimate pino project, confirming the package is a hostile payload carrier designed to deceive and potentially compromise systems that install it.
Potential Impact
Any system or developer that installs and requires [email protected] will execute the obfuscated malicious payload embedded in the package. This can lead to unauthorized code execution and potential network communication due to the axios dependency. The impersonation of a trusted package increases the risk of inadvertent installation and exploitation. No known exploits in the wild are reported yet.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance. Until a fix or removal is confirmed, avoid installing or requiring [email protected]. Verify package authenticity before use and prefer official, well-maintained packages. Remove any installations of [email protected] from your environment.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14220
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a85b4c7acd9273b4925282d
Added to database: 08/19/2026, 13:51:03 UTC
Last enriched: 08/19/2026, 14:37:29 UTC
Last updated: 10/02/2026, 13:52:27 UTC
Views: 43
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.