MAL-2026-17302 Malicious code in solidity-lock (npm)
Malicious package
Published
MAL-2026-17302 is a malicious package: solidity-lock (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-17302/ (Markdown: https://insights.sbomify.com/MAL-2026-17302/index.md)
- Package
- solidity-lock
- Registry
- npm
What is MAL-2026-17302?
MAL-2026-17302 is a malicious package in solidity-lock, published on 30 Sep 2026.
Official description
The package's declared main index.js is a trivial no-op Express middleware whose only real effect is to require('./lib/config'), a ~4 MB obfuscator.io-style bundle (rotating string array, hex-escaped entries, self-executing IIFE) that runs at import time. Package identity does not match the shipped code: package.json name is 'solidity-lock' with a vulnerability-management description, keywords advertise a logger ('fast','logger','stream','json'), scripts are 'smoke:pino'/'smoke:file', the README is a copy of pino's README with the name changed, and index.d.ts references pinojs/pino — three inconsistent cover stories layered over the opaque payload. axios ^1.10.0 is declared as a dependency but is not referenced anywhere in the plain-text sources; the only plausible consumer is the obfuscated blob, consistent with outbound HTTP from the hidden payload. Any process that requires this package executes the obfuscated bundle in-process with full host privileges.
What should I do about MAL-2026-17302?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.