ReviverSoftSmartMonitor.exe file report

MD5 04e6fd172668eb0cadffd07c5eb61a55
Latest seen 2023-09-14 23:20:45 (2 years ago)
First seen 2019-08-21 04:07:12 (6 years ago)
Size 5 MB
Publisher Corel Corporation
Product Smart Monitor
Signed by Corel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-08-21 04:07:12 (6 years ago); latest analysis 2023-09-14 23:20:45 (2 years ago).

Publisher context

Company metadata: Corel Corporation. Product metadata: Smart Monitor.

Digital signature

Signed by Corel Corporation. The signature is reported as valid, but signed files can still be bundled or abused.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

ReviverSoftSmartMonitor.exe is a Windows file recorded in the ThreatInfo database. It is associated with Smart Monitor. The reported company name is Corel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-09-14 23:20:45 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Smart Monitor
Company Name: Corel Corporation
MD5: 04e6fd172668eb0cadffd07c5eb61a55
Size: 5 MB
First Published: 2019-08-21 04:07:12 (6 years ago)
Latest Published: 2023-09-14 23:20:45 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-09-14 23:20:45 (2 years ago)
Signed By: Corel Corporation
Status: Valid

The signature on ReviverSoftSmartMonitor.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft
%programfiles%\reviversoft

ThreatInfo has observed ReviverSoftSmartMonitor.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

23.7%
10.5%
7.9%
7.9%
7.9%
7.9%
5.3%
5.3%
2.6%
2.6%
2.6%
2.6%
2.6%
2.6%
2.6%
2.6%
2.6%

The strongest geographic signal for this file is Germany with 23.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 84.6%
Windows 7 12.8%
Windows 8.1 2.6%

The most common operating system signal for ReviverSoftSmartMonitor.exe is Windows 10 with 84.6% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

ReviverSoftSmartMonitor.exe is identified as pe for 64 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x001f5774

PE Sections:

Name Size of data MD5
.text 4040192 67ea5ebaebf45e9df7c24a5d150cfc15
.rdata 889344 b30abc402bfcd11e349eed0d9ad25656
.data 166400 87bf22ed8bc31c5e9eb0dd928f5f608c
.pdata 124928 14c7c2aac9dca97ac1a4713d7b1ff176
.rsrc 131072 9605e1f11851ac91b705eb9c7b534a66
.reloc 20480 05baa8e96e6cec3705053590fe8f79ea

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

More information: