AxComponentsVCL_IObitDel.bpl file report

MD5 fb7cc348b6eb0cec62a97ebda411e50f
Latest seen 2021-01-15 11:07:51 (5 years ago)
First seen 2017-05-22 11:17:40 (8 years ago)
Size 3 MB
Publisher Auslogics

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:17:40 (8 years ago); latest analysis 2021-01-15 11:07:51 (5 years ago).

Publisher context

Company metadata: Auslogics. Product metadata: Components Package.

Digital signature

Signed by Auslogics Labs Pty Ltd. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

AxComponentsVCL_IObitDel.bpl is a Windows file recorded in the ThreatInfo database. It is associated with Components Package. The reported company name is Auslogics. The current detection status is Undefined, based on the latest analysis from 2021-01-15 11:07:51 (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: Components Package
Company Name: Auslogics
MD5: fb7cc348b6eb0cec62a97ebda411e50f
Size: 3 MB
First Published: 2017-05-22 11:17:40 (8 years ago)
Latest Published: 2021-01-15 11:07:51 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-15 11:07:51 (5 years ago)
Signed By: Auslogics Labs Pty Ltd
Status: Valid

The signature on AxComponentsVCL_IObitDel.bpl 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%\auslogics\driver updater
%programfiles%\auslogics\driver updater\app\driverupdater
%programfiles%\auslogics
%programfiles%\auslogics\driver updater\app
%programfiles%
%sysdrive%
%sysdrive%\download\auslogics driver updater v1.9.4 repack+portable by dodakaedr\auslogics driver updater v1.9.4 portable\app
%sysdrive%\adwcleaner\quarantine\gtxsl1c00g
%programfiles%\auslogics
%programfiles%\auslogics

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

AxComponentsVCL.bpl
AxComponentsVCL_IObitDel.bpl

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

31.0%
12.6%
10.3%
4.0%
2.9%
2.9%
2.9%
2.3%
2.3%
2.3%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.7%
1.1%
1.1%
1.1%
1.1%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%
0.6%

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

Windows 10 64.6%
Windows 7 24.6%
Windows 8.1 9.1%
Windows XP 1.1%
Windows 8 0.6%

The most common operating system signal for AxComponentsVCL_IObitDel.bpl is Windows 10 with 64.6% 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.

AxComponentsVCL_IObitDel.bpl 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: 0x50000000
Entry Address: 0x00152bb4

PE Sections:

Name Size of data MD5
.text 1379328 bef240c4e18f779acff411b89b0b2819
.itext 3072 d787920cec47988b75bf8436cc08c1f3
.data 5120 ecbd0db954bb388ed77bd63b0bae4a22
.bss 0 00000000000000000000000000000000
.idata 103936 969fafccfb8ff33eb355fa19cb27daa1
.didata 25600 72ab31a4a43b2f55a59d7bd967ad9359
.edata 811008 fe4284f8a6654a5820df2f8fb941ecf2
.rdata 512 459a8b8056e54976eb1868e02cb7cfb8
.reloc 146432 4409e627430ee952dcae9f891c44d089
.rsrc 1680896 1f913b30649eb7d96dde8c6f769cba31

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: