Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Something odd happened on my company account and I do not know if it was a breach

Short answer

One strange alert is not proof of a breach, and silence is not proof of safety. Treat it as real until checked: change the password and sign out every session from a clean device, turn on a second sign-in step, then read the account's own login and activity history to see whether anything was actually done.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I got a login alert from a country or device nobody in the company uses.
  • A password reset or new-device email arrived that nobody asked for.
  • Emails are in the sent folder that nobody remembers writing, or mail rules appeared.
  • Settings, users or payment details changed and no one admits to it.
  • Customers say they received a strange message that looks like it came from the company.

Why does this happen?

  1. A password from another site was reused

    Passwords stolen from one service are tried on others. If an employee used the same password on a personal site that was breached, the company account can be opened with no hacking at all.

  2. Someone was tricked into giving the login away

    A fake sign-in page or a message asking to confirm an account is enough. The login looks completely normal in the history because it came from the real user's details.

  3. A former employee, contractor or shared login still works

    Accounts that nobody removed after someone left, or one login shared by several people, make real activity impossible to tell from abuse.

  4. Alerts are often harmless, which is why they get ignored

    A phone on mobile data, a VPN or a trip abroad can all look suspicious. The risk is in the pattern: a harmless alert followed by changed settings or forwarding rules is not harmless. The NCSC counts any unauthorised access, or attempted access, to your IT systems as an incident, malicious or accidental.

  5. Securing things too fast can destroy the evidence

    Resetting credentials is right, because stolen logins keep attackers in. Wiping or deleting things before you have kept the records makes it impossible to learn what was reached.

What can I do about it today?

  1. Change the password from a device you trustUse a computer or phone you know is clean, not the one that may be affected. Pick a long password that is used nowhere else.
  2. Sign out all other sessions and turn on a second sign-in stepMost business accounts have a 'sign out everywhere' option and a code or app step for sign-in. Do both for the account in question and for the owner and admin accounts.
  3. Read the account's own history, change nothing yetLook at the login list and the activity or audit log. Write down the time, place and what was done. Take screenshots before you delete anything.
  4. Check for forwarding rules and unknown usersLook in the mailbox rules and in the user list for anything you did not create. Only note them down at this stage.
  5. Tell the people who need to know inside the companyAsk staff not to open odd links and not to reuse the old password anywhere. Keep one person in charge of collecting what is found.
  6. Do not delete accounts, logs or filesRemoving things looks like cleaning up but destroys the record of what happened.

When should I bring someone in?

  • Money moved, customer data was opened or messages went out to your customers.
  • You cannot tell from the history whether a login was real, or the history looks incomplete.
  • The attacker could still be inside, for example you cannot sign in to your own account.

How do I handle it?

  1. Keep a copy of the records firstLogin histories, audit logs and screenshots are saved before any change, so the timeline can be rebuilt.
  2. Build the timelineI list every unusual event in order and mark which ones are explained by real people and which are not.
  3. Close the way inCredentials are reset, sessions ended, a second sign-in step added and rules or users that should not exist are listed for you to approve for removal.
  4. Check what else shares the same loginOther systems that used the same password or the same email address are checked and secured in the same pass.
  5. Write down what is known and not knownYou get a plain summary of what was reached, what is unknown and what to do next. Decisions about telling customers or authorities stay with you and your advisers.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How do I know if it was a real breach?

Look for actions, not just logins: changed settings, new users, mail rules, exports or money movements. A login with no action after it is often harmless, but it still means the password should change.

Should I tell my customers now?

Not before you know what was reached. Whether you must tell anyone depends on your location and on what data was involved, which is a question for a lawyer, not something I can decide.

Can I just change the password and move on?

It stops the same login working, but it does not show whether something was changed or copied. Read the history first and check for rules and users that were added.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.