How to recognise and protect against credential stuffing attacks on your business accounts
Summary
This guide helps you troubleshoot and resolve: How to recognise and protect against credential stuffing attacks on your business accounts. Follow the steps below to fix the issue.
Common Causes
Credential stuffing is a type of automated cyber attack where criminals use large lists of usernames and passwords stolen from other data breaches to try and log into unrelated accounts. Because many people reuse the same password across multiple services, these attacks are surprisingly effective. For Australian small businesses, a successful credential stuffing attack can lead to stolen data, fraudulent invoices, hijacked email accounts, and significant reputational damage. The good news is that recognising the warning signs early and putting a few protective measures in place can dramatically reduce your risk.
Warning Signs of a Credential Stuffing Attack
Because credential stuffing is automated, the first clue is usually a sudden, unusual spike in activity. Watch for the following indicators across your business accounts:
- Multiple failed sign-in attempts in a short period, especially from different geographic locations or unfamiliar countries.
- Account lockouts affecting one or more users without any obvious cause.
- Unusual sign-in times, such as successful logins at 3:00 AM AEST when no-one in your team is working.
- Unexpected MFA prompts arriving on staff phones when they are not actively signing in.
- Mail forwarding rules appearing in Microsoft 365 mailboxes that nobody on your team created.
- Unfamiliar sent items or deleted items in user mailboxes.
- Spike in outbound spam originating from your domain, which may indicate a compromised account is being used to send phishing emails.
Quick Fix Steps
These are the highest-impact actions you can take right now to reduce your exposure. If you manage the accounts yourself, work through them in order. If 220 manages your environment, open a ticket and we will action these on your behalf.
- Enforce multi-factor authentication (MFA) on every business account, with no exceptions. MFA is the single most effective control against credential stuffing.
- Force a password reset for any user showing signs of compromise, and reset passwords for any accounts that share credentials with breached services.
- Block legacy authentication in Microsoft 365, as attackers frequently bypass modern security by targeting older protocols.
- Review sign-in logs in the Microsoft 365 admin centre and disable any active sessions that look suspicious.
- Remove any unauthorised mail rules and revoke any app permissions you do not recognise.
Detailed Protective Measures
Enforce Multi-Factor Authentication in Microsoft 365
If your business uses Microsoft 365, MFA should be mandatory for every user. Modern attackers can guess or purchase valid passwords, but they cannot easily bypass a second factor.
- Sign in to the Microsoft Entra admin centre at
entra.microsoft.comusing an administrator account. - Navigate to Protection > Multifactor authentication.
- Select the users you want to protect, then choose Enable from the bulk actions menu.
- For stronger protection, go to Protection > Conditional Access and create a policy that Requires multifactor authentication for all users, all cloud apps, and all device platforms.
- Encourage staff to use the Microsoft Authenticator app rather than SMS, as SMS-based codes can be intercepted.
Block Legacy Authentication
Legacy authentication protocols (such as POP, IMAP, and older Outlook versions) do not support MFA, making them a common entry point for credential stuffing.
- In the Microsoft Entra admin centre, go to Protection > Conditional Access.
- Create a new policy and configure the Conditions to include Client apps > Exchange ActiveSync clients and Other clients.
- Set the Grant control to Block access.
- Apply the policy to All users and enable the policy.
Review Sign-In Activity and Audit Logs
Regular log reviews help you catch attacks early, before significant damage occurs.
- In the Microsoft Entra admin centre, go to Identity > Monitoring & health > Sign-in logs.
- Filter by Failure reason and look for repeated failures from unfamiliar locations.
- Click any suspicious entry and choose Disable user or Revoke sessions if you confirm malicious activity.
- Also check the Unified Audit Log in the Microsoft Purview compliance portal for mailbox rule changes, mailbox delegations, and app consent grants.
Use a Password Manager and Unique Passwords
Credential stuffing works because people reuse passwords. A password manager removes the temptation by generating and storing a unique, complex password for every service.
- Choose a reputable password manager such as Microsoft Edge Password Manager, 1Password, or Bitwarden.
- Ensure every business account uses a unique password of at least 14 characters.
- Never store passwords in browsers on shared or unmanaged devices.
Enable Brute-Force Protections on Other Platforms
If your business uses Google Workspace, cPanel, or other admin portals, apply similar protections:
- Google Workspace: Enforce 2-Step Verification via Admin console > Security > Authentication > 2-Step Verification.
- WordPress and cPanel: Install a plugin or enable cPHulk to block IPs after repeated failed logins.
- VPNs and firewalls: Enable account lockout thresholds and integrate with a SIEM or alerting tool if available.
What to Do If You Suspect a Successful Breach
If you believe an attacker has successfully logged into one of your business accounts, act quickly. The longer an attacker has access, the more damage they can do.
- Disable the affected account immediately in the Microsoft 365 admin centre to stop further access.
- Reset the password and revoke all active sessions.
- Remove any suspicious mail rules, forwarding rules, and app permissions the attacker may have set up.
- Check for sent mail the attacker may have used to phish your contacts, and notify any recipients.
- Review connected services such as OneDrive, SharePoint, and Teams for unauthorised file access or sharing.
- Document the incident with timestamps and affected accounts, then open a ticket with 220 so we can assist with containment, eradication, and recovery.
- Consider reporting the incident to the Australian Cyber Security Centre at cyber.gov.au/report, particularly if customer data may have been accessed.
Still Having Issues?
💻 Open a Ticket