Which versions of ganache-cli-provider are malicious?

The following npm versions of ganache-cli-provider are flagged malicious: 1.7.51. Treat any of these as compromised.

How do I remediate ganache-cli-provider if I installed it?

ganache-cli-provider establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ganache-cli-provider — how do I know if it already compromised me?

If ganache-cli-provider 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 ganache-cli-provider part of a known attack campaign?

Yes — ganache-cli-provider is associated with the GHSA-hfp4-5fx7-5mwm, IN-MAL-2026-003314 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 ganache-cli-provider 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 ganache-cli-provider (version 1.7.51). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ganache-cli-provider across your stack and pipelines.

Malicious package

ganache-cli-providernpm

Malicious code in ganache-cli-provider (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4243

Immediate action

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

npm uninstall ganache-cli-provider

What this malware does

Package name impersonates the widely-used ganache-cli Ethereum development tool but ships only a 138-byte index.js stub that wraps ethers.getDefaultProvider — none of the advertised Ganache functionality is implemented. The package's only real behavior is a postinstall hook in package.json that runs an inline node -e script issuing an HTTPS GET to rqnyz-2605-7280-7--2000-c51.run.pinggy-free.link/npm/-/binary/telemetry. Pinggy free-tunnel hostnames are user-created ephemeral tunnels (operator-controlled endpoints), and the URL path is crafted to mimic npm registry telemetry. The fetch reveals the installer's IP and User-Agent to the operator and confirms successful execution on the host; errors are silently swallowed via try/catch. The combination of typosquat name, sham implementation, and install-time beacon to an anonymous tunnel matches the name-squat dropper / install-time reconnaissance pattern.

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

1 flagged

1.7.51

Indicators of compromise (SHA-256)

9c84ea63480d182abd75e9f993c83905bbc216a0b0d662ad049da1241548b598

144bbaf975156b3114f5526a7e9a8ffbe8eb411a541c7e457b7bf444200a02c5

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ganache-cli-provider (version 1.7.51). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ganache-cli-provider across your stack and pipelines.
If you installed it — respond
ganache-cli-provider establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ganache-cli-provider 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 ganache-cli-provider 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. ganache-cli-provider on npm has been identified as a malicious package (version 1.7.51 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hfp4-5fx7-5mwmIN-MAL-2026-003314

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ganache-cli-provider-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring