Query: detect Detects the creation of a dMSASvc account using the New-ADServiceAccount cmdlet in certain OUs. The fact that the Cmdlet in logs
Matching passage: Sigma rule: Detects the creation of a dMSASvc account using the New-ADServiceAccount cmdlet in certain OUs. The fact that the Cmdlet. Logsource: windows / process_creation. Rule: title: New DMSA Service Account Created in Specific OUs id: 0ea8db81-2ff6-4525-9448-33bbe7effc13 related: - id: e15bc294-ae2a-45ad-b7d6-637b33868bde type: similar - id: 02122374-b74e-495c-b285-9e4da973f3d6 type: similar status: experimental description: 'Detects the creation of a dMSASvc account using the New-ADServiceAccount cmdlet in certain OUs. The fact that the Cmdlet is used to create a dMSASvc account in a specific OU is highly suspicious. It is a pattern trying to exploit the BadSuccessor privilege escalation vulnerability in Windows Server 2025. On top of that, if the user that is creating the dMSASvc account is not a legitimate administrator or does not have the necessary permissions, it is a strong signal of an attempted or successful abuse of the BaDSuccessor vulnerability for privilege escalation within the Windows Server 2025 Active Directory environment. ' references: - https://www.akamai.com/blog/security-research/abusing-bad-successor-for-privilege-escalation-in-active-directory author: Swachchhanda Shrawan Poudel (Nextron Systems) date: 2025-05-24 tags: - attack.privilege-escalation - attack.initial-access - attack.persistence - attack.stealth - attack.t1078.002 - attack.t1098 logsource: category: process_creation product: windows detection: selection_img: - Image|endswith: - \powershell.exe - \pwsh.exe - \powershell_ise.exe - OriginalFileName: - powershell.exe - pwsh.dll - powershell_ise.exe selection_cli: CommandLine|contains|all: - New-ADServiceAccount - -CreateDelegatedServiceAccount - -path condition: all of selection_* falsepositives: - Unknown level: medium
Near-miss passage: Sigma rule: Detects when AppLocker prevents the execution of an Application, DLL, Script, MSI, or Packaged-App from running.. Logsource: windows / applocker. Rule: title: AppLocker Prevented Application or Script from Running id: 401e5d00-b944-11ea-8f9a-00163ecd60ae status: test description: 'Detects when AppLocker prevents the execution of an Application, DLL, Script, MSI, or Packaged-App from running. ' references: - https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/applocker/what-is-applocker - https://learn.microsoft.com/en-us/windows/security/application-security/application-control/windows-defender-application-control/applocker/using-event-viewer-with-applocker - https://nxlog.co/documentation/nxlog-user-guide/applocker.html author: Pushkarev Dmitry date: 2020-06-28 modified: 2025-12-03 tags: - attack.execution - attack.t1204.002 - attack.t1059.001 - attack.t1059.003 - attack.t1059.005 - attack.t1059.006 - attack.t1059.007 logsource: product: windows service: applocker detection: selection: EventID: - 8004 - 8007 - 8022 - 8025 condition: selection falsepositives: - Unlikely, since this event notifies about blocked application execution. Tune your applocker rules to avoid blocking legitimate applications. level: medium