GridinSoft Threat Intelligence

AvastBrowser.exe file report

Under review File reputation report
MD5 fab682ce8f4fcfc200107d7db4bd02bd
Latest seen 2021-01-12 00:00:14 (5 years ago)
First seen 2021-01-11 23:46:19 (5 years ago)
Size 1 MB
Publisher AVAST Software

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-11 23:46:19 (5 years ago); latest analysis 2021-01-12 00:00:14 (5 years ago).

Publisher context

Company metadata: AVAST Software. Product metadata: Avast Secure Browser.

Digital signature

Signed by Avast Software s.r.o.. The signature is reported as valid, but signed files can still be bundled or abused.

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.

AvastBrowser.exe is a Windows file recorded in the ThreatInfo database. It is associated with Avast Secure Browser. The reported company name is AVAST Software. The current detection status is Undefined, based on the latest analysis from 2021-01-12 00:00:14 (5 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: Avast Secure Browser
Company Name: AVAST Software
MD5: fab682ce8f4fcfc200107d7db4bd02bd
Size: 1 MB
First Published: 2021-01-11 23:46:19 (5 years ago)
Latest Published: 2021-01-12 00:00:14 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-12 00:00:14 (5 years ago)
Signed By: Avast Software s.r.o.
Status: Valid

The signature on AvastBrowser.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.

Windows 10 100.0%

The most common operating system signal for AvastBrowser.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.

AvastBrowser.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 0x00110360
Image base 0x00400000

PE Sections:

Sections 9
Raw data 1950720

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

.text 1291264 bytes · 66.2% of section data
MD5 448f9fd4ff462b1a386bc0a641db664b
.rdata 344576 bytes · 17.7% of section data
MD5 f7c0c3335ad50d53a9e03f304f6f0bab
.data 164864 bytes · 8.5% of section data
MD5 8e9dd5067e56630e776bb7ff8510071c
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 c1334aff67b7779c0dd21984e88796fa
.tls 512 bytes · 0.0% of section data
MD5 27942a65eef7d96696f345e88a4ce24b
.voltbl 512 bytes · 0.0% of section data
Uncommon name
MD5 8c0958215619ebb8ff6d0dff557082e5
CPADinfo 512 bytes · 0.0% of section data
Uncommon name
MD5 842689af09e7bf563672a4b43f1a2286
.rsrc 98304 bytes · 5.0% of section data
MD5 b680383f514a89f2294d90fabc61e9a3
.reloc 49664 bytes · 2.5% of section data
MD5 b7c5ba5a7821d829bbbcc55875cc947d

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 fab682ce8f4fcfc200107d7db4bd02bd.
  • 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.