T1562.011 Google Chronicle · YARA-L

Detect Spoof Security Alerting in Google Chronicle

Adversaries may spoof security alerting from tools, presenting false evidence to impair defenders' awareness of malicious activity. Messages produced by defensive tools contain information about potential security events as well as the functioning status of security software and the system. Rather than or in addition to Indicator Blocking, an adversary can spoof positive affirmations that security tools are continuing to function even after legitimate security tools have been disabled. An adversary can also present a 'healthy' system status even after infection. For example, adversaries may show a fake Windows Security GUI and tray icon with a 'healthy' system status after Windows Defender and other system tools have been disabled. This technique was observed in Black Basta ransomware campaigns using custom EDR evasion tools tied to FIN7.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1562 Impair Defenses
Sub-technique
T1562.011 Spoof Security Alerting
Canonical reference
https://attack.mitre.org/techniques/T1562/011/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1562_011_spoof_security_alerting {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects T1562.011 Spoof Security Alerting — fake Windows Security GUIs and Defender service disablement. Observed in Black Basta ransomware via FIN7-linked EDR evasion tools."
    mitre_attack_tactic = "Defense Evasion"
    mitre_attack_technique = "T1562.011"
    severity = "CRITICAL"
    priority = "HIGH"
    created = "2026-04-21"

  events:
    (
      $e.metadata.event_type = "PROCESS_LAUNCH"
      and (
        (
          (
            re.regex($e.target.process.file.full_path, `(?i)(SecurityHealthSystray\.exe|SecurityHealthHost\.exe|MSASCuiL\.exe|NisSrv\.exe)$`)
          )
          and not (
            re.regex($e.target.process.file.full_path, `(?i)^C:\\Windows\\System32\\`) or
            re.regex($e.target.process.file.full_path, `(?i)^C:\\Program Files\\Windows Defender\\`) or
            re.regex($e.target.process.file.full_path, `(?i)^C:\\ProgramData\\Microsoft\\Windows Defender\\'`)
          )
        ) or
        (
          re.regex($e.target.process.command_line, `(?i)(SecurityHealth|Windows Defender|WindowsSecurity)`) and
          not re.regex($e.target.process.file.full_path, `(?i)(SecurityHealthSystray\.exe|SecurityHealthHost\.exe|MSASCuiL\.exe|NisSrv\.exe|MsMpEng\.exe|svchost\.exe|services\.exe)$`)
        ) or
        (
          re.regex($e.target.process.command_line, `(?i)(sc stop WinDefend|sc stop SecurityHealthService|sc stop wscsvc|DisableRealtimeMonitoring|sc config WinDefend start= disabled)`)
        )
      )
    )

  condition:
    $e
}
critical severity high confidence

Chronicle YARA-L 2.0 rule detecting T1562.011 Spoof Security Alerting via UDM process launch events. Identifies three attack patterns: (1) Windows Defender and Security Health executables running from unauthorized paths indicating spoofed security GUIs, (2) non-security processes masquerading with defender-themed command-line arguments, and (3) direct service-control commands disabling core Windows Defender and Security Center services. This technique was used by FIN7-associated tooling in Black Basta ransomware pre-encryption phases.

Data Sources

Windows Endpoint DetectionSysmon via Chronicle forwarder

Required Tables

UDM Events (PROCESS_LAUNCH)

False Positives & Tuning

  • Enterprise endpoint management solutions that temporarily stage or run Defender-related binaries from temp directories during update or remediation workflows
  • Custom security dashboards or monitoring tools that invoke Defender command-line interfaces from non-standard script directories
  • Incident response toolkits that collect Defender status by calling sc.exe with Defender service names for forensic triage
Download portable Sigma rule (.yml)

Other platforms for T1562.011


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Fake SecurityHealthSystray from TEMP Directory

    Expected signal: Sysmon Event ID 1: Process Create with Image pointing to %TEMP%\SecurityHealthSystray.exe instead of C:\Windows\System32\. Sysmon Event ID 11: File Create for the copied binary. DeviceProcessEvents in MDE shows FolderPath as the TEMP directory.

  2. Test 2Disable Windows Defender Real-Time Monitoring

    Expected signal: Sysmon Event ID 1: Process Create with CommandLine containing 'Set-MpPreference -DisableRealtimeMonitoring'. PowerShell ScriptBlock Log Event ID 4104. Microsoft-Windows-Windows Defender/Operational Event ID 5001 (Real-Time Protection disabled). If Tamper Protection is on, Event ID 1125 (tamper attempt blocked).

  3. Test 3Stop Windows Defender Service via sc.exe

    Expected signal: Sysmon Event ID 1: Process Create with CommandLine 'sc stop WinDefend'. System Event ID 7036: WinDefend service entered stopped state. If Tamper Protection is on, the command will fail with Access Denied.

Unlock Pro Content

Get the full detection package for T1562.011 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections