REI_AVIRA.exe file report

MD5 c6b2eba34ba556d56101b22923f4141b
Latest seen 2025-05-20 23:05:28 (a year ago)
First seen 2020-10-16 06:40:36 (5 years ago)
Size 1 MB
Publisher Reimage
Product Reimage
Signed by Reimage Ltd.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-16 06:40:36 (5 years ago); latest analysis 2025-05-20 23:05:28 (a year ago).

Publisher context

Company metadata: Reimage. Product metadata: Reimage.

Digital signature

Signed by Reimage Ltd.. 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.

REI_AVIRA.exe is a Windows file recorded in the ThreatInfo database. It is associated with Reimage. The reported company name is Reimage. The current detection status is Undefined, based on the latest analysis from 2025-05-20 23:05:28 (a year 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: Reimage
Company Name: Reimage
MD5: c6b2eba34ba556d56101b22923f4141b
Size: 1 MB
First Published: 2020-10-16 06:40:36 (5 years ago)
Latest Published: 2025-05-20 23:05:28 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-20 23:05:28 (a year ago)
Signed By: Reimage Ltd.
Status: Valid

The signature on REI_AVIRA.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%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage
%programfiles%\reimage

ThreatInfo has observed REI_AVIRA.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.

12.7%
9.3%
9.3%
6.7%
4.7%
2.7%
2.7%
2.7%
2.7%
2.7%
2.7%
2.0%
2.0%
2.0%
2.0%
2.0%
2.0%
2.0%
2.0%
2.0%
1.3%
1.3%
1.3%
1.3%
1.3%
1.3%
1.3%
1.3%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%
0.7%

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

Windows 10 69.9%
Windows 7 20.2%
Windows 8.1 5.5%
Windows 8 1.8%
Windows Server 2012 R2 1.8%
Windows Server 2008 R2 0.6%

The most common operating system signal for REI_AVIRA.exe is Windows 10 with 69.9% 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.

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

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x0013734b

PE Sections:

Name Size of data MD5
.text 1459712 c6f38b85a8955b12b92a83f6aec2322a
.rdata 314368 d0a80b57c5c56d11cfa009de6d5ab4e2
.data 20992 6c2777d13b0f72399928f7d03690f3c2
.rsrc 1536 e48446317a3646c1e2d7c6175ff45c9c
.reloc 132608 0bf978576682bcf8897124095f28c84f

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: