Potential Abuse of msDS-ManagedAccountPrecededByLink for Privilege Escalation
Detection of PowerShell scripts modifying the msDS-ManagedAccountPrecededByLink attribute, potentially indicating exploitation of the BadSuccessor privilege escalation vulnerability in Windows Server 2025.
This threat brief focuses on the modification of the msDS-ManagedAccountPrecededByLink attribute within Active Directory via PowerShell scripts. This activity is flagged as potentially malicious because it could be indicative of an attempt to exploit the ‘BadSuccessor’ privilege escalation vulnerability in Windows Server 2025. The vulnerability, as outlined in Akamai’s research, allows attackers to manipulate managed service account (dMSA) links to gain elevated privileges. The detection is based on identifying specific PowerShell script patterns that include .Put("msDS-ManagedAccountPrecededByLink' and CN=, which are used to modify these critical AD attributes. Defenders should be aware that legitimate administrative tasks might also trigger this detection, so careful tuning and validation are necessary.
Attack Chain
- Initial Access: An attacker gains initial access to a system with sufficient privileges to execute PowerShell scripts, possibly through compromised credentials or other initial access vectors (T1078.002).
- Discovery: The attacker uses PowerShell to enumerate existing dMSAs and their associated
msDS-ManagedAccountPrecededByLinkattributes. - Attribute Modification: The attacker crafts a PowerShell script to modify the
msDS-ManagedAccountPrecededByLinkattribute of a target dMSA. This involves using the.Put("msDS-ManagedAccountPrecededByLink"command and specifying a new distinguished name (CN=) for the preceding account. - Persistence: The attacker leverages the modified dMSA link to establish a persistent foothold in the environment by gaining control over the targeted dMSA.
- Privilege Escalation: By manipulating the dMSA links, the attacker effectively inherits the permissions and privileges associated with the compromised dMSA, thereby escalating their own privileges.
- Defense Evasion: The attacker may attempt to evade detection by obfuscating the PowerShell script or using other techniques to hide their activity.
- Lateral Movement: With elevated privileges, the attacker can move laterally within the network, accessing sensitive resources and systems.
Impact
Successful exploitation of the ‘BadSuccessor’ vulnerability through modification of the msDS-ManagedAccountPrecededByLink attribute can lead to complete domain compromise. An attacker can gain control over critical services and data, potentially resulting in data breaches, service disruptions, and significant financial losses. The impact is amplified in environments heavily reliant on Active Directory for authentication and authorization.
Recommendation
- Deploy the provided Sigma rule to your SIEM and tune for your environment to detect potentially malicious modifications to dMSA link attributes via PowerShell (logsource: ps_script, product: windows).
- Investigate any alerts triggered by the Sigma rule to determine if the activity is legitimate or indicative of an attempted exploitation of the ‘BadSuccessor’ vulnerability.
- Implement strict access controls and monitoring for systems and accounts with the ability to modify Active Directory attributes.
- Review and harden Active Directory security configurations to prevent unauthorized modification of sensitive attributes.
Detection coverage 2
DMSA Link Attribute Modification via PowerShell
lowDetects modification of dMSA link attributes (msDS-ManagedAccountPrecededByLink) via PowerShell scripts.
Suspicious PowerShell Script with msDS-ManagedAccountPrecededByLink
infoDetects PowerShell scripts containing 'msDS-ManagedAccountPrecededByLink' that might indicate malicious activity.
Detection queries are kept inside the platform. Get full rules →