Is OverlayCat_1.1.0_windows_x64-setup.exe safe?
Unsigned installer with zero engine detections but imphash matches to previously suspicious samples.
No antivirus engine flagged the file, yet the imphash matches four prior suspicious and one malicious installer. The unsigned status and single sandbox run showing T1134 leave the risk level unresolved.
75833b331c6b997e6e…42eaee52db0404Recommended 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.
No antivirus engine flagged the file, yet the imphash matches four prior suspicious and one malicious installer. The unsigned status and single sandbox run showing T1134 leave the risk level unresolved.
Seventy-five engines returned zero malicious detections, including seventeen tier-1 engines. The file is unsigned despite being an installer, and its imphash collides with four previously suspicious samples and one malicious sample. Sandbox execution recorded one offensive technique (T1134) but no malicious verdict or dropped malicious children. The contacted IP lacks a completed host-reputation check, leaving the direct-IP heuristic inconclusive.
What We Detected
Zero detections across 75 engines, including all tier-1 engines. The executable is unsigned and carries an imphash shared by other installer packages previously flagged suspicious or malicious.
Threat Behavior
One sandbox run observed T1134 (access token manipulation) plus common installer activity. No malicious sandbox verdict, no dropped malicious children, and no completed host-reputation check for the single contacted IP.
What To Do Now
Run the installer only in a controlled environment or obtain a signed build from the vendor. Keep endpoint protection enabled and monitor for unexpected outbound connections.
Where this verdict could be wrong1 caveat
- similarHashes shows 4/5 prior imphash matches flagged suspicious despite zero engine detections — possible installer-framework false-positive pattern.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- zero engine detections
- medium prevalence
- no malicious sandbox verdict
- unsigned installer
- imphash matches prior suspicious samples
- direct-IP contact without domain
Treat as borderline; do not execute on production systems until a signed version or additional reputation data is available.
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
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 16MITRE ATT&CK techniques
- 1spawned processes
- 1network contacts
- 13filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
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
OverlayCat_1.1.0_windows_x64-setup.exe
75833b331c6b997e6e669490f6c47730dc0e56521c05b53e4242eaee52db0404
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\OverlayCat_1.1.0_windows_x64-setup.exe"
02Isolated runtime analysis
Files
Created or changed
- Written fileObserved
nscA5C7.tmp
C:\Users\<USER>\AppData\Local\Temp\nscA5C7.tmp
03Isolated runtime analysis - Written fileObserved
LangDLL.dll
C:\Users\<USER>\AppData\Local\Temp\nsiA636.tmp\LangDLL.dll
04Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
05Isolated runtime analysis
5 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>\AppData\Local\Temp\nscA5C7.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsiA636.tmp\LangDLL.dll
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\Users\user\AppData\Local\Temp
- C:\Users\user\AppData\Local\Temp\
- C:\Users\<USER>\AppData\Local\Temp\nsxA421.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsiA636.tmp
- C:\Users\user\AppData\Local\Temp\nsj376B.tmp
- C:\Users\user\AppData\Local\Temp\nsnC9.tmp
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 4cf25411f28f639f7215…2d5b7eNever 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.
- 1rule hit recorded
- 0 / 75engines flagged
- 56sources 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 59 times from 56 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: OverlayCat_1.1.0_windows_x64-setup.exe — 75833b331c6b997e6e669490f6c47730dc0e56521c05b53e4242eaee52db0404
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\user\Desktop\OverlayCat_1.1.0_windows_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
File written: nscA5C7.tmp — C:\Users\<USER>\AppData\Local\Temp\nscA5C7.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: LangDLL.dll — C:\Users\<USER>\AppData\Local\Temp\nsiA636.tmp\LangDLL.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.
Evidence162.159.36.2
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- OverlayCat_1.1.0_windows_x64-setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 30.9 MB
- Last analyzed
- Sep 7, 2026, 5:56 PM UTC
75833b331c6b997e6e669490f6c47730dc0e56521c05b53e4242eaee52db0404Safety & 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 OverlayCat_1.1.0_windows_x64-setup.exe safe, or is it malware?
What is OverlayCat_1.1.0_windows_x64-setup.exe?
How many antivirus engines detected OverlayCat_1.1.0_windows_x64-setup.exe?
What should I do if I already installed OverlayCat_1.1.0_windows_x64-setup.exe?
How do I remove OverlayCat_1.1.0_windows_x64-setup.exe?
What is the SHA-256 hash of OverlayCat_1.1.0_windows_x64-setup.exe?
How up to date is this analysis of OverlayCat_1.1.0_windows_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.