GridinSoft Threat Intelligence

D4BB.exe file report

Clean record File reputation report
MD5 fa0edfa9899dfdebf1ab7e3e00bc66fa
Latest seen 2021-04-18 20:13:53 (5 years ago)
First seen 2021-04-15 20:47:57 (5 years ago)
Size 1 MB
Product Avira@Pr

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-04-15 20:47:57 (5 years ago); latest analysis 2021-04-18 20:13:53 (5 years ago).

Publisher context

Company metadata: Avira Operations GmbH & Co. KG4 FileDescriptionAvira<. Product metadata: Avira@Pr.

Digital signature

Signed by Avira Operations GmbH & Co. KG. 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.

D4BB.exe is a Windows file recorded in the ThreatInfo database. It is associated with Avira@Pr. The reported company name is Avira Operations GmbH & Co. KG4 FileDescriptionAvira<. The current detection status is Clean, based on the latest analysis from 2021-04-18 20:13:53 (5 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: Avira@Pr
Company Name: Avira Operations GmbH & Co. KG4 FileDescriptionAvira<
MD5: fa0edfa9899dfdebf1ab7e3e00bc66fa
Size: 1 MB
First Published: 2021-04-15 20:47:57 (5 years ago)
Latest Published: 2021-04-18 20:13:53 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-04-18 20:13:53 (5 years ago)
Signed By: Avira Operations GmbH & Co. KG
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.

%temp%

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

D4BB.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 0x000a2cea
Image base 0x00400000

.NET Info:

MVID: c92ac4f6-5ac5-437a-9ae1-610fe89df628
Typelib ID: 145c0181-f8c3-49da-82e4-9aabc929fde5

PE Sections:

Sections 3
Raw data 1507840

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

.text 658944 bytes · 43.7% of section data
MD5 7469b8ea9b29aaef606695b1e3d2f1f5
.rsrc 848384 bytes · 56.3% of section data
MD5 3485a8fc42dba5b935a2b99c45fc6537
.reloc 512 bytes · 0.0% of section data
MD5 27609532b4b767fff9a5aebdcebe553a

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