Brute Force: Credential Stuffing T1110.004
Tactic: Credential Access
Adversaries may use credentials obtained from breach dumps of unrelated accounts to gain access to target accounts through credential overlap. Occasionally, large numbers of username and password pairs are dumped online when a website or service is compromised and the user account credentials accessed. The information may be useful to an adversary attempting to compromise accounts by taking advantage of the tendency for users to use the same passwords across personal and business accounts.
Events covered
2 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Security-Auditing | Event ID 4624 | An account was successfully logged on. |
| Security-Auditing | Event ID 4625 | An account failed to log on. |
Authoring guide
Patterns shared across the 31 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (75 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (137 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (22 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 2 rules
Elastic 9 rules
- Entra ID Excessive Account Lockouts Detected
- Entra ID Sign-in Brute Force Attempted (Microsoft 365)
- Entra ID User Sign-in Brute Force Attempted
- M365 Identity User Account Lockouts
- M365 Identity User Brute Force Attempted
- Multiple Okta User Auth Events with Same Device Token Hash Behind a Proxy
- Multiple Okta User Authentication Events with Same Device Token Hash
- Okta Successful Login After Credential Attack
- Potential Okta Credential Stuffing (Single Source)
Splunk 12 rules
- AWS High Number Of Failed Authentications From Ip
- AWS Multiple Users Failing To Authenticate From Ip
- AWS Unusual Number of Failed Authentications From Ip
- Azure AD Multi-Source Failed Authentications Spike
- Azure AD Multiple Users Failing To Authenticate From Ip
- Azure AD Unusual Number of Failed Authentications From Ip
- CrushFTP Max Simultaneous Users From IP
- GCP Multiple Users Failing To Authenticate From Ip
- GCP Unusual Number of Failed Authentications From Ip
- O365 Multi-Source Failed Authentications Spike
- O365 Multiple Users Failing To Authenticate From Ip
- Windows Local Administrator Credential Stuffing
Kusto 2 rules
- Cross-Cloud Unauthorized Credential Access Detection From AWS RDS Login
- Unauthorized user access across AWS and Azure
YARA-L 3 rules
- AWS High Number Of Unknown User Authentication Attempts
- AWS Unusual Number Of Failed Authentication Attempts From The Same IP
- Okta ThreatInsight Login Failure With High Unknown Users