Is UCheck_setup_win10 (1).exe safe?
A verified ADLICE signature and sparse generic detections are offset by observed T1055 and LSASS-targeting activity whose intent remains unresolved.
Only 3 of 75 engines flagged this signed installer, and no malware family consensus formed. However, one completed sandbox recorded possible process injection and LSASS-targeting activity, while three direct IP contacts could not be reputation-checked completely, so execution should be deferred pending publisher verification.
80cfb967c8a84068a3…359f8104a2395fRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
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.
Only 3 of 75 engines flagged this signed installer, and no malware family consensus formed. However, one completed sandbox recorded possible process injection and LSASS-targeting activity, while three direct IP contacts could not be reputation-checked completely, so execution should be deferred pending publisher verification.
Three of 75 engines raised generic detections, with Sophos providing the only tier-1 flag and no agreed malware family. The ADLICE signature is verified, but the publisher is not on the curated trusted list and has no stored sample history. Runtime evidence mapped activity to T1055 and recorded LSASS targeting, both unusual for an ordinary installer, although the sandbox itself issued no malware finding. Three direct IP connections were observed, but no complete host-reputation result is available. Five dropped children produced no malicious child finding, while their individual verdicts remained unknown. Taken together, the evidence warrants caution but does not establish a specific malware family or confirmed harmful infrastructure.
What We Detected
Three of 75 antivirus engines flagged the executable. Sophos used the generic label Mal/Generic-S, Varist reported W32/ABRisk.OMNI-5343, and Google supplied no family name; there is no tier-1 family consensus. The file carries a verified ADLICE signature, but no established signer history or curated trusted-publisher match is available.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055 and recorded interaction targeting LSASS, which can be associated with process injection or credential access. It also observed direct connections to three IP addresses. Because contactedHosts is unavailable, those addresses did not receive a complete reputation cross-check. No malicious sandbox verdict was issued, and none of five inspected dropped children was identified as malicious, although each child remained individually unclassified.
What To Do Now
Do not run this copy until its download source and ADLICE signature can be verified against the publisher's official release channel. Keep endpoint protection enabled, and quarantine or remove the file if its source cannot be validated or if further monitoring confirms LSASS access or injection behavior.
Where this verdict could be wrong4 caveats
- Only 3/75 engines detected the sample, 16 of 17 tier-1 engines did not flag it, and no tier-1 family consensus exists.
- The executable has a verified ADLICE signature, brandMismatch is null, and peAnalysis.likelyPacked=false.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false after five children were inspected.
- The similarHashes results share only imphash with signerMatchesSubject=false, so installer-framework reuse may explain those matches.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- signing.verified=true for ADLICE.
- 16 of 17 tier-1 engines did not flag the file.
- engines.tier1FamilyConsensus.family=null.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false across five inspected children.
- Runtime evidence mapped possible process injection to MITRE T1055.
- A heuristic recorded process activity targeting LSASS.
- Three direct IP contacts lack a complete host-reputation result.
- Sophos, Google, and Varist account for 3/75 engine detections.
- The ADLICE signer has no stored historical sample statistics.
Verify the installer hash and ADLICE signature through the publisher's official channel before use. Keep endpoint protection enabled and avoid execution if provenance cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 11MITRE ATT&CK techniques
- 12spawned processes
- 3network contacts
- 11filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Reads your Windows user-account details.
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.
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
UCheck_setup_win10 (1).exe
80cfb967c8a84068a39f414162b2e0a6fb19889ceabe58c2a1359f8104a2395f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\setup_qt6.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-SYDI75UT61.tmp\setup_qt6.tmp" /SL5="$180026,53520262,921088,C:\Users\<USER>\Desktop\setup_qt6.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
setup_qt6.tmp
C:\Users\<USER>\AppData\Local\Temp\is-SYDI75UT61.tmp\setup_qt6.tmp
04Isolated runtime analysis - Written fileObserved
UCheck_debug.log
C:\ProgramData\UCheck\Debug\UCheck_debug.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.67.157.48
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.21.74.102
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 172.67.157.48
- 104.21.74.102
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\is-SYDI75UT61.tmp\setup_qt6.tmp
- C:\ProgramData\UCheck\Debug\UCheck_debug.log
- C:\ProgramData\UCheck\cacert.pem
- C:\ProgramData\UCheck\config.ini
- C:\ProgramData\UCheck\scheduler
- Local\SessionImmersiveColorMutex
- UCheck_Mutex
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 3e851abd2da91a527cf7…1b379fNever scannednever seen before
- bdbc2b246edde40111d4…9002d3Never scannednever seen before
- 71a06973b13c1d1140eb…8c202fNever scannednever seen before
- ca3ecf17f0f3d6de2858…ea097dNever scannednever seen before
- 208da2055653465e443d…7338e7Never 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.
- 3rule hits recorded
- 3 / 75engines flagged
- 34sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including Google and Sophos.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from ADLICE.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: UCheck_setup_win10 (1).exe — 80cfb967c8a84068a39f414162b2e0a6fb19889ceabe58c2a1359f8104a2395f
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\setup_qt6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-SYDI75UT61.tmp\setup_qt6.tmp" /SL5="$180026,53520262,921088,C:\Users\<USER>\Desktop\setup_qt6.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: setup_qt6.tmp — C:\Users\<USER>\AppData\Local\Temp\is-SYDI75UT61.tmp\setup_qt6.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: UCheck_debug.log — C:\ProgramData\UCheck\Debug\UCheck_debug.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 172.67.157.48 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.21.74.102 — 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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence172.67.157.48 · 104.21.74.102 · 162.159.36.2
3 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
- UCheck_setup_win10 (1).exe
- Format
- Win32 EXE
- Code signing
- Signature valid: ADLICE
- Size
- 52.3 MB
- Last analyzed
- Sep 14, 2026, 8:06 AM UTC
80cfb967c8a84068a39f414162b2e0a6fb19889ceabe58c2a1359f8104a2395fSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't install it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is UCheck_setup_win10 (1).exe safe, or is it malware?
What is UCheck_setup_win10 (1).exe?
How many antivirus engines detected UCheck_setup_win10 (1).exe?
I already downloaded and installed UCheck_setup_win10 (1).exe — what should I do?
How do I remove UCheck_setup_win10 (1).exe?
Is UCheck_setup_win10 (1).exe digitally signed?
What is the SHA-256 hash of UCheck_setup_win10 (1).exe?
How up to date is this analysis of UCheck_setup_win10 (1).exe?
Community
Member reviews and reports for this exact file hash.