Which versions of solidity-coverage-plus are malicious?

The following npm versions of solidity-coverage-plus are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate solidity-coverage-plus if I installed it?

solidity-coverage-plus is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If solidity-coverage-plus 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-coverage-plus part of a known attack campaign?

Yes — solidity-coverage-plus is associated with the IN-MAL-2026-004599, IN-MAL-2026-004445, IN-MAL-2026-004600, GHSA-j3fh-3pm4-rw5h 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-coverage-plus 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-coverage-plus (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solidity-coverage-plus across your stack and pipelines.

Malicious package

solidity-coverage-plusnpm

Malicious code in solidity-coverage-plus (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4672

Immediate action

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

npm uninstall solidity-coverage-plus

What this malware does

Package name impersonates the well-known solidity-coverage Hardhat plugin (sc-forks) and ships a verbatim copy of the upstream README. On require('solidity-coverage-plus') from hardhat.config.js, plugins/hardhat.plugin.js line 21 enumerates process.env, capturing all uppercase-prefixed variables under 50 chars into a module-level reference. When the user runs npx hardhat coverage, lib/badge.js filters that snapshot for keys matching /KEY|PRIVATE|MNEMONIC|DEPLOYER|WALLET|SEED/i — the canonical names Hardhat projects use for deployer private keys and wallet seed phrases — AES-256-GCM-encrypts the values with a key derived from the hardcoded constant sha256('sc:' + BADGE_SERVICE), base64url-encodes them into the X-Project-Id HTTP header, and POSTs them to https://coverage.rpc-health-monitor.xyz/v1/report. The encryption key is fully derivable from source constants, providing no protection to the user; its sole purpose is to disguise the exfiltrated credentials as opaque data in proxy/IDS logs. The README does not mention any badge service or env transmission. Result: any developer who installs this typosquat and runs the documented coverage workflow has their crypto wallet private keys and seed phrases sent to attacker infrastructure.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

2652225925019da40677d3b3dd05149a0db2e152671efe2720a097d483c13dda

44e5a7775aa2bbde61d35a548198d976f9bdc6e9b11de33a2e28f6a6a9929de6

93aa0144f8f7a1a03e381ebe28f753a21f813a0e39fc8a8c7baa065751b77788

2d7606814c697ba02283baeaeadfd5bbaf282f5850978e54f7b36387d8ad51dc

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solidity-coverage-plus (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solidity-coverage-plus across your stack and pipelines.
If you installed it — respond
solidity-coverage-plus is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If solidity-coverage-plus 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-coverage-plus 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-coverage-plus on npm has been identified as a malicious package (versions 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004599IN-MAL-2026-004445IN-MAL-2026-004600GHSA-j3fh-3pm4-rw5h

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks solidity-coverage-plus-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring