{"id":"MAL-2026-14220","revision":"90cb7d969f9b41aca13f7b0f68e6e929","records":[{"revision":"90cb7d969f9b41aca13f7b0f68e6e929","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14220","aliases":[],"title":"Malicious code in solidity-hold (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (39144e822a0964821b92859c04cbe7311ac13a889c585465ac0533c831f1904f)\nThe npm package solidity-hold@2.0.1 impersonates the popular pino logger: the README badges and lib/ source tree are copied from pino (pinojs/pino), but lib/config.js is replaced with a ~4 MB obfuscator.io-obfuscated bundle (hex string-array, rotating while(!![]) decoder IIFE, control-flow flattening, ~23,890-entry string array). index.js requires('./lib/config') at top level, so this opaque payload executes on any require('solidity-hold'). The advertised middleware export is a no-op stub, and the package declares an axios dependency (network egress capability) that a logger does not need. Publisher metadata (author Jackson Blau <hello@jsonspack.com>, bugs URL jsonspack.com/issues) is unrelated to the pino project whose code and branding are copied. Heavy control-flow obfuscation of an auto-executing module inside a package that impersonates a widely used dependency is a payload-carrier shape hostile to any installer that requires the module.\n","state":0,"publishedAt":"2026-08-19T03:03:18+00:00","modifiedAt":"2026-08-19T03:30:19.9590839+00:00","affected":[{"ecosystem":"npm","name":"solidity-hold","ranges":[],"versions":["2.0.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/solidity-hold/v/2.0.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14220","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14220","identifiers":["MAL-2026-14220"]},"retained":false,"historicalAffected":[]}],"coverage":[]}