Which versions of solidity-lock are malicious?

The following npm versions of solidity-lock are flagged malicious: 2.21.0. Treat any of these as compromised.

How do I remediate solidity-lock if I installed it?

Remove solidity-lock 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.

I already installed solidity-lock — how do I know if it already compromised me?

If solidity-lock 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.

Is solidity-lock part of a known attack campaign?

Yes — solidity-lock is associated with the IN-MAL-2026-020750 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find solidity-lock across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solidity-lock (version 2.21.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solidity-lock across your stack and pipelines.

Malicious package

solidity-locknpm

solidity-lock is a confirmed malicious npm package (MAL-2026-17302) that executes malicious code on install (malicious version 2.21.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solidity-lock (npm)

MAL-2026-17302

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall solidity-lock

What this malware does

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.

Malicious versions

1 flagged

2.21.0

Indicators of compromise (SHA-256)

7e283fd2d07e81705e23d5756d15edd4ff4dc7a074d375111155ef9dca1fd9b8

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solidity-lock (version 2.21.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solidity-lock across your stack and pipelines.
If you installed it — respond
Remove solidity-lock 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 solidity-lock 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 solidity-lock 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

No. solidity-lock on npm has been identified as a malicious package (version 2.21.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020750

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks solidity-lock-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database