GridinSoft Threat Intelligence

avastclear.exe file report

Clean record File reputation report
MD5 e99acfb5786b246bdf86d9f322785092
Latest seen 2022-01-10 21:36:28 (4 years ago)
First seen 2022-01-10 21:36:28 (4 years ago)
Size 10 MB
Publisher AVAST Software

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-01-10 21:36:28 (4 years ago); latest analysis 2022-01-10 21:36:28 (4 years ago).

Publisher context

Company metadata: AVAST Software. Product metadata: Avast Antivirus .

Digital signature

Signed by AVAST Software s.r.o.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

avastclear.exe is a Windows file recorded in the ThreatInfo database. It is associated with Avast Antivirus . The reported company name is AVAST Software. The current detection status is Clean, based on the latest analysis from 2022-01-10 21:36:28 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Avast Antivirus
Company Name: AVAST Software
MD5: e99acfb5786b246bdf86d9f322785092
Size: 10 MB
First Published: 2022-01-10 21:36:28 (4 years ago)
Latest Published: 2022-01-10 21:36:28 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-01-10 21:36:28 (4 years ago)
Signed By: AVAST Software s.r.o.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%sysdrive%

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

Windows 10 100.0%

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

avastclear.exe is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0002df50
Image base 0x00400000

PE Sections:

Sections 6
Raw data 1244160

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 892928 bytes · 71.8% of section data
MD5 1256202e04b10a8a6217e155475c8d71
.rdata 232448 bytes · 18.7% of section data
MD5 556492cd7ccc8fa9906f2de4979a41ab
.data 17408 bytes · 1.4% of section data
MD5 630718adbc3345236ae8645e17a2ff81
.didat 1024 bytes · 0.1% of section data
Uncommon name
MD5 df100c0b620cecd906eb29c073399f6f
.rsrc 55808 bytes · 4.5% of section data
MD5 771e3b08ad2e0be246f4fbdf676af2c2
.reloc 44544 bytes · 3.6% of section data
MD5 375757855ff466145bd65cbee2dd198e

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.

Report conclusion

This hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with e99acfb5786b246bdf86d9f322785092.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.