File scan report
Verdict Malicious
Is Step 1 - Disable Defender. exe safe? No, we rate this exact file malicious.
Strong consensus labels from major antivirus engines this file a DefenderControl hacking tool with multiple offensive MITRE techniques.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Treat the file as malicious and block or delete it; maintain all security software in an active state.
What to do now4 steps
This is a hacking tool. It is risky to keep and run, but finding it is not by itself a sign that the device is infected.
What to do
Don't run it unless you got it on purpose for security testing on systems you own. Delete it, then empty the Recycle Bin.
If you didn't put it on the device yourself, delete it and run a full antivirus scan: something else may have brought it.
Tools like this often come with cracked or pirated software. If it came that way, treat the whole download as unsafe and scan everything it installed.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
40 of 70 flagged
- Flagged 40
- No detection 30
- No result 4
- Code signing Signer not verified
- Test run Completed
- First seen 6y ago
Chapter 02
Why we think so
5 points against it and 0 in its favour, checked against the scan evidence.
The reasoning behind this verdict
40 of the 70 antivirus engines that checked it flag the sample, including 8 major antivirus engines that converge on the defendercontrol family. The file carries six offensive MITRE techniques and is listed as known malicious by CIRCL.
The signer has no historical samples in our records, removing any benign-publisher benefit. Community annotations and the CIRCL known-malicious flag reinforce the engine findings.
What We Detected
8 major antivirus engines and 32 additional engines classify the file as a hacking tool targeting Windows Defender.
Threat Behavior
Evidence from the test run shows direct-IP connections, persistence indicators, and registry modifications consistent with tools designed to neutralize security software. The sample is signed by an untracked publisher and appears on malware repositories.
What To Do Now
Do not execute the file. Keep security software enabled and remove the sample from any system where it was downloaded.
- Strong major hacking tool consensus
- Offensive MITRE techniques observed
- Filename mimics security software
- CIRCL marks as known malicious
- Unsigned or unverified signer with no history
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 38sandbox rule tags
- 5spawned processes
- 1network contact
- 40filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Created a Windows service so it keeps running.
Moderate concern: Set itself to start automatically after a restart.
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Used an unusual way to talk to a server.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Checked whether it was running on a test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How hacking tools are used
Hacking tools are programs that can switch off security software, test passwords or attack other computers. Security professionals use them on purpose; criminals also bundle them with malware.
Bottom line:Keep it only if you installed it on purpose, and check how it got onto the device if you didn't.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 6: FileSeen in the test run
Step 1 - Disable Defender.exe
a201f7f81277e28c0bdd680427b979aee70e42e8a98c67f11e7c83d02f8fe7ae
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\Desktop\program.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
a201f7f81277e28c0bdd680427b979aee70e42e8a98c67f11e7c83d02f8fe7ae.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
aut36B6.tmp
C:\Users\<USER>\AppData\Local\Temp\aut36B6.tmp
Test run - Evidence 5 of 6: Written fileSeen in the test run
nbvsaoh
C:\Users\<USER>\AppData\Local\Temp\nbvsaoh
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
52.184.215.140
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
Includes 38 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
40 of the 70 antivirus engines that checked it flag it; a signature that did not verify.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 40
- BitDefender (major engine)Application.HackTool.AQU
- DrWeb (major engine)Tool.DefenderControl.3
- ESET-NOD32 (major engine)Win32/RiskWare.DefenderControl.A application
- Fortinet (major engine)Riskware/Snatch_SM
- GData (major engine)Application.HackTool.AQU
- Kaspersky (major engine)not-a-virus:RiskTool.Win32.Disabler.mi
- Microsoft (major engine)HackTool:Win32/Defendercontrol!pz
- Sophos (major engine)BlueLife Windows Defender Control (PUA)
File fingerprint
- Last analyzed
- Aug 24, 2026, 5:08 PM UTC
- SHA-256
a201f7f81277e28c0bdd680427b979aee70e42e8a98c67f11e7c83d02f8fe7ae- SHA-1
5da4de1dbba55774891497297396fd2e5c306cf5- MD5
3a24a7b7c1ba74a5afa50f88ba81d550
About this file
Step 1 - Disable Defender.exe is a Win32 EXE file of 846.0 kB.
- Type and size
- Win32 EXE · 846.0 kB
- Signer
- Sordum Software (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Dec 16, 2019On VirusTotal.
- Submitted by
- 2,068 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (74), 2 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 9 questions people ask most about this file.
Is Step 1 - Disable Defender.exe a virus?
What is Step 1 - Disable Defender.exe?
How many antivirus engines detected Step 1 - Disable Defender.exe?
What should I do if I already ran Step 1 - Disable Defender.exe?
How do I remove Step 1 - Disable Defender.exe?
What kind of program is Step 1 - Disable Defender.exe?
Is Step 1 - Disable Defender.exe digitally signed?
What is the SHA-256 hash of Step 1 - Disable Defender.exe?
How up to date is this analysis of Step 1 - Disable Defender.exe?
Community
Member reviews and reports for this exact file hash.