MalwareTipsTools

File scan report

Scan another file

Verdict Safe

Analyzed , 12 hours ago

Is Revival-Client-Installer-x64-v0.1.19.exe safe? Yes, no threats found.

Only 1 of the 71 antivirus engines that checked it flagged this installer, while stronger engines remained silent and the combined sandbox verdict found no corroborating hostile activity.

Moderate evidence · No engine flags it, but no publisher signature confirms who made it.

Install it as usual if it came from the official source

Good practice2 tips

We found nothing harmful in this file.

  1. Install it only if it came from the developer's own website or an official app store.

  2. Keep your antivirus and Windows updates switched on.

No scanner can promise a file is 100% safe.

Why we think so

Share this file report

Revival-Client-Installer-x64-v0.1.19.exe: Safe — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Antivirus results

1 of 71 flagged

  • Flagged 1
  • No detection 70
  • No result 4
FileRevival-Client-Installer-x64-v0.1.19.exe4.8 MBSHA-256 19c0215ce6f7…abd272
  • Code signing Unsigned
  • Test run Completed
  • First seen 13d ago
1 of the 71 antivirus engines that checked it flags it (APEX).

Chapter 02

Why we think so

3 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

APEX alone flagged the installer with a generic malicious label; none of the stronger engines agreed. Six sandbox runs produced a combined clean verdict, with no named injection target, malicious host, confirmed harmful child, or malware-specific rule match, making the isolated detection highly likely to be a false positive.

Full reasoning

Only 1 of the 71 antivirus engines that checked it flagged the file, and that result came from APEX without a named malware family. None of the stronger engines detected it, leaving the isolated generic label uncorroborated. Across six sandbox runs, the combined verdict was clean and no named process-injection target or other high-risk technique was recorded. The mapping lacks the artefact needed to show actual injection and therefore does not count against the file. No malicious host, confirmed harmful child, public malware-sample listing, or malware-specific community rule supports the detection. The main limitation is that the executable is unsigned and our static analysis was unavailable, but the available evidence still strongly favors a false alarm.

Detailed assessment

What We Detected

APEX was the only engine to flag the installer, giving a generic malicious result. The other 74 of the 71 antivirus engines that checked it did not flag it, including all stronger engines represented in the report, and no engine identified a real malware family.

Threat Behavior

Six sandbox runs produced a combined clean verdict. A T1055 mapping appeared without any named target process or supporting artefact, so it does not demonstrate process injection. The observed file and registry changes fit ordinary installer activity, and the only recorded network contact was identified as analysis-environment background traffic rather than sample activity. The completed host check found no malicious or suspicious host.

What To Do Now

The lone generic detection is most consistent with a false positive. Because the executable is unsigned and its internal code was not directly examined by our static analysis, obtain it from the developer's official distribution channel, verify any published checksum, and keep security software enabled while installing it.

Where this verdict could be wrong3 caveats
  • APEX labeled the executable “Malicious,” although no other engine corroborated that generic result.
  • The executable is unsigned and was first seen on Oct 29, 2026, so its publisher identity cannot be authenticated.
  • Our static analysis was not available, so the executable's internal code and packaged components were not directly examined.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Points in its favour
  • Only 1 of the 71 antivirus engines that checked it flagged the installer, and none of the stronger engines agreed.
  • Six sandbox runs produced a combined clean verdict with no named process-injection target.
  • No malicious or suspicious host was found in the complete check of the recorded contact.
  • No confirmed harmful dropped file, malware-specific rule match, or public malware-sample listing was present.
  • The antivirus analysis found no packer, unusually high code entropy, or brand mismatch.
Points against
  • APEX issued the only malicious label, although it was generic and uncorroborated.
  • The executable is unsigned, so there is no authenticated publisher identity.
  • Our static analysis was unavailable, leaving the executable's internal code without direct inspection.

6 sources checked · all complete. See every source

Chapter 03

What it did in our test

It ran in 6 isolated tests; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 6isolated sandbox runs
  • 25sandbox rule tags
  • 2spawned processes
  • 0network contacts
  • 27filesystem & mutex artifacts
Runtime behaviour

What this file did when executed

This file was detonated in 6 sandboxes and its runtime behaviour was observed.

1 clean detonation

Sandbox verdicts

1
  • VT: CLEANclean

Techniques observed in the sandbox

25

MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.

  • T1010
  • T1012
  • T1027· Obfuscated code
  • T1033· Reads user info
  • T1036
  • T1055· Process injection
  • T1059· Runs commands
  • T1069
  • T1071· Application protocol
  • T1082· System recon
  • T1083· Scans your files
  • T1112
  • T1115
  • T1125
  • T1129· Loads modules
  • T1134
  • T1222
  • T1485
  • T1497· Sandbox evasion
  • T1497.001· Sandbox evasion
  • T1529
  • T1547.009· Auto-start
  • T1553
  • T1553.002
  • T1574· Execution hijack

Observed activity

Processes started
2

Programs the file ran, with their command lines.

  • Revival-Client-Installer-x64-v0.1.19.exe"C:\Users\<USER>\Desktop\Revival-Client-Installer-x64-v0.1.19.exe"
  • Revival-Client-Installer-x64-v0.1.19.exe"C:\Users\user\Desktop\Revival-Client-Installer-x64-v0.1.19.exe"
Files
25

Files the file created, changed or deleted.

  • WrittenC:\Users\<USER>\AppData\Local\Temp\nsx2A48.tmp
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nsx2A97.tmp\System.dll
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nsx2A97.tmp\modern-header.bmp
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nsx2A97.tmp\modern-wizard.bmp
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nsx2A97.tmp\nsDialogs.dll
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nsx2A97.tmp\nsis_tauri_utils.dll
Show all 25 entries for files
  • WrittenC:\Users\<USER>\AppData\Local\Revival Client\revival-client.exe
  • WrittenC:\Users\<USER>\AppData\Local\Revival Client\uninstall.exe
  • WrittenC:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Revival Client.lnk
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nszD052.tmp
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nskD0E0.tmp\System.dll
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nskD0E0.tmp\modern-header.bmp
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nskD0E0.tmp\modern-wizard.bmp
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nskD0E0.tmp\nsDialogs.dll
  • WrittenC:\Users\<USER>\AppData\Local\Temp\nszCFB6.tmp
  • DeletedC:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
  • DeletedC:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
  • DeletedC:\Users\<USER>\AppData\Local\Temp\nsuD032.tmp
  • DeletedC:\Users\<USER>\AppData\Local\Temp\nskD0E0.tmp
  • DeletedC:\Users\<USER>\AppData\Local\Temp\nszCF67.tmp
  • DeletedC:\Users\<USER>\AppData\Local\Temp\nsuD0D0.tmp
  • DeletedC:\Users\<USER>\AppData\Local\Temp\nsz27D.tmp
  • DeletedC:\Users\<USER>\AppData\Local\Temp\nsl5CB.tmp
  • DeletedC:\Users\user\AppData\Local\Temp\nsjCBD7.tmp
  • DeletedC:\Users\user\AppData\Local\Temp\nstCA8D.tmp
Registry and auto-start
18

Settings the file changed, including ways to start again after a restart.

  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFiles0000
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\RegFilesHash
  • SetHKEY_CURRENT_USER\SOFTWARE\revivalclient\Revival Client\(Default)
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\MainBinaryName
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\DisplayName
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\DisplayIcon
Show all 18 entries for registry and auto-start
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\DisplayVersion
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\Publisher
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\InstallLocation
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\UninstallString
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\NoModify
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\NoRepair
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Revival Client\EstimatedSize
  • SetHKEY_CURRENT_USER\SOFTWARE\revivalclient\Revival Client\Installer Language
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search\InstalledWin32AppsRevision
  • DeletedHKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\Owner
  • DeletedHKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\SessionHash
  • DeletedHKEY_CURRENT_USER\SOFTWARE\Microsoft\RestartManager\Session0000\Sequence
Mutexes
2

Named locks a program uses so only one copy runs; malware families often reuse them.

  • cversions.3.m
  • Global\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
9

The analysis machine's own processes and connections, recorded in every run.

  • VM processExplorer.EXEC:\Windows\Explorer.EXE
  • VM processservices.exeC:\Windows\system32\services.exe
  • VM processsvchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p
  • VM processsvchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
  • VM processsvchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup
  • VM processsvchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 9 entries for sandbox background — not the file
  • VM processlsass.exeC:\Windows\system32\lsass.exe
  • VM processsvchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p
  • VM hostatm.teams.mira.tm.svc.cloud.microsoft
Dropped payload

Files this sample writes at runtime

This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.

10 not checked
  • f363165f2e3fcb4ede7c…296829Not checked
    no saved verdict
  • 9c76f4d53ceee2a471c9…d114cbNot checked
    no saved verdict
  • e7a48b7968d37ced257a…35158dNot checked
    no saved verdict
  • afe032f942e2ed0bf749…894432Not checked
    no saved verdict
  • 02f4b01047be2560ac69…2216e3Not checked
    no saved verdict
  • 5ba143b5db4a87d32d6e…ad4709Not checked
    no saved verdict
  • 319c6ae8cebf72f419e3…d484a1Not checked
    no saved verdict
  • 386284480fd2ec3f1577…8e8b2fNot checked
    no saved verdict
  • f8b87af1eb0c689347cb…a6321dNot checked
    no saved verdict
  • 4282d38cd70d76c73203…ce2205Not checked
    no saved verdict

Chapter 04

Technical details

1 of the 71 antivirus engines that checked it flags it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteWorth noting: 1 of 71 engines flagged it · 4 gave no result · treated as non-decisive Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxComplete6 runs: 1 clean, 5 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete1 contacted host checked
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 1

The saved verdict treats these detections as likely false positives.

  • APEXMalicious

File fingerprint

Last analyzed
Nov 10, 2026, 4:26 PM UTC
SHA-256
19c0215ce6f7c34086339466b68c3acd6b58f6d91131e76c27a4d87041abd272
SHA-1
7bb69d44e81b17e9e5f2d6e4b0a8493f4a41dcfa
MD5
17560ddf1818af6b673331266b34fdd6

About this file

Revival-Client-Installer-x64-v0.1.19.exe says it is Revival Client, 4.8 MB.

Claims to be
Revival ClientFrom the file's own version information, written by whoever built it.
Type and size
Win32 EXE · 4.8 MB
Signer
UnsignedNo code signature.
First seen
Oct 29, 2026On VirusTotal.
Submitted by
40 distinct sources
Packer
None detected
Entropy
5.60 of 8

First scanned

Antivirus consensus

1 of 71 engines flagged this file

1 malicious0 suspicious70 not flagged4 no result

4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.

  • Tier-118 engines
    0flagged
  • Tier-236 engines
    0flagged
  • Low-trust17 engines
    1flagged
These detections were treated as likely false positives in the saved verdict.
View all 75 engine results
  • APEXMalicious: Malicious
  • AcronisClean
  • AhnLab-V3Clean
  • AlibabaClean
  • alibabacloudClean
  • ALYacClean
  • Antiy-AVLClean
  • ArcabitClean
  • AvastClean
  • Avast-MobileNo result
  • AVGClean
  • AviraClean
  • BitDefenderClean
  • BitDefenderFalxNo result
  • BkavClean
  • CAT-QuickHealClean
  • ClamAVClean
  • CMCClean
  • CrowdStrikeClean
  • CTXClean
  • CylanceClean
  • CynetClean
  • DeepInstinctClean
  • DrWebClean
  • ElasticClean
  • EmsisoftClean
  • ESET-NOD32Clean
  • F-SecureClean
  • FortinetClean
  • GDataClean
  • GoogleClean
  • GridinsoftClean
  • huorongClean
  • IkarusClean
  • JiangminClean
  • K7AntiVirusClean
  • K7GWClean
  • KasperskyClean
  • KingsoftClean
  • LionicClean
  • MalwarebytesClean
  • MaxSecureClean
  • McAfeeDClean
  • MicrosoftClean
  • MicroWorld-eScanClean
  • NANO-AntivirusClean
  • PaloaltoClean
  • PandaClean
  • RisingClean
  • SangforClean
  • SentinelOneClean
  • SkyhighClean
  • SophosClean
  • SUPERAntiSpywareClean
  • SymantecClean
  • SymantecMobileInsightNo result
  • TACHYONClean
  • tehtrisClean
  • TencentClean
  • TrapmineClean
  • TrellixENSClean
  • TrendMicroClean
  • TrendMicro-HouseCallClean
  • TrustlookNo result
  • VaristClean
  • VBA32Clean
  • VIPREClean
  • VirITClean
  • ViRobotClean
  • WebrootClean
  • XcitiumClean
  • YandexClean
  • ZillyaClean
  • ZoneAlarmClean
  • ZonerClean
Rule-based evidence

Signatures and behavior heuristics

Low-severity pattern matches — worth noting but not on their own cause for alarm.

1 heuristic
MITRE ATT&CK profile
Defense evasion× 1
Behavior heuristics
Deterministic patterns derived from scan data and observed runtime behavior
  • ProcessInjection
    T1055
    low

    VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.

    Evidence
    T1055 (sandbox MITRE mapping)
PE forensics

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.

ent 5.60Unpacked
Section entropy5 sections
.text
6.45
.rdata
5.10
.data
4.12
.ndata
0.00
.rsrc
4.63
0.0Packed threshold 7.28.0
Prevalence

How widely this file has been seen

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
40
Moderate upload volume.
Total submissions
43
Includes repeat uploads by the same source.
First seen
13d ago
Oct 29, 2026
Prevalence quadrant
Rare · New
Needs evidence-led scrutiny
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Often established software

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is Revival-Client-Installer-x64-v0.1.19.exe safe?
We found nothing harmful in Revival-Client-Installer-x64-v0.1.19.exe. 1 of the 71 antivirus engines that checked it flags it; after weighing the other evidence we treat that alert as false alarms. Install it only if it came from the developer's own website or an official app store.
What is Revival-Client-Installer-x64-v0.1.19.exe?
Revival-Client-Installer-x64-v0.1.19.exe is a software installer, about 4.8 MB. Its version information says it is “Revival Client”. Version information is written by whoever built the file, so it is a claim, not proof of who made it. VirusTotal first saw it on Oct 29, 2026.
How many antivirus engines detected Revival-Client-Installer-x64-v0.1.19.exe?
1 of the 71 antivirus engines that checked it flags Revival-Client-Installer-x64-v0.1.19.exe (APEX). We weigh which engines flagged it and what else the scan found, not just the count.
What is the SHA-256 hash of Revival-Client-Installer-x64-v0.1.19.exe?
The SHA-256 fingerprint of Revival-Client-Installer-x64-v0.1.19.exe is 19c0215ce6f7c34086339466b68c3acd6b58f6d91131e76c27a4d87041abd272, and its MD5 is 17560ddf1818af6b673331266b34fdd6. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
Is it safe to install Revival-Client-Installer-x64-v0.1.19.exe?
We found nothing harmful in Revival-Client-Installer-x64-v0.1.19.exe. The main caveat is where you got it: attackers sometimes spread malware under the name of real software, so get it from the official website. If your own antivirus warns about it, check the source before you ignore the warning.
How up to date is this analysis of Revival-Client-Installer-x64-v0.1.19.exe?
This report reflects the scan on Nov 10, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.