Is RevivalSetup.exe safe?
No antivirus engine detected this unsigned installer, but one sandbox recorded offensive technique mappings, LSASS-related activity, and an unchecked direct-IP connection.
All 75 engines were non-detecting, including 17 tier-1 products, and no dropped child was identified as malware. However, the unsigned installer produced T1055 and LSASS-related runtime signals plus direct-IP traffic whose host reputation was not checked, so it should not be trusted without source verification.
e631a3ae68be08d389…5faf7ffa4a0ddfRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy 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.
All 75 engines were non-detecting, including 17 tier-1 products, and no dropped child was identified as malware. However, the unsigned installer produced T1055 and LSASS-related runtime signals plus direct-IP traffic whose host reputation was not checked, so it should not be trusted without source verification.
Static detection evidence is favorable: 0 of 75 engines flagged the executable, and all 17 reporting tier-1 engines were non-detecting. One completed sandbox run nevertheless mapped activity to five offensive techniques, including T1055, and surfaced LSASS-related process activity. The file is unsigned, leaving no authenticated publisher identity to offset those runtime concerns. Ten dropped files were inspected without a malicious finding, but each child still has an unknown individual verdict. The observed IP address lacks a completed host-reputation cross-check, while imphash-only history is adverse but weak because none of the five matches shares a signer.
What We Detected
No antivirus product flagged the executable: 0 of 75 engines reported a detection, including 17 tier-1 engines. The installer is unsigned, and no publisher history is available. External research sources returned no matching malware reference or YARA rule.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1485, T1543.003, T1547.001, and T1548. A heuristic also associated process activity with LSASS, while the sample contacted 104.21.37.99 directly. These mappings are concerning but do not independently prove credential theft or command-and-control, and no sandbox issued a malicious verdict. Host reputation was not checked or saved for the observed IP, so no complete network-reputation conclusion is available.
What To Do Now
Verify that the file came from the software publisher's official release channel and compare its SHA-256 value, e631a3ae68be08d38914251897269beabf765e92d9c4ed35215faf7ffa4a0ddf, with a publisher-provided checksum. Keep endpoint protection enabled, and avoid installing it on a production system until the publisher and network destination are independently confirmed.
Where this verdict could be wrong5 caveats
- All 75 engines were non-detecting, including 17 tier-1 engines, which weighs strongly against a recognized malware family.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false after 10 children were inspected.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false, although absence of these references does not prove benignity.
- prevalence.uniqueSources=495 and prevalence.timesSubmitted=556 indicate broad recent circulation rather than an isolated sample.
- The five similar files share only imphash 88016fcdef7f227c62171d0afad9aae4 without signer co-match, so their adverse verdicts may reflect a common installer framework.
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 of 75 antivirus engines reported a detection
- All 17 reporting tier-1 engines were non-detecting
- No malicious sandbox verdict was recorded
- No malicious child was identified among 10 inspected dropped files
- No MalwareBazaar, CIRCL, or YARAify match was found
- Unsigned Win32 installer with no verified publisher identity
- Sandbox mapping to process injection technique T1055
- LSASS-related process activity surfaced by MalwareTips.Synth.CredentialDumper
- Five offensive technique mappings in one sandbox run
- Direct connection to 104.21.37.99 without a completed host-reputation check
- Recent first observation, only seven days old
Obtain a fresh copy from the publisher's official channel and verify its SHA-256 checksum before running it. Keep security protection enabled and use an isolated test environment if further execution is necessary.
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
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
- 18MITRE ATT&CK techniques
- 12spawned processes
- 1network contacts
- 38filesystem & 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: Created or modified a system service, which can keep code running.
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: 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.
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
RevivalSetup.exe
e631a3ae68be08d38914251897269beabf765e92d9c4ed35215faf7ffa4a0ddf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\RevivalSetup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-KOBJQ0IN0E.tmp\RevivalSetup.tmp" /SL5="$200EC,31585644,926208,C:\Users\<USER>\Desktop\RevivalSetup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
RevivalSetup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-KOBJQ0IN0E.tmp\RevivalSetup.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-XXQW01M1FD.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.37.99
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 104.21.37.99
- C:\Users\<USER>\AppData\Local\Temp\is-KOBJQ0IN0E.tmp\RevivalSetup.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-XXQW01M1FD.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_48.db
- C:\Users\<USER>\AppData\Local\Programs\Revival\is-MT6IBTTC3B.tmp
- C:\Users\<USER>\AppData\Local\Programs\Revival\is-8E2D2ZNNKF.tmp
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Revival\Revival.lnk
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Revival\Revival.pif
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Revival\Revival.url
- cversions.3.m
- \BaseNamedObjects\Local\SM0:6236:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:6236:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- da3f122d19f811a0ee68…fde700Never scannednever seen before
- b5ad794270351a5d8116…432d5fNever scannednever seen before
- d62c876da3b54eeba74a…27fab3Never scannednever seen before
- 5769285a081ae63fa14b…439001Never scannednever seen before
- 34dda42fb1fc5daee442…300cb3Never scannednever seen before
- ad11e361b5a47eac076c…2e5d20Never scannednever seen before
- bac32d147a25ee1b71f0…b3b6a9Never scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- b38c536fb55f0641cadb…e8e2caNever scannednever seen before
- df56731b92f6afe4720d…aba537Never 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
- 0 / 75engines flagged
- 495sources 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
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 556 times from 495 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: RevivalSetup.exe — e631a3ae68be08d38914251897269beabf765e92d9c4ed35215faf7ffa4a0ddf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\RevivalSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-KOBJQ0IN0E.tmp\RevivalSetup.tmp" /SL5="$200EC,31585644,926208,C:\Users\<USER>\Desktop\RevivalSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: RevivalSetup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-KOBJQ0IN0E.tmp\RevivalSetup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-XXQW01M1FD.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.21.37.99 — 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\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.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.
Evidence104.21.37.99
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- RevivalSetup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 31.4 MB
- Last analyzed
- Sep 23, 2026, 4:07 PM UTC
e631a3ae68be08d38914251897269beabf765e92d9c4ed35215faf7ffa4a0ddfSafety & 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 run 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. Get a fresh copy 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 RevivalSetup.exe safe, or is it malware?
What is RevivalSetup.exe?
How many antivirus engines detected RevivalSetup.exe?
I already downloaded and ran RevivalSetup.exe — what should I do?
How do I remove RevivalSetup.exe?
What is the SHA-256 hash of RevivalSetup.exe?
How up to date is this analysis of RevivalSetup.exe?
Community
Member reviews and reports for this exact file hash.