Which versions of solhint-plugin-hyperlane are malicious?

The following PyPI versions of solhint-plugin-hyperlane are flagged malicious: 0.1.0. Treat any of these as compromised.

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

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

If solhint-plugin-hyperlane was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is solhint-plugin-hyperlane part of a known attack campaign?

Yes — solhint-plugin-hyperlane is associated with the GENERIC-questionable-pentest 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?

Search your lockfiles and build artifacts for solhint-plugin-hyperlane (version 0.1.0).

Malicious package

solhint-plugin-hyperlanePyPI

Advisory published Jan 27, 2026Updated Jan 27, 2026

solhint-plugin-hyperlane is a confirmed malicious PyPI package (MAL-2026-547) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solhint-plugin-hyperlane (PyPI)

MAL-2026-547

Immediate action

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

pip uninstall solhint-plugin-hyperlane

What this malware does

Generic campaign for all (likely) research / pentests, where the amount or art of collected data raises questions about the privacy, security and ethical side.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: GENERIC-questionable-pentest

Reasons (based on the campaign):

exfiltration-env-variables
exfiltration-generic
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

5f1d66ba0771661e6786da7d4953af3fc1ff1e280d1c666abd1e69e481274747

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for solhint-plugin-hyperlane (version 0.1.0).
If you installed it — respond
solhint-plugin-hyperlane 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 solhint-plugin-hyperlane was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. solhint-plugin-hyperlane on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-questionable-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database