Is hngr3.exe safe?
Twenty-three of 74 engines flagged this unsigned, newly observed executable, including six tier-1 detections describing generic trojan or malware patterns.
The file drew 23 detections from 74 engines, including six high-trust detections from vendors such as Microsoft and BitDefender. Although one sandbox run did not produce an explicit malware judgment, the unsigned status, minimal prevalence, and broad multi-engine detection pattern make execution unsafe.
8b7d1ad49affcdef59…e2b37e6a8e4299Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The file drew 23 detections from 74 engines, including six high-trust detections from vendors such as Microsoft and BitDefender. Although one sandbox run did not produce an explicit malware judgment, the unsigned status, minimal prevalence, and broad multi-engine detection pattern make execution unsafe.
A substantial 23 of 74 engines detected the executable, and six independent high-trust votes are represented in that count. Microsoft identified Wacatac, while BitDefender, Avast, Avira, Emsisoft, and others used generic trojan or malware labels. The labels do not establish a reliable named family, but they converge on harmful executable code rather than a potentially unwanted application or test file. The file is unsigned and has appeared from only one source, leaving no trusted publisher or established prevalence to counterbalance the detections. One sandbox run had no explicit malicious judgment or offensive-only technique, but that limited observation does not outweigh the static engine evidence, and no complete contacted-host reputation result is available.
What We Detected
Twenty-three of 74 antivirus engines flagged the executable. Six high-trust engines contributed detections, including Microsoft with Wacatac, BitDefender and Emsisoft with GenericKD, Avast with MalwareX, and Avira with Agent terminology. These names do not form a strong consensus around one specific family, but they consistently describe trojan or generic-malware characteristics.
Threat Behavior
One completed sandbox run recorded ambient techniques including T1027, T1082, T1083, and T1129, without an explicit malicious sandbox judgment or offensive-only technique. No domains, IP addresses, or URLs were recorded during that run. A complete contacted-host reputation check is unavailable, so network reputation cannot provide additional reassurance.
What To Do Now
Do not run the executable on a production or personal system. Quarantine or remove it while keeping endpoint protection enabled; if it was already executed, perform a full security scan and review the system for unexpected processes, files, and account activity.
Where this verdict could be wrong4 caveats
- The completed sandbox run produced behaviour.hasMaliciousSandboxVerdict=false and offensiveCount=0.
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false, although absence of those hits does not negate the engine detections.
- Seven tier-1 engines reported the sample clean, and the tier-1 detections do not strongly agree on one family.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false, so the executable does not show common packing indicators.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- One sandbox run produced no explicit malicious verdict
- No offensive-only MITRE techniques were recorded
- No dropped malicious child was identified
- No packing or high-entropy code indicator was found
- No YARAify or MalwareBazaar hit was present
- 23/74 antivirus detections
- Six tier-1 malicious votes
- Unsigned Win32 executable
- Only one submitter and one recorded submission
- Microsoft Wacatac and multiple generic-trojan detections
- No trusted publisher or signer history
Quarantine or delete the file and do not execute it. If it has already run, keep endpoint protection enabled, perform a full scan, and investigate any unexpected system changes.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete23 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 5MITRE ATT&CK techniques
- 3spawned processes
- 0network contacts
- 2filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Scans through your files and folders.
Note: Collects details about your system.
Note: Loads extra code modules while running.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
hngr3.exe
8b7d1ad49affcdef596283c046aae2ebe8bd4462fc5fb9cc94e2b37e6a8e4299
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\wxl-patcher.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\wxl-patcher.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ConDrv
\Device\ConDrv
04Isolated runtime analysis - Written fileObserved
Connect
\Device\ConDrv\\Connect
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- \Device\ConDrv
- \Device\ConDrv\\Connect
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 23 / 74engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
23 of 74 antivirus engines flagged the file, including ALYac and Antiy-AVL.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: hngr3.exe — 8b7d1ad49affcdef596283c046aae2ebe8bd4462fc5fb9cc94e2b37e6a8e4299
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\wxl-patcher.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\wxl-patcher.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: ConDrv — \Device\ConDrv
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Connect — \Device\ConDrv\\Connect
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
23 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 23 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- hngr3.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 152.0 KB
- Last analyzed
- Sep 22, 2026, 12:50 AM UTC
8b7d1ad49affcdef596283c046aae2ebe8bd4462fc5fb9cc94e2b37e6a8e4299Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is hngr3.exe a virus?
What is hngr3.exe?
How many antivirus engines detected hngr3.exe?
What should I do if I already ran hngr3.exe?
How do I remove hngr3.exe?
What kind of malware is hngr3.exe?
What is the SHA-256 hash of hngr3.exe?
How up to date is this analysis of hngr3.exe?
Community
Member reviews and reports for this exact file hash.