ACCOUNT SUPPORT GUIDE

Phishing Email Reported

Accounts troubleshooting guide

Knowledge Base / Accounts / Phishing Email Reported

Problem

Practical checks for phishing email reported. Follow the safe steps below and contact your support team if the issue continues.

These are general troubleshooting checks, not a confirmed diagnosis. Follow your organization's procedures and stop if a step could risk data, safety, or managed equipment.

Symptoms to check

  • A user reports a suspicious email, fake login page, or unexpected file request.
  • The issue may affect one mailbox or many users if a mass campaign is active.

Possible causes

  • A malicious or spoofed sender may be impersonating a trusted company or service.
  • Credential theft or malware can happen if a user clicks a malicious link or opens an unsafe attachment.

Resolution

  1. Do not click any links, download attachments, or reply to the suspicious message. If the email is in a mailbox, use the official report button or your organization's safe-report workflow.
  2. Check whether any user clicked the link or entered credentials. If there was interaction, notify IT/security immediately and follow the contained recovery process.
  3. Review the sender, subject, and associated domain for signs of impersonation. Confirm whether the message matches a known legitimate message from the organization.
  4. If the email was received on a managed device, isolate the mailbox or device according to policy and check for malware or suspicious sign-ins.
  5. Escalate to the security team with the sender details, time received, and whether credentials were entered. Keep evidence without exposing passwords or codes.

Prevention and preparation

  • Train users to verify sender identity, hover before clicking, and report suspicious messages rather than forwarding them to others.
  • Use approved security tools to quarantine suspicious mail and maintain MFA and password hygiene.

Related guides

Still not fixed? Log a support request and include the exact error, who or what is affected, and the steps you already tried. Never include passwords or verification codes.

Submit a ticket

Last reviewed: October 2026