DriverBooster.exe file report

MD5 85b4033add3c9b900c38331b63c21fc5
Latest seen 2021-04-25 20:09:30 (5 years ago)
First seen 2021-02-09 04:12:14 (5 years ago)
Size 6 MB
Publisher IObitHFi

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-02-09 04:12:14 (5 years ago); latest analysis 2021-04-25 20:09:30 (5 years ago).

Publisher context

Company metadata: IObitHFi. Product metadata: Driver Booster,ProductVer.

Digital signature

Signed by IObit Information Technology. 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.

DriverBooster.exe is a Windows file recorded in the ThreatInfo database. It is associated with Driver Booster,ProductVer. The reported company name is IObitHFi. The current detection status is Undefined, based on the latest analysis from 2021-04-25 20:09:30 (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: Driver Booster,ProductVer
Company Name: IObitHFi
MD5: 85b4033add3c9b900c38331b63c21fc5
Size: 6 MB
First Published: 2021-02-09 04:12:14 (5 years ago)
Latest Published: 2021-04-25 20:09:30 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-04-25 20:09:30 (5 years ago)
Signed By: IObit Information Technology
Status: Valid

The signature on DriverBooster.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%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster
%programfiles%\iobit\driver booster

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

71.4%
28.6%

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

Windows 10 100.0%

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

DriverBooster.exe is identified as pe for 32 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: 32
Image Base: 0x00400000
Entry Address: 0x0035a5e4

PE Sections:

Name Size of data MD5
.text 3500544 8b487d8697d2d9747a20ebba94e93f70
.itext 10240 419f2711aeef16b1c2a4746c5e100c49
.data 132096 a2b6da4bd4f8d9b94025806c600d691a
.bss 0 d41d8cd98f00b204e9800998ecf8427e
.idata 128512 ed2f1d29903a6d8a8326b28de852dfdc
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 833c6ee55230ea478f0a3b2c9bdbaa3a
.rsrc 3442176 18f10991d376af05e606f35a0b0c566c

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: