Account takeover response: protect access, safety, and evidence first
An account takeover is more than an unwanted login. An intruder may add a recovery address, create forwarding rules, copy stored data, issue new sessions, or use the account to reset other services. Changing one password without reviewing those changes can leave a quiet route back in.
Work from a device you reasonably trust. If the affected device is behaving unexpectedly, use another updated device for recovery and avoid deleting messages, alerts, or logs until you have recorded them.
Record what changed before revoking the intruder's access
Capture unfamiliar sessions, recovery details, forwarding rules, connected apps, messages, purchases, and security alerts. Then remove persistence and secure connected recovery channels from a device you reasonably trust.
Work in this order unless immediate safety changes it
Open a clean recovery route
Use the provider's official app or a typed bookmark. Recover access, replace the password with a unique one, and add a phishing-resistant sign-in method where supported.
Capture the security history
Record alert times, devices, approximate locations, changed recovery details, case numbers, and unauthorized activity before logs roll over.
Revoke persistence
Sign out other sessions and remove unknown forwarding, filters, delegates, app passwords, passkeys, security keys, and third-party connections.
Inspect connected accounts
Prioritize accounts that use the compromised mailbox or phone for password resets, especially finance, cloud storage, social media, and work administration.
Monitor and close the incident
Check security activity and statements for several weeks. Keep the evidence and provider response with a short note describing what was restored.
Let the signal determine the next owner
| Signal or evidence | What may be happening | Response or owner |
|---|---|---|
| Password changed but alerts continue | A live session or connected app may remain | Revoke all sessions and integrations, then re-enrol trusted devices |
| Messages appear in Sent or Trash | The account was used for impersonation or concealment | Preserve examples and warn affected contacts through another channel |
| Recovery details are unfamiliar | The intruder created a route back | Remove them, replace recovery codes, and review the primary email and phone |
| Financial or work data was available | The event may exceed a personal login problem | Notify the institution or incident owner promptly and follow its response process |
Close the route back in and watch for downstream harm
Treat recovery channels as part of the incident
Primary email, mobile service, authenticator access, and saved recovery codes can all restore access. Secure them before assuming the visible account is isolated.
End access, not only the old password
Review active sessions, app passwords, connected apps, inbox rules, API tokens, and remembered devices. Revoke anything you do not recognize.
Look for actions taken in your name
Check sent mail, purchases, profile changes, downloads, security events, and messages to contacts. The response depends on what the intruder did after entry.
Warn people with a precise message
If the account sent scams, tell contacts which channel was compromised, which messages to ignore, and how you will verify yourself now.
Work out what the intruder could reach after signing in
Build the exposure review around the account's actual powers. A mailbox may reset shopping, banking, social, and cloud accounts. A social account may expose private messages and trusted contacts. An administrator account may change other users. List the connected systems, recovery channels, stored payment methods, and sensitive records before treating the password change as the end of the incident.
Separate observed facts from possibilities. A login alert confirms an event, while an unfamiliar forwarding rule or sent message shows an action. Record the time, device, session, rule, transaction, or message that supports each conclusion. This gives a provider, employer, bank, or affected contact something precise to investigate and avoids claiming that every connected account was accessed without evidence.
Close the case only after trusted recovery details are restored, unknown sessions and connections are gone, consequential actions have been reviewed, and alerts reach a channel you control. If work, financial, health, or identity information was exposed, follow the relevant organization's reporting process even when the account itself appears secure again.
What people ask while responding
Should I delete the compromised account?+
Usually not as a first move. Deletion may remove evidence, break recovery for connected services, or surrender a username. Contain it, document the impact, and decide after dependencies are mapped.
Is changing the password enough?+
No. It may not revoke existing sessions, app passwords, forwarding rules, delegated access, or tokens. Review each persistence route the provider exposes.
What if the provider will not return access?+
Use only the provider's official recovery and appeal routes. Secure connected accounts, warn contacts, retain proof of ownership, and document every case number and response.
Continue the recovery beyond this incident
The right response changes when exposure reaches credit, recovery access, or official records. Use the Identity theft protection hub for the complete topic pathway, then continue with Identity theft recovery plan, Two-factor authentication guide, and Password managers.
If the phone number changed or stopped working, use the SIM-swap response plan.
If the misuse extends beyond one login, review what counts as identity theft.
A compromised tax-software login can also require the tax identity theft workflow.
After recovery, reduce reliance on reusable credentials and set up a passkey with a tested fallback.
Confirm live response details here
Sources for Account takeover response
Confirm current instructions and limits for this specific task before acting.
