ganache-cli-providernpm
Advisory published Updated
ganache-cli-provider is a confirmed malicious npm package (MAL-2026-4243) that opens a backdoor for remote access (malicious version 1.7.51). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ganache-cli-provider (npm)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for ganache-cli-provider (version 1.7.51).
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 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
Campaign
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.