verify-contract-ethersnpm
Advisory published Updated
verify-contract-ethers is a confirmed malicious npm package (MAL-2026-15598) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in verify-contract-ethers (npm)
What this malware does
The package ships a single bin entry (bin/cli.js) that, when invoked, runs whoami and POSTs the package name, username, hostname, and platform to a hardcoded Cloudflare Workers callback at https://oobme.kunalsharma0553.workers.dev/r/7bq6fz3l15r9. The bin is registered under the name fuels-typegen while the package itself is published as verify-contract-ethers, a name/bin mismatch consistent with typosquatting or dependency-confusion against fuels-typegen / verify-contract. The package's declared description openly states its purpose is to POST package name and whoami to an out-of-band callback, and no legitimate functionality is present beyond that beacon.
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.
The OpenSSF Package Analysis project identified 'verify-contract-ethers' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for verify-contract-ethers (version 1.0.0).
If you installed it — respond
verify-contract-ethers 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 verify-contract-ethers 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks verify-contract-ethers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.