Is rqwa2hxhg.exe safe?
Old unsigned 26 KB EXE with zero engine detections but minimal coverage and no signer history.
No antivirus engine flagged the file across 75 total scanners. The sample is unsigned, extremely rare, and lacks any corroborating malicious signals from sandbox, external intel, or prior similar-hash verdicts.
3bd50397e265518462…d8e31c1615fc5aRecommended next actions
Before running
Treat the file as unverified and avoid running it until more evidence is available.
If you already ran it
Run a full device scan. If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source.
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.
No antivirus engine flagged the file across 75 total scanners. The sample is unsigned, extremely rare, and lacks any corroborating malicious signals from sandbox, external intel, or prior similar-hash verdicts.
Zero malicious detections from 75 engines, including 17 tier-1 engines that returned clean, is a strong negative signal. However, the file is unsigned, has only two historical submissions, and contacted-host reputation data is unavailable. The single low-severity heuristic on direct-IP traffic is inconclusive without host reputation context. Low coverage and absence of a trusted publisher therefore prevent a confident safe verdict.
What We Detected
75 engines scanned the 26 KB Win32 EXE; none returned a malicious or suspicious result. 17 tier-1 engines explicitly classified it clean. The binary is unsigned and shows no packers or high-entropy code sections.
Threat Behavior
One sandbox execution recorded four ambient MITRE techniques and a single direct-IP connection. No offensive techniques, dropped children, or malicious sandbox verdict were observed. External-intel sources (CIRCL, MalwareBazaar, YARAify) returned no matches.
What To Do Now
Because the file is unsigned, rare, and lacks host-reputation coverage, treat it as unknown. Do not run it without additional verification such as code signing, broader sandbox coverage, or submission to multiple independent scanners.
- 0/75 engines flagged malicious
- 17 tier-1 engines returned clean
- no malicious sandbox verdict
- unsigned executable
- rare_old prevalence (2 submissions)
- contactedHosts reputation check unavailable
Keep the file quarantined or delete it; obtain a signed, prevalent alternative if the software is needed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 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
Complete1 signature or behavior rule 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
- 4MITRE ATT&CK techniques
- 1spawned processes
- 1network contacts
- 0filesystem & mutex artifacts
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
rqwa2hxhg.exe
3bd50397e265518462960b076f67489572ddb7291f6b12089ed8e31c1615fc5a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
<MACHINE_DNS_SERVER>
Contact observed during runtime.
03Isolated runtime analysis
3 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.
- <MACHINE_DNS_SERVER>
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: rqwa2hxhg.exe — 3bd50397e265518462960b076f67489572ddb7291f6b12089ed8e31c1615fc5a
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Contacted host: <MACHINE_DNS_SERVER> — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence<MACHINE_DNS_SERVER>
0 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
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- rqwa2hxhg.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 25.5 KB
- Last analyzed
- Aug 19, 2026, 3:37 AM UTC
3bd50397e265518462960b076f67489572ddb7291f6b12089ed8e31c1615fc5aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
There isn't enough information to give this file a clear rating.
- Recovery step 01
Be cautious — an unknown rating is not the same as a clean bill of health.
- Recovery step 02
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 03
When in doubt, don't run it — or scan it again later once it's more widely seen.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is rqwa2hxhg.exe safe? What is it?
What is rqwa2hxhg.exe?
How many antivirus engines detected rqwa2hxhg.exe?
What is the SHA-256 hash of rqwa2hxhg.exe?
How up to date is this analysis of rqwa2hxhg.exe?
Community
Member reviews and reports for this exact file hash.