Skip to content
cyber-security.eu

Account compromise

A compromised account is one of the most common incident types today. This page outlines causes, early signs and reasonable first actions.

Who this page is for

IT administrators, helpdesk, SOC analysts, incident owners and any employee taking a suspicion seriously.

What does account compromise mean?

External access to an account, usually through phishing, weak passwords, missing MFA or stolen tokens.

Typical causes

Phishing with harvested password.

Weak or reused passwords.

Token theft after a valid login, where MFA no longer applies.

Missing or weak MFA.

Malware on the endpoint.

Indicators

Unusual sign-ins from atypical countries, devices or times.

New mail rules, especially forwarding or auto-mark-read.

Newly registered devices or MFA methods.

Unusual mail activity, such as bulk sends or replies in old threads.

Unexpected consent to third-party apps (consent phishing).

First actions

Revoke sessions so that stolen tokens become invalid.

Change password and review MFA methods.

Check mail rules and delegated access.

Review logs, ideally in SIEM or audit logs.

Review third-party apps and remove unnecessary permissions.

Escalate to incident response if there are signs of broader activity.

Checklist

  • Revoke sessions
  • Change password, review MFA methods
  • Check mail rules and delegations
  • Review audit logs for unusual sign-ins
  • Review app permissions
  • Assess and possibly isolate the endpoint
  • Escalate on signs of broader compromise

Frequently asked questions

+Is a password reset enough?

No. Without revoking sessions, stolen tokens can keep working.

+When do I escalate to incident response?

As soon as there are signs of more than a single account, data exfiltration or further activity, see [Incident response](/en/incident-response).

Related topics