A compromised key feels like the worst-case moment in self-custody. It is not — but it is an emergency, and how you respond in the next few hours matters more than how you feel about it. This article walks through what a compromise actually means in a 2-of-2 multisig wallet, how to recognize one, and how to re-secure your funds by rotating keys.
If you have not yet read Recovery 101: what you actually need to restore a wallet, start there. It explains the difference between keys, seeds, and metadata — the vocabulary the rest of this article assumes.
One compromised key is not stolen funds
Here is the reassurance, stated plainly: in a 2-of-2 multisig, one compromised key does not let an attacker move your money.
SSP uses a 2-of-2 setup — two independent keys, on two separate devices, and both signatures are required to authorize any transaction. One key lives in the browser extension; the other lives on your phone in SSP Key. If you are unsure how that split works, What is 2-of-2 multisig covers it in detail.
The practical consequence is direct. An attacker who steals, phishes, or extracts a single key holds exactly half of what they need. They cannot sign a valid transaction. They cannot drain your wallet. They have a key that, on its own, signs nothing.
This is the entire point of multisig, and it is why a single compromised key is a survivable event rather than a catastrophic one. With a single-key wallet, a stolen key is stolen funds — instantly, irreversibly. With 2-of-2, you get something a single-key holder never gets: time to react.
Why it is still an emergency
Reassurance is not complacency. A compromised key is genuinely urgent for one reason: it removes your safety margin.
A 2-of-2 wallet has a built-in second factor. The moment one key is compromised, that protection is gone. You are now, in effect, running a single-key wallet — except the attacker may already hold that single key. If your second key is then compromised, lost, or phished, the attacker has both halves and your funds are gone.
Think of it as redundancy spent. Multisig gave you two locks. An attacker just picked one. The wallet is still secure today, but it has no margin left. The job now is to restore the redundancy before anything touches the second key.
There is also a quieter risk. An attacker holding one valid key may not give up. They may pivot — phishing you for the second signature, pushing a malicious transaction request for you to approve, or socially engineering support channels. A compromise is not a single event; it is the start of a campaign. Acting fast ends that campaign.
How to recognize a compromised key
Compromise is rarely announced. It usually shows up as a pattern you can learn to spot. The most common ones:
- Device malware. Your computer or phone behaves oddly — unexpected pop-ups, browser extensions you did not install, a wallet UI that asks for your seed phrase when it never did before. Malware that reaches the device a key lives on should be treated as a compromise of that key.
- A phishing-approved transaction. You approved a transaction that was not what you thought it was — a fake "verify your wallet" page, a malicious dApp connection, a transaction whose details did not match the screen you expected. If you signed something under false pretenses, assume the key that signed it is exposed.
- A lost-but-not-wiped device. You lost a phone or laptop and cannot confirm it was locked, encrypted, or remotely wiped. An unrecovered device that holds a key is a key in someone else's hands until proven otherwise.
- A leaked backup. A photo of your seed phrase synced to a cloud account, a backup file on a shared drive, a written phrase someone else may have seen. Anything that exposes the material a key is derived from is a compromise of that key.
The honest test is simple: if you cannot confidently say a key is still exclusively yours, treat it as compromised. Self-custody rewards acting on suspicion, not waiting for proof. For more on the mindset behind this, see Why self-custody matters now.
Act fast: the first hour
When you suspect a compromise, the priority order is fixed.
- Isolate the suspect device. Disconnect it from the internet. Do not "test" the wallet on it. Do not log in to check. Every action on a compromised device can leak more.
- Confirm your funds with the clean key. Use your other device — the one you trust — to check balances. In a 2-of-2, you can still see your wallet; you simply will not authorize anything yet.
- Do not approve anything. This is the critical hour for phishing follow-ups. Treat every transaction request, support message, or "urgent verification" prompt as hostile until your wallet is re-secured.
- Plan the rotation. Decide which key is compromised and how you will replace it. Do not improvise mid-process.
Speed matters because the attacker is racing you for the second key. The faster you rotate, the smaller their window. General incident-response guidance — for example, the NIST Computer Security Incident Handling Guide (SP 800-61) — makes the same point in an enterprise context: containment before eradication, and eradication before recovery. The order is not arbitrary.
How key rotation re-secures the wallet
Rotation is the fix. The principle: a compromised key is permanently burned. You do not "clean" it or trust it again. You replace it, and you move your funds to a wallet the attacker has never touched.
Concretely, that means:
- Generate a fresh wallet on devices you trust — devices that have been checked for malware, or ideally a clean device entirely. This produces two new keys and a new 2-of-2 pair, with no relationship to the compromised one.
- Move your funds from the old wallet to the new one. Because you still control both keys of the old 2-of-2, you can still sign this transfer — the attacker, holding only one key, cannot stop it or front-run it into their own address.
- Retire the old wallet completely. Once funds are moved, the old wallet — and the compromised key inside it — is dead. It holds nothing and signs nothing that matters.
- Re-establish your backups. Your new wallet has a new BIP39 seed. Back it up with the same discipline you would a fresh setup, and make sure the leaked backup that started this incident is destroyed.
The reason this works is the same reason the compromise was survivable: the attacker never had both keys. That gave you a signing majority the attacker could not match — long enough to evacuate to safety. Rotation converts a temporary advantage into a permanent one.
The takeaway
A compromised key is an emergency, not a disaster. The 2-of-2 architecture buys you time that a single-key wallet never offers — but that time is a margin to be spent deliberately, not a reason to relax. Recognize the compromise patterns early, isolate fast, refuse every approval prompt, and rotate to a clean wallet before the second key is ever at risk. Do that, and a stolen key stays exactly what multisig makes it: half of a lock that opens nothing.
