External website; opens in a new tab.

Remote Support

What should a business do when an email account may be compromised?

Use a trusted recovery route, contain access and preserve evidence; resetting one password may not revoke sessions, forwarding or other affected accounts.

Remote Support

Source review 21 November 2026

Unexpected forwarding, messages you did not send or a suspicious reset alert can indicate compromise, but symptoms alone may not establish its extent. Treat the concern seriously and use a known trusted provider/support route. Do not follow a new login or payment link from the suspicious message itself.

Establish a safe contact and authority

Identify the account owner, authorised business administrator and an alternative communication channel if the mailbox cannot be trusted. A supplier needs explicit authority before changing a company account. If financial instructions have changed, verify them with the relevant party through a previously trusted route; an apparently familiar email thread is not sufficient proof.

Preserve relevant times, safe message details and provider alerts without forwarding confidential material widely. Avoid deleting the only useful evidence in a rush to tidy the inbox. Do not investigate by sending real customer campaigns, probing unrelated accounts or copying a mailbox into an unapproved external tool.

Contain and recover through the actual provider

Follow the provider’s current account-recovery/security process from a trusted device and address. Review passwords, MFA/recovery methods, active sessions/tokens, delegated access, forwarding and mailbox rules as appropriate. A password reset does not necessarily end every session or remove a malicious rule. Check connected applications and other accounts whose recovery depends on this email.

The right steps depend on the platform and incident; a general article cannot replace a scoped investigation. Do not disable security controls or share recovery codes with an unverified helper. Record which changes were actually performed and which permissions or devices remain unverified. If needed, use a competent authorised specialist rather than claim full forensic certainty from an ordinary support check.

Assess consequences and responsibilities

Consider what information or financial instructions may have been accessed or altered, who is affected and whether this is a personal-data breach. The controller’s notification assessment and a processor’s prompt notice duties are different. A reportable breach has time-sensitive requirements; do not wait for a commercial dispute or perfect certainty before assessing them. Record the awareness timeline and seek appropriate targeted advice where material.

Tell relevant people through a safe channel where necessary, giving factual protective actions without unsupported speculation. Restoring access is not the same as proving no information was taken. Avoid absolute statements that an account is “completely safe” unless the actual evidence supports the limited claim being made.

After recovery review mailbox ownership, independent administrator recovery, payment-verification practice and the incident escalation owner. Keep protected evidence and apply lawful retention. A useful outcome is a controlled account and a clear record of known scope, remaining risks and follow-up, not merely a changed password.

Sources and review

Prepared by Yellow Brick Tech. General guidance; the source and test conditions for your own situation still matter.

Next review: 4 May 2027

Related services

How Yellow Brick Tech can help.

Next step

Need to apply this to a real situation?

Ask a question or choose the closest project route. A short conversation can often clarify the next step.