Which versions of solhint-plugin-hyperlane are malicious?

The following npm versions of solhint-plugin-hyperlane are flagged malicious: 19.9.9, 99.0.0, 99.9.9. Treat any of these as compromised.

How do I remediate solhint-plugin-hyperlane if I installed it?

Remove solhint-plugin-hyperlane 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 solhint-plugin-hyperlane — how do I know if it already compromised me?

If solhint-plugin-hyperlane 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 solhint-plugin-hyperlane part of a known attack campaign?

Yes — solhint-plugin-hyperlane is associated with the GHSA-mp62-7w25-x8jm, RLMA-2026-01584 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 solhint-plugin-hyperlane 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 solhint-plugin-hyperlane (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solhint-plugin-hyperlane across your stack and pipelines.

Malicious package

solhint-plugin-hyperlanenpm

Malicious code in solhint-plugin-hyperlane (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-638

Immediate action

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

npm uninstall solhint-plugin-hyperlane

What this malware does

The package solhint-plugin-hyperlane was found to contain malicious code.

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

3 flagged

19.9.999.0.099.9.9

Indicators of compromise (SHA-256)

cc1aa9de63bf20821ba2b8081862d56bf4238d4d5138cdfae10fa1d260ee9b57

5b4fe59a8ff576654fc3214caf43a6d0dfa98f57811eb76712c98dcf41aa5e8c

8c6249994f4106b5b17ad21985b555f830d18dddb1f0c00a8ca925fa3aab355a

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 solhint-plugin-hyperlane (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solhint-plugin-hyperlane across your stack and pipelines.
If you installed it — respond
Remove solhint-plugin-hyperlane 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 solhint-plugin-hyperlane 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 solhint-plugin-hyperlane 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. solhint-plugin-hyperlane on npm has been identified as a malicious package (versions 19.9.9, 99.0.0, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mp62-7w25-x8jmRLMA-2026-01584

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks solhint-plugin-hyperlane-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