Our call: Is SETUP.EXE safe?Safe
73 of 73 engines report clean; signed by Jiangsu Qinheng Co. and widely distributed since 2012.
- 0 of 73 antivirus engines flagged the file.Observed · Antivirus analysis
- The hash has a long, established submission history across 631 sources.Derived · Submission history
- The file has a valid code signature from Jiangsu Qinheng Co..Observed · Code-signing metadata
64c4e60a7b5c3799fb…bca57297b5Recommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 73 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
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
SETUP.EXE
64c4e60a7b5c3799fba275082a05b68dd5b6ab03d63af0cdb31c59bca57297b5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\SETUP.EXE"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\SETUP.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
udhisapi.dll
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
20.190.155.132
Contact observed during runtime.
05Isolated runtime analysis - Contacted hostObserved
192.229.211.108
Contact observed during runtime.
06Isolated runtime analysis - +1 more recorded observation in Analyst mode
6 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 73 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 631 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Jiangsu Qinheng Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: SETUP.EXE — 64c4e60a7b5c3799fba275082a05b68dd5b6ab03d63af0cdb31c59bca57297b5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\SETUP.EXE"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\SETUP.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: udhisapi.dll — C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 20.190.155.132 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.229.211.108 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
Zero detections across 73 engines, a valid 2012 certificate, and over 600 submitters over 14 years indicate the file is a legitimate installer. Sandbox analysis found no malicious behaviour.
The complete absence of malicious detections from every engine tier, including 16 tier-1 engines, is the strongest signal. The file carries a verified digital signature from Jiangsu Qinheng Co. dated 2012 and has been submitted by 631 distinct sources since first seen, confirming long-term prevalence. Sandbox execution produced only ambient techniques and no malicious verdict. The single heuristic that fired (DirectIpC2) explicitly notes that direct-IP traffic is also common in legitimate installers, and no host-reputation data exists to elevate the signal. No external-intel hits or prior similar-hash verdicts contradict the clean assessment.
What We Detected
73 engines scanned the 83 kB Win32 EXE; none flagged it malicious or suspicious. The binary is signed with a valid certificate issued to Jiangsu Qinheng Co. in February 2012. Prevalence data shows 725 submissions from 631 sources since 2012-02-20, classifying it as common_old.
Threat Behavior
One sandbox execution recorded nine ambient MITRE techniques and 20 direct-IP connections but returned no malicious verdict. No domains, dropped children, or persistence mechanisms were observed. The DirectIpC2 heuristic fired, yet the rule itself states that direct-IP traffic can occur in legitimate installers.
What To Do Now
The file can be executed with standard precautions. Keep endpoint protection enabled; no disabling of security software is required or recommended.
Where this verdict could be wrong2 caveats
- contactedHosts is null, so no complete host-reputation cross-check is available; the 20 contacted IPs cannot be definitively classified.
- signerStats.found=false — no historical sample count for 'Jiangsu Qinheng Co.' in our records, limiting signer-trust weighting.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/73 engines flagged malicious
- verified digital signature from 2012
- common_old prevalence (631 sources)
- no malicious sandbox verdict
Treat the installer as safe; continue normal operations with endpoint protection left enabled.
Behavior
Plain-English impact first, then the observed runtime evidence.
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.
- 20.190.155.132
- 192.229.211.108
- 52.191.219.104
- 23.205.89.23
- 13.71.55.58
- 20.190.155.131
- 52.165.164.15
- 40.68.123.157
- 20.190.155.65
- 51.11.168.232
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42
- C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF80.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF03C.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF06B.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER615.tmp.WERInternalMetadata.xml
- Local\SM0:2800:168:WilStaging_02
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidence20.190.155.132 · 192.229.211.108 · 52.191.219.104
0 of 73 engines flagged this file
View all 73 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- SETUP.EXE
- Format
- Win32 EXE
- Code signing
- Signature valid: Jiangsu Qinheng Co.
- Size
- 81.8 KB
- Last analyzed
- Jul 26, 2026, 5:14 PM UTC
64c4e60a7b5c3799fba275082a05b68dd5b6ab03d63af0cdb31c59bca57297b5Safety & 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.
Install it only when it came from the developer's official site or an official app store.
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
Keep your antivirus and Windows updates switched on so you stay protected.