Registry Modification to Disable Windows Defender Notifications
Adversaries, including RedLine Stealer, modify registry keys to disable Windows Defender notifications, allowing malicious activity to proceed without alerting the user or security teams.
Adversaries and malware, such as the RedLine Stealer infostealer, frequently employ techniques to evade detection on compromised Windows endpoints. One such method involves the manipulation of the Windows Registry to silence security alerts by disabling Windows Defender notifications. By setting the 'DisableNotifications' registry value to '1' within the Windows Defender Security Center policies, attackers effectively suppress warnings that would otherwise notify users of malicious activity or the presence of unauthorized software. This evasion technique is critical for threat actors attempting to maintain persistence and conduct data exfiltration or credential theft while minimizing the likelihood of immediate user intervention. Defenders should monitor registry modifications for this specific key as a high-fidelity indicator of post-exploitation activity.
Attack Chain
- Initial access is established through phishing or exploit kits, resulting in the execution of the RedLine Stealer binary.
- The malware gains elevated privileges or executes within a user session with sufficient permissions to modify system policies.
- The adversary identifies the target registry path: HKLM\SOFTWARE\Policies\Microsoft\Windows Defender Security Center\Notifications.
- Using native Windows utilities or built-in API calls, the malware creates or modifies the 'DisableNotifications' value.
- The registry value is set to '0x00000001' to force the suppression of security alerts.
- The adversary proceeds with additional malicious objectives, such as browser data theft, credential dumping, or command-and-control communication.
- Because security notifications are disabled, the user does not receive alerts regarding the initial compromise or subsequent suspicious process execution.
- The final objective is achieved, such as the exfiltration of sensitive information, with a reduced risk of early detection.
Impact
Successful suppression of Windows Defender notifications significantly increases the risk of successful data exfiltration and long-term endpoint compromise. By silencing security alerts, adversaries can operate with greater stealth, extending their dwell time and decreasing the probability that a user will report suspicious system behavior or unauthorized modifications.
Recommendation
- Deploy the provided Sigma rule to detect modifications to the specified Windows Defender registry path.
- Monitor Sysmon Event ID 13 (RegistryValueset) for changes to the 'DisableNotifications' key.
- Audit administrative access to system registry policies to prevent unauthorized policy modification.
- Investigate any 'DisableNotifications' registry change occurring in conjunction with unknown or unsigned binaries.
Immediate actions
Deploy the Sigma rule to monitor for DisableNotifications registry modifications.
Threat Hunt
Search for instances of DisableNotifications set to 0x00000001 across the fleet.
Data: Endpoint registry telemetry
Mitigations
Enforce policy settings via Group Policy Objects (GPO) to prevent end-user or unauthorized binary modification of security registry keys.
T1112
Detection coverage 1
Detect Registry Modification to Disable Windows Defender Notifications
mediumDetects an attempt to disable Windows Defender notifications by modifying the registry, a technique used by RedLine Stealer to evade security alerts.
Detection queries are available on the platform. Get full rules →