Is QHSafeMain.exe safe?
Clean, properly signed executable with zero engine detections and no malicious behaviour observed.
All 75 engines returned clean results. The file carries a valid digital signature from Beijing Qihu Technology Co. and showed no offensive techniques or malicious network activity in the sandbox.
b1fb5a0acbd06a2f3e…4fb0bccc1a5dafRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
All 75 engines returned clean results. The file carries a valid digital signature from Beijing Qihu Technology Co. and showed no offensive techniques or malicious network activity in the sandbox.
Zero malicious detections across the entire engine set, including 17 tier-1 engines, eliminates the possibility of a known malware family. The verified signature and absence of any offensive MITRE techniques or sandbox alerts further support a benign classification. The file is newly submitted and rare, but the complete lack of malicious indicators outweighs the limited history.
What We Detected
No antivirus engine flagged the sample. The executable is digitally signed and the signature verified successfully. Sandbox analysis recorded only ambient behaviour with zero offensive techniques.
Threat Behavior
No C2 communication, dropped files, persistence mechanisms, or registry modifications associated with malware were observed. External intelligence sources returned no matches.
What To Do Now
The file can be considered safe for normal use. Keep endpoint protection enabled and continue to monitor for any future changes in reputation.
- Zero detections from 75 engines
- Valid code signature from established signer
- No malicious sandbox indicators
The evidence supports treating the file as clean; no further action is required beyond routine security hygiene.
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
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
- 2MITRE ATT&CK techniques
- 2spawned processes
- 0network contacts
- 3filesystem & 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
QHSafeMain.exe
b1fb5a0acbd06a2f3e74df4c3f46b3d4f9c1534d83bb3459584fb0bccc1a5daf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\QHSafeMain.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\QHSafeMain.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
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.
- 1830B7BD-F7A3-4c4d-989B-C004DE465EDE 5648
- 1830B7BD-F7A3-4c4d-989B-C004DE465EDE 2216
- \Sessions\1\BaseNamedObjects\1830B7BD-F7A3-4c4d-989B-C004DE465EDE 6468
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
- 0 / 75engines 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
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from Beijing Qihu Technology Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: QHSafeMain.exe — b1fb5a0acbd06a2f3e74df4c3f46b3d4f9c1534d83bb3459584fb0bccc1a5daf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\QHSafeMain.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\QHSafeMain.exe"
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- QHSafeMain.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Beijing Qihu Technology Co.
- Size
- 4.4 MB
- Last analyzed
- Aug 12, 2026, 10:02 AM UTC
b1fb5a0acbd06a2f3e74df4c3f46b3d4f9c1534d83bb3459584fb0bccc1a5dafSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is QHSafeMain.exe safe?
What is QHSafeMain.exe?
How many antivirus engines detected QHSafeMain.exe?
Is QHSafeMain.exe digitally signed?
What is the SHA-256 hash of QHSafeMain.exe?
Is it safe to run QHSafeMain.exe?
How up to date is this analysis of QHSafeMain.exe?
Community
Member reviews and reports for this exact file hash.