GridinSoft Threat Intelligence

vcl140_IObitDel.bpl file report

Under review File reputation report
MD5 0067e35f7e182778f99c9e687fa03835
Latest seen 2024-07-30 23:07:10 (2 years ago)
First seen 2017-12-08 19:07:59 (8 years ago)
Size 2 MB
Publisher Embarcadero Technologies, Inc.
Product Borland Package Library

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-12-08 19:07:59 (8 years ago); latest analysis 2024-07-30 23:07:10 (2 years ago).

Publisher context

Company metadata: Embarcadero Technologies, Inc.. Product metadata: Borland Package Library.

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.

File context

vcl140_IObitDel.bpl is a Windows file recorded in the ThreatInfo database. It is associated with Borland Package Library. The reported company name is Embarcadero Technologies, Inc.. The current detection status is Undefined, based on the latest analysis from 2024-07-30 23:07:10 (2 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.

File Details

Product Name: Borland Package Library
Company Name: Embarcadero Technologies, Inc.
MD5: 0067e35f7e182778f99c9e687fa03835
Size: 2 MB
First Published: 2017-12-08 19:07:59 (8 years ago)
Latest Published: 2024-07-30 23:07:10 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-07-30 23:07:10 (2 years ago)

Common Places:

%programfiles%\baisvik
%sysdrive%\programme\baisvik

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

File Names:

3 observed names
vcl140.bpl vcl140_IObitDel_IObitDel_IObitDel.bpl vcl140_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.

Geographic signal

Observed country distribution

ThreatInfo has seen vcl140_IObitDel.bpl across 50 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 27.4%
Low High activity

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

OS Version:

Windows 10 62.4%
Windows 7 24.4%
Windows 8.1 10.6%
Windows XP 1.6%
Windows 8 0.9%

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

Analysis

vcl140_IObitDel.bpl 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 0x0017982c
Image base 0x501c0000

PE Sections:

Sections 10
Raw data 2445824

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

.text 1539584 bytes · 62.9% of section data
MD5 c01c26d034501cf54a2e156380ee90ab
.itext 2560 bytes · 0.1% of section data
Uncommon name
MD5 09412f61c620a6537711ece6550ad5b7
.data 9216 bytes · 0.4% of section data
MD5 eacdc6843fd4655d31dd4dc3008e64f4
.bss 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 63488 bytes · 2.6% of section data
MD5 9185c43d54661c76968e6f3bb0d6ce8b
.didata 1024 bytes · 0.0% of section data
Uncommon name
MD5 5fff76e96fc598f6d76d64cb2727419f
.edata 502272 bytes · 20.5% of section data
MD5 ef522be1f009bc8515a94b1ffe5fbfdf
.rdata 512 bytes · 0.0% of section data
MD5 64ae65d59f7f7a33c9e9cd4974b90c7d
.reloc 139776 bytes · 5.7% of section data
MD5 0a58cb29ba1ba3125a5f6834148a6341
.rsrc 187392 bytes · 7.7% of section data
MD5 34f0ba9e7b56bba617cd86c306a42bbe

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 0067e35f7e182778f99c9e687fa03835.
  • 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.