First 30 minutes
Use a clean device, change the most important password first, revoke sessions, contact bank/telco/work if relevant, and preserve evidence.
Response
Prevention matters. So does getting back in, preserving evidence and stopping a bad moment from becoming a month-long admin disaster.
Nigel version
Protect email, phone number, backup codes, password-manager recovery and backups. Test one restore before it matters.



First-30-minutes builder
Most recovery mistakes happen while people are stressed: approve the prompt, wipe the phone, reset from the infected laptop, forget the telco. Pick the incident, then build the first moves.
2 prep items still weak. Fix them while everyone is calm.
Explain the jargon
Tap a term for the plain-English version and the practical move. No fake mystique, just the bit that changes what you do at home.
A device you do not suspect is compromised. It might be another phone, a patched family laptop or a freshly reset machine.
Do this: Use it for password resets and session revocation when the main device may be infected or stolen.
One-time backup codes that get you back into an account when the usual MFA device is gone.
Do this: Store them somewhere safe before the bad day. Do not leave recovery dependent on one phone.
Screenshots, timestamps, sender details and device names can matter for banks, telcos, work and police reports.
Do this: Capture facts before panic-wiping, unless safety or policy requires immediate isolation.
Full guidance
An incident timeline builder for the first 30 minutes and first day.
Use a clean device, change the most important password first, revoke sessions, contact bank/telco/work if relevant, and preserve evidence.
Review account recovery settings, connected devices, mail forwarding rules, payment changes and cloud sharing.
Cloud sync is not the same as backup. Deletion and ransomware can sync too. Keep a second copy for files that matter.
Most household recovery paths route through email. If email is exposed, changing a bank, social or cloud password may not hold because the attacker can still receive reset links. Secure email from a clean device, revoke sessions, check forwarding rules, then move down the account list.
A phone number can sit behind MFA prompts, bank checks and password resets. If the SIM, number or identity documents are involved, slow down enough to record times, contact the provider, report where appropriate, and protect the document trail. Panic-wiping the only evidence helps the wrong person.
Scenario
A login prompt appears while nobody is logging in.
Better response
Worse habit
Approving it because the notification is annoying.
A password reset email appears, mail is missing, or friends receive odd messages from the account.
Better response
Worse habit
Changing a few visible passwords while the email account still controls resets.
The phone loses service, bank checks fail, or a provider says account details changed.
Better response
Worse habit
Assuming it is a reception problem while reset codes and bank checks keep routing through the number.