Is Oxy Recoil.exe safe?
Thirty-one of 75 engines flagged this unsigned executable, seven tier-1 engines detected it, and eight researcher YARA rules add strong corroboration.
The unsigned executable drew 31 detections from 75 engines, including seven tier-1 products, with GameHack and Wacatac among the recurring labels. Eight researcher YARA rules also matched, while the single sandbox run did not produce a malicious verdict and its observed IP lacked a completed reputation check.
73557d7ec8fc056947…8343892a7c3444Recommended 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 unsigned executable drew 31 detections from 75 engines, including seven tier-1 products, with GameHack and Wacatac among the recurring labels. Eight researcher YARA rules also matched, while the single sandbox run did not produce a malicious verdict and its observed IP lacked a completed reputation check.
A broad 31/75 engine response includes seven tier-1 detections, which cannot reasonably be dismissed as low-trust noise. Microsoft and TrendMicro identify Wacatac-related activity, while ESET-NOD32 and Fortinet use GameHack labels, although only two tier-1 engines agree on the latter family. Eight YARAify rules matched, including FreddyBearDropper, adding strong independent static corroboration. The executable is unsigned and has no established publisher history to counterbalance these findings. One sandbox run recorded no malicious verdict or offensive-only technique, but it contacted 162.159.36.2 and no complete host-reputation result is available. The combined engine and researcher-rule evidence substantially outweighs the limited benign-leaning runtime observations.
What We Detected
31 of 75 antivirus engines flagged the executable, including seven tier-1 products. Microsoft reported Trojan:Win32/Wacatac.B!ml, TrendMicro reported Trojan.Win32.WACATAC.USBLIH26, and ESET-NOD32 identified GameHack_AGen. Eight researcher YARA rules also matched, including FreddyBearDropper and dsc.
Threat Behavior
The completed sandbox run recorded 12 general techniques but no offensive-only techniques, persistence indicators, or explicit malicious sandbox verdict. It observed a connection to 162.159.36.2; however, the host-reputation cross-check was not completed or saved, so that connection cannot be characterized as clean or hostile. Two written child files were inspected but remain unclassified.
What To Do Now
Do not run the executable on a production or personal system. Keep endpoint protection enabled, quarantine or remove the file, and investigate any machine where it was already launched for related processes, written files, and unexpected network activity.
Where this verdict could be wrong4 caveats
- engines.tier1FamilyConsensus.strong=false: only 2 tier-1 engines agree on gamehack, and several detections are generic or PUA-oriented.
- behaviour.hasMaliciousSandboxVerdict=false, offensiveCount=0, and no persistence indicators were observed in the single sandbox run.
- droppedChildren.hasMaliciousChild=false, although both inspected children have unknown verdicts.
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false, providing no static packing signal.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- behaviour.hasMaliciousSandboxVerdict=false in one completed sandbox run
- behaviour.offensiveCount=0
- No persistence indicators were observed
- peAnalysis.likelyPacked=false and highEntropyCode=false
- droppedChildren.hasMaliciousChild=false
- 31/75 antivirus detections
- Seven tier-1 engine detections
- Eight YARAify rule matches
- Unsigned Win32 executable with no signer history
- Wacatac and GameHack labels across established engines
- Direct contact with 162.159.36.2 without completed reputation coverage
Quarantine or delete the executable and do not launch it. If it has already run, keep security protection enabled and perform a full system scan plus targeted review of its written files and network activity.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete31 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete6 signature or behavior rules matched.
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
- 12MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 2filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
Oxy Recoil.exe
73557d7ec8fc05694702d2fe559099f100168aade6222e68088343892a7c3444
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Oxy Recoil.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\Oxy Recoil.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
imgui.ini
C:\Users\<USER>\Desktop\imgui.ini
04Isolated runtime analysis - Written fileObserved
imgui.ini
C:\Users\user\Desktop\imgui.ini
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\Desktop\imgui.ini
- C:\Users\user\Desktop\imgui.ini
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- dd81598d794e74445671…97ab78Never scannednever seen before
- 32dc7778d4790ae1be9b…2aadd7Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 6rule hits recorded
- 31 / 75engines flagged
- 312sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
31 of 75 antivirus engines flagged the file, including ALYac and Antiy-AVL.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 8 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Oxy Recoil.exe — 73557d7ec8fc05694702d2fe559099f100168aade6222e68088343892a7c3444
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Oxy Recoil.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\Oxy Recoil.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: imgui.ini — C:\Users\<USER>\Desktop\imgui.ini
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: imgui.ini — C:\Users\user\Desktop\imgui.ini
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- Check_OutputDebugStringA_iat
- dsc
- FreddyBearDropper
- golang_bin_JCorn_CSC846
- pe_detect_tls_callbacks
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence162.159.36.2
31 of 75 engines flagged this file
View all 75 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Oxy Recoil.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 606.5 KB
- Last analyzed
- Sep 23, 2026, 9:25 AM UTC
73557d7ec8fc05694702d2fe559099f100168aade6222e68088343892a7c3444Safety & 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
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- 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 Oxy Recoil.exe malware?
What is Oxy Recoil.exe?
How many antivirus engines detected Oxy Recoil.exe?
I already downloaded and ran Oxy Recoil.exe — what should I do?
How do I remove Oxy Recoil.exe?
What kind of malware is Oxy Recoil.exe?
What is the SHA-256 hash of Oxy Recoil.exe?
How up to date is this analysis of Oxy Recoil.exe?
Community
Member reviews and reports for this exact file hash.