Defendnot
Defendnot is a tool abused to disable Microsoft Defender on Windows by registering a fake antivirus product with Windows Security Center (WSC), including via the IWscAvStatus interface, causing Defender to automatically turn itself off to avoid conflicts. The content describes it as a research tool originally designed to demonstrate weaknesses in the Windows Security Center trust model, later repurposed operationally in malware campaigns.
Behavior described in the content includes process injection into a trusted Microsoft-signed process such as Taskmgr.exe, interaction with undocumented or vendor-oriented WSC APIs, and fraudulent antivirus registration. In some reporting, Defendnot components were deployed as defendnot.dll and defendnot-loader.exe under %PROGRAMDATA%, with injection telemetry potentially visible via Sysmon Event IDs 7, 8, and 10 and process creation via Event ID 4688. Optional persistence artifacts mentioned alongside its use include autorun registry entries and scheduled task creation or modification.
Defendnot appears in a multi-stage phishing campaign primarily targeting users and organizations in Russia. In that campaign, victims were lured via compressed archives containing business/accounting-themed decoys and malicious LNK files that launched PowerShell to retrieve additional stages from GitHub. After privilege escalation attempts through repeated UAC prompts, the malware disabled Defender through PowerShell configuration changes, exclusions, and Defendnot deployment, then proceeded with reconnaissance, screenshot capture, Amnesia RAT installation, and Hakuna Matata-derived ransomware/WinLocker deployment. Associated infrastructure and tooling mentioned in the content include GitHub and Dropbox for payload hosting and Telegram Bot API for operator notification and exfiltration.
High-confidence indicators and artifacts directly mentioned in the content include Defendnot registering a fake AV in Windows Security Center, possible visible registration of a fake antivirus product in the GUI, Defender state changes, deployment paths such as %PROGRAMDATA%\defendnot.dll and %PROGRAMDATA%\defendnot-loader.exe, and abuse of Taskmgr.exe as an injection target. The primary purpose consistently described is defense evasion through neutralization of Microsoft Defender rather than direct exploitation of Defender itself.
Hunt this family in your stack
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
Techniques & procedures
8 distinct techniques documented for this family, organized by ATT&CK tactic.
Execution
1 technique
Execution
Persistence
3 techniques
Persistence
Figure 15: Scheduled Task Creation... Figure 16: Scheduled Task Updated... Having successfully been established as a registered security product, the additional option exists to implement persistence to ensure survival across system reboots.
Privilege Escalation
4 techniques
Privilege Escalation
Figure 15: Scheduled Task Creation... Figure 16: Scheduled Task Updated... Having successfully been established as a registered security product, the additional option exists to implement persistence to ensure survival across system reboots.
Operating from within the injected process context, defendnot now leverages its elevated position to interact with WSC API IWscAvStatus to register itself as a legitimate antivirus product...
Stealth
3 techniques
Stealth
Register fake AV (Malicious Security Product) via IWscAvStatus Interface... The Windows Security Center processes the fraudulent registration request and accepts it as a legitimate security product (AV).
Defense Impairment
1 technique
Defense Impairment
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Tool used to disable Microsoft Defender as part of the attack chain to facilitate subsequent payload execution.
Tool used to help evade or disable Microsoft Defender scanning as part of the attack chain.
Tool used to disable Microsoft Defender by registering a fake antivirus product, causing Defender to disable itself; supports stealth/persistence for subsequent payload execution.
A repurposed research tool used to disable Microsoft Defender by registering a fake antivirus product with Windows Security Center, forcing Defender to shut down.
The version that knows your environment.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.