Attackers could still have active sessions, forwarding rules, connected apps, mailbox permissions or recovery methods. A full security check is essential.
If a business email account is hacked, changing the password is an important first step, but it may not be enough. An attacker could retain access through a signed-in device, malicious app or hidden mailbox rule. Because email is used to reset passwords for other business services, an exposed inbox can also put cloud storage, accounting software and social media accounts at risk.
Some email services keep existing sessions active after a password change. Attackers may also have stolen session tokens, added recovery details or created rules to forward or hide messages.
Use the provider's administration tools to sign out other devices and revoke sessions. If malware may be present on the employee's computer, investigate it before signing in again.
Look for unfamiliar forwarding addresses and rules that move or hide security alerts, invoices or password-reset messages. In Microsoft 365, check inbox rules through the administration tools, including hidden rules.
Review apps authorised to access the mailbox. OAuth permissions can allow an app to read email without knowing the account password. Remove anything unrecognised or unauthorised.
Check who has Full Access, Send As or Send on Behalf permissions. Changing the mailbox owner's password does not necessarily remove access granted to other accounts.
Check registered devices, authenticator apps, passkeys, security keys, phone numbers and recovery addresses. Remove anything the account owner cannot verify.
Your IT provider or email administrator should coordinate the recovery process.
Reduce the risk of future attacks by requiring MFA for all email accounts, restricting automatic external forwarding and controlling which third-party apps employees can authorise. Where supported, passkeys and physical security keys offer stronger protection against phishing. Employees should report unexpected MFA prompts, unfamiliar sign-in alerts and messages they did not send. Regular monitoring and a clear incident response process can help your business identify suspicious activity before it causes further damage.
Not always. The behaviour depends on the provider, so revoke active sessions and tokens separately where necessary.
Yes. Existing sessions, forwarding rules, connected apps or delegated permissions may still provide access.
Yes. Authorised apps can use OAuth permissions to access account data without storing the password. Review and remove suspicious connections.
No. MFA helps protect future sign-ins, but it does not automatically remove forwarding rules, app permissions, delegates or other existing access.
Usually, no. The account should be secured and investigated first, as deleting it could remove evidence needed to understand the incident.

























