sodcalculator

10 Tech How-To

Check If a Wallet Breach Affects Your Ethereum Validator

Guide 10-50167 · Updated · Step by step

This guide helps you determine whether a wallet security incident—such as a leaked seed phrase, compromised keystore, or stolen withdrawal credentials—puts your Ethereum validator at risk. You’ll learn how to audit your validator’s keys, withdrawal address, and signing activity, and what steps to take if you find a problem. Before starting, ensure you have access to your validator’s keystore files, your withdrawal credentials (if you have them), and a machine you trust (ideally offline for sensitive operations).

What You’ll Need

  • Access to your validator’s keystore files (usually in a keystore directory) and their passwords.
  • The validator’s public key(s) and index number(s) (you can find these in your validator client’s logs or on a beacon chain explorer).
  • If you set withdrawal credentials, the Ethereum address they point to (the “withdrawal address”).
  • A beacon chain explorer (e.g., beaconcha.in) to check validator status and history.
  • Optional: a tool like ethdo or staking-deposit-cli to verify keys offline.

Step-by-Step

  1. Identify the scope of the incident. Determine exactly what was exposed: seed phrase, keystore file + password, withdrawal private key, or the machine running your validator. Write down what was compromised—this guides your actions.
  2. Check your withdrawal credentials. Go to a beacon chain explorer, search for your validator’s public key or index, and look at the “Withdrawal Credentials” field. If they start with 0x00 (BLS) and you never set a withdrawal address, your funds are at risk if the seed phrase or withdrawal key is leaked. If they start with 0x01 (Ethereum address), the withdrawal address is fixed—but if that address’s private key is compromised, your rewards are at risk.
  3. Verify your keystore files are intact and unmodified. Compare the checksums of your keystore files against backups you made before the incident. If they match, the files themselves weren’t tampered with. Use sha256sum on Linux/macOS or Get-FileHash on Windows.
  4. Test your keystore password. Use the validator client’s built-in command or ethdo to attempt to decrypt the keystore with your password. If it fails, the password may have been changed—a sign of compromise.
  5. Check for unauthorized signing activity. Look at your validator’s recent attestations and proposals on the explorer. If you see attestations signed at times when your validator was offline or when you didn’t expect activity, that could indicate someone else is using your keys. Legitimate validators sign roughly every 6.4 minutes; unexpected gaps or bursts are red flags.
  6. Review your withdrawal address history. If your withdrawal credentials are 0x01, check the Ethereum address they point to on a block explorer. Look for any outgoing transactions you didn’t make. If the address is empty or has unexpected activity, your withdrawal key may be compromised.
  7. Check for “double signing” slashing events. On the explorer, see if your validator has a “Slashing” status or a “Slashings” history. If so, someone may have used your keys to sign conflicting messages—this is a critical sign of compromise.
  8. If you suspect compromise, act immediately: If your withdrawal credentials are 0x00 and the seed phrase is leaked, you cannot change them—your funds are at risk. If you have 0x01 credentials, you can move funds from the withdrawal address to a new wallet. If your validator signing key is compromised, you must voluntarily exit your validator to prevent slashing, then withdraw remaining balance to a safe address.
  9. If you are safe, document and monitor. Record the incident, what you checked, and the results. Set up alerts for any future validator activity (many explorers offer email/webhook alerts).

Common Mistakes

  • Assuming a leaked seed phrase only affects the wallet, not the validator—if you used the same seed for both, your validator’s withdrawal key is derived from it.
  • Forgetting that 0x00 withdrawal credentials are immutable. You cannot change them after deposit; if compromised, you can only exit and hope to withdraw before the attacker.
  • Ignoring the difference between the validator signing key (hot) and withdrawal key (cold). Compromise of the signing key allows slashing, but not theft of principal; compromise of withdrawal key allows theft of rewards and principal.
  • Checking only the validator’s balance, not its signing history. A compromised validator may still have a balance but be actively slashed.
  • Using the same machine that was compromised to run checks—malware could alter your findings. Use a clean, offline machine if possible.

Tips

  • Always keep a backup of your keystore files and withdrawal credentials in a secure, offline location (e.g., a hardware wallet or encrypted USB).
  • Use a dedicated withdrawal address that you control separately from your daily-use wallet.
  • Regularly check your validator’s status on a beacon chain explorer—at least weekly—to catch anomalies early.
  • If you’re unsure about a step, use ethdo in “read-only” mode to inspect keys without signing anything.
  • Consider running a “doppelganger” detection tool (if available) to alert you if your validator key signs twice.

Troubleshooting

What if I can’t access my keystore files? If the files are deleted or encrypted by ransomware, you may need to recover from backups. If you have no backup, you may have to exit the validator using your mnemonic (seed phrase) via the deposit CLI’s “existing mnemonic” path.

What if the withdrawal credentials show 0x00 but I thought I set an address? You may have made a deposit before the withdrawal address feature was fully implemented, or you used a tool that didn’t set it. Double-check your deposit data—if you used a recent version of the deposit CLI, it would have set 0x01.

What if the explorer shows no slashing but I see unexpected attestations? It’s possible your validator client is misconfigured or another instance is running with the same keys. Check your client logs and ensure only one instance is running.

What if I find a compromise but my validator is still active? Immediately stop your validator client to prevent further signing. Then, use the exit mechanism (voluntary exit) to remove the validator from the active set. If you can’t do that, move your withdrawal address funds if possible.

What if my withdrawal address is compromised but I have 0x01 credentials? Transfer all ETH from that address to a new wallet you control. Then, consider exiting and re-depositing with a new withdrawal address (though this is complex and not always feasible).

What if I’m not sure if the incident affects my validator at all? If the compromised wallet is unrelated to your validator keys (e.g., a separate hot wallet), your validator is likely safe. But if the seed phrase or private key is shared, treat it as compromised.

Frequently Asked Questions

Q: Can I change my withdrawal credentials after deposit?
A: No. If they are 0x00 (BLS), they are immutable. If they are 0x01 (Ethereum address), you cannot change them either—but you can move funds from that address if you control its private key.

Q: What does “slashing” mean for my validator?
A: Slashing is a penalty for signing conflicting messages. It results in a forced exit and loss of a portion of your stake. It’s a sign that your signing key may be compromised or your client misconfigured.

Q: If my seed phrase is leaked, can the attacker steal my validator’s balance?
A: If your withdrawal credentials are 0x00, yes—they can derive the withdrawal key and eventually withdraw your funds. If they are 0x01, they can’t withdraw to a different address, but they could still slash your validator if they have the signing key.

Q: How do I know if my validator is still active?
A: On a beacon chain explorer, your validator’s status should be “active_ongoing”. If it shows “active_exiting” or “exited”, it may have been compromised or voluntarily exited.

Q: Should I exit my validator if I suspect compromise?
A: If your signing key is compromised, yes—exit immediately to prevent slashing. If only your withdrawal key is compromised, you may have time to move funds, but exiting is safer if you cannot secure the keys.

Q: Can I use a hardware wallet to secure my validator keys?
A: Yes, you can store your withdrawal private key on a hardware wallet, and some validator clients support remote signing with a hardware wallet. This reduces the risk of key compromise.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →