Is Revival-Client-Installer-x64-v0.1.11 (1).exe safe?
Unsigned installer shows process-injection and credential-dumper sandbox signals with only a single low-trust engine flag.
One low-trust engine flagged the file; sandbox observed T1055 and T1134 activity. No tier-1 detections, unsigned, and similar imphash samples mostly returned suspicious verdicts.
4a847a6e76823561b8…2555355e78fe67Recommended 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.
One low-trust engine flagged the file; sandbox observed T1055 and T1134 activity. No tier-1 detections, unsigned, and similar imphash samples mostly returned suspicious verdicts.
The single malicious detection comes from a low-trust engine and no tier-1 engines flagged the sample. Sandbox evidence shows process injection and LSASS access, yet the sandbox itself did not return a malicious verdict. The file is unsigned and the imphash matches prior samples that were mostly rated suspicious. Medium prevalence and installer filename provide no strong benign anchor.
What We Detected
75 engines scanned the file; only APEX (low-trust) reported malicious. Sandbox recorded MITRE T1055 and T1134 activity plus LSASS access. The installer is unsigned and drops multiple temporary NSIS files before writing revival-client.exe.
Threat Behavior
Observed techniques map to process injection and token manipulation. No C2 domains, no malicious dropped children, and no external-intel hits were found. Similar imphash samples have mixed verdicts leaning suspicious.
What To Do Now
Do not run the installer on production systems. Keep endpoint protection enabled and consider obtaining the software from an official, signed source if this is a legitimate application.
Where this verdict could be wrong1 caveat
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false; contactedHosts is null so no host-reputation result is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 detections
- No malicious dropped children
- Medium prevalence
- Unsigned executable
- Sandbox observed T1055 and T1134
- 4 of 5 similar imphash samples rated suspicious
Treat as untrusted; obtain a signed copy from the vendor or avoid execution until further verification.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
Complete2 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
- 21MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 23filesystem & 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.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
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.
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
Revival-Client-Installer-x64-v0.1.11 (1).exe
4a847a6e76823561b8a459a7756503e4f0beeeefa46d99832c2555355e78fe67
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Revival-Client-Installer-x64-v0.1.11.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsmB73B.tmp
C:\Users\<USER>\AppData\Local\Temp\nsmB73B.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsmB77A.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
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.
- C:\Users\<USER>\AppData\Local\Temp\nsmB73B.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsmB77A.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsmB77A.tmp\modern-header.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsmB77A.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsmB77A.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\<USER>\AppData\Local\Temp\nsaAC10.tmp
- C:\Users\<USER>\AppData\Local\Temp\nslACED.tmp
- C:\Users\user\AppData\Local\Temp\nspD561.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- ff3f02bc2ad88c599fab…ea5ea9Never scannednever seen before
- 1675d4d05949fe6f36d9…ea946eNever scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- 386284480fd2ec3f1577…8e8b2fNever scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 8c2625472f892ffbfe7a…c1a830Never scannednever seen before
- b47502989cf0623fe331…580daaNever scannednever seen before
- 8c3240094ff1c4f72039…dde895Never scannednever seen before
- 5128e8238770da580b8a…2a2082Never 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.
- 2rule hits recorded
- 1 / 75engines flagged
- 12sources 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
1 of 75 antivirus engines flagged the file, including APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 18 times from 12 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Revival-Client-Installer-x64-v0.1.11 (1).exe — 4a847a6e76823561b8a459a7756503e4f0beeeefa46d99832c2555355e78fe67
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Revival-Client-Installer-x64-v0.1.11.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsmB73B.tmp — C:\Users\<USER>\AppData\Local\Temp\nsmB73B.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsmB77A.tmp\System.dll
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\Explorer.EXESandbox 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.exe
1 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
- Revival-Client-Installer-x64-v0.1.11 (1).exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.4 MB
- Last analyzed
- Aug 19, 2026, 2:13 AM UTC
4a847a6e76823561b8a459a7756503e4f0beeeefa46d99832c2555355e78fe67Safety & 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 Revival-Client-Installer-x64-v0.1.11 (1).exe safe, or is it malware?
What is Revival-Client-Installer-x64-v0.1.11 (1).exe?
How many antivirus engines detected Revival-Client-Installer-x64-v0.1.11 (1).exe?
I already downloaded and installed Revival-Client-Installer-x64-v0.1.11 (1).exe — what should I do?
How do I remove Revival-Client-Installer-x64-v0.1.11 (1).exe?
What is the SHA-256 hash of Revival-Client-Installer-x64-v0.1.11 (1).exe?
How up to date is this analysis of Revival-Client-Installer-x64-v0.1.11 (1).exe?
Community
Member reviews and reports for this exact file hash.