How Do You Recover a Hacked Account?
Key takeaways
- Revoke sessions and registered applications before changing the password, because a stolen refresh token survives a password change and keeps the attacker inside.
- Removing inbox forwarding rules and app passwords matters as much as the password, because those are the quiet channels the attacker uses to keep access.
- Rebuild multi-factor authentication on a device you control, and drop any authenticator or number the attacker registered while they were inside.
- Check the account history for what was sent, shared and deleted, because a compromised mailbox is a trusted sender and your contacts will receive the attacker's messages.
- A phone number linked to a compromised email account needs a separate check, because a SIM swap or a forwarded OTP is how the attacker gets back in after you reset.
As of 24 October 2026: the service descriptions, prices and turnaround figures on this page are current.
How do I recover a hacked email account?
Work from a device you know is clean, not from the compromised machine. Change the password there, then immediately revoke every active session and every registered application, because a stolen session token is unaffected by a new password. Remove any forwarding rules, inbox rules, delegates and app passwords you do not recognise, and reset any recovery email address or phone number the attacker added. Rotate the recovery codes and re-enrol two-factor authentication with a device you control. Then read the sent items, the deleted items and the login activity, and note what was forwarded or used to reset other accounts, because a compromised mailbox is a trusted sender and your contacts will act on whatever it sends next.
What if the attacker changed the recovery email or phone number?
Use the provider's own recovery path, not the account's email. For a business account, the domain administrator can reset the account from the admin console, remove the attacker's recovery address and restore access directly. For a consumer account, the provider's recovery flow asks for information only the real owner would have, and you should supply it so it demonstrates knowledge, not just possession of the old password. If the attacker also controls the recovery phone, that is a SIM swap or a port-out, so report it to your operator and ask them to reverse the port, otherwise every OTP goes to the attacker. Where the domain was hijacked, approach the registrar, whose security contact moves faster than a support ticket.
How do I recover a hacked WhatsApp or social media account?
Start with the linked identity, not the app. If a compromised email account was the root, fix it first, because social account re-registration depends on it. Then check for linked devices in the app's security settings and remove anything unfamiliar, and revoke third-party app permissions that could post on your behalf. Register the official mobile number with the platform if you have lost the SIM, and be careful about anyone who calls offering recovery, that being the standard social engineering route. Where an intruder has added a recovery email, it must be removed before a normal reset works. Report the takeover on the platform, and file on cybercrime.gov.in if money was involved.
What should I check after I regain control of the account?
Treat the account as hostile until proven otherwise. Read the sent folder and the deleted items, because the attacker often uses the mailbox to request password resets elsewhere. Check inbox rules, filters and delegates, and remove anything you did not create. Review the list of authorised third-party apps and connected accounts. Check the recovery settings again after the reset, since a reintroduced recovery address is a common way back in. Then look at what else shares that identity: a phone number linked to the account, a password manager, a cloud drive, and any account that used the compromised email for recovery. Those secondary accounts turn a single takeover into a full identity compromise.
| Step | Action | Why it comes here |
|---|---|---|
| 1 | Work from a device and network you know are clean | Otherwise you hand the new credentials straight back |
| 2 | Revoke active sessions and registered applications | Session tokens survive a password change |
| 3 | Change the password and rotate recovery codes | Only meaningful once sessions are dead |
| 4 | Remove unknown forwarding rules, delegates and app passwords | These are the quiet channels back in |
| 5 | Restore your own recovery email and phone, re-enrol 2FA | Otherwise the attacker resets you again |
| 6 | Review sent, deleted and login history, then report | Establishes what was done while they were inside |
What are the frequently asked questions?
Get a straight answer on this
Send us the account type, the last time you had clean access and what changed, and we will tell you the exact recovery order for that platform.
Send us the details See pricing