GitHub Repo

Detection: Windows Multiple Account Passwords Changed

Updated Date: 2026-05-13 ID: faefb681-14be-4f0d-9cac-0bc0160c7280 Author: Mauricio Velazco, Splunk Type: TTP Product: Splunk Enterprise Security

Description

The following analytic detects instances where more than five unique Windows account passwords are changed within a 10-minute interval. It leverages Event Code 4724 from the Windows Security Event Log, using the wineventlog_security dataset to monitor and count distinct TargetUserName values. This behavior is significant as rapid password changes across multiple accounts are unusual and may indicate unauthorized access or internal compromise. If confirmed malicious, this activity could lead to widespread account compromise, unauthorized access to sensitive information, and potential disruption of services.

 1`wineventlog_security` EventCode=4724 status=success
 2  
 3| bucket span=10m _time
 4  
 5| stats count dc(user) as unique_users values(user) as user values(dest) as dest
 6    BY EventCode signature _time
 7       src_user SubjectDomainName TargetDomainName
 8       Logon_ID
 9  
10| where unique_users > 5
11  
12| `windows_multiple_account_passwords_changed_filter`

Data Source

Name Platform Sourcetype Source
Windows Event Log Security 4724 Windows icon Windows 'XmlWinEventLog' 'XmlWinEventLog:Security'

Macros Used

Name Value
wineventlog_security eventtype="wineventlog_security" OR Channel="security" OR source="XmlWinEventLog:Security" OR source="WinEventLog:Security"
windows_multiple_account_passwords_changed_filter search *
windows_multiple_account_passwords_changed_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic
T1078 Valid Accounts Initial Access
T1098 Account Manipulation Persistence
Exploitation
Installation
Delivery
DE.CM
CIS 10

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting Value
Disabled true
Cron Schedule 0 * * * *
Earliest Time -70m@m
Latest Time -10m@m
Schedule Window auto
Creates Finding (Notable) Yes
Rule Title %name%
Rule Description %description%
Notable Event Fields user, dest
Creates Intermediate Finding (Risk Event) No
TTP detections generate a Finding (Notable) and may generate Intermediate Findings (Risk Events) for associated entities.

Implementation

To successfully implement this search, you need to be ingesting Domain Controller events with the Windows TA. The Advanced Security Audit policy setting Audit User Account Management within Account Management needs to be enabled.

Known False Positives

Service accounts may be responsible for the creation, deletion or modification of accounts for legitimate purposes. Filter as needed.

Associated Analytic Story

Finding

Title Entity Field Entity Type Risk Score
User $src_user$ changed the passwords of multiple accounts in a short period of time. src_user user 50

References

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation ✅ Passing N/A N/A N/A
Unit ✅ Passing Dataset XmlWinEventLog:Security XmlWinEventLog
Integration ✅ Passing Dataset XmlWinEventLog:Security XmlWinEventLog

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 11