GridinSoft Threat Intelligence

xmlrtl70.bpl file report

Under review File reputation report
MD5 c3bad88734a93db4c9ba822e492c6e76
Latest seen 2023-06-06 23:32:40 (2 years ago)
First seen 2018-07-30 10:15:50 (7 years ago)
Size 833 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-07-30 10:15:50 (7 years ago); latest analysis 2023-06-06 23:32:40 (2 years ago).

Publisher context

Company metadata: Borland Software Corporation. Product metadata: Borland Package Library.

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.

xmlrtl70.bpl is a Windows file recorded in the ThreatInfo database. It is associated with Borland Package Library. The reported company name is Borland Software Corporation. The current detection status is Undefined, based on the latest analysis from 2023-06-06 23:32:40 (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.

Product Name: Borland Package Library
Company Name: Borland Software Corporation
MD5: c3bad88734a93db4c9ba822e492c6e76
Size: 833 KB
First Published: 2018-07-30 10:15:50 (7 years ago)
Latest Published: 2023-06-06 23:32:40 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-06-06 23:32:40 (2 years ago)
%programfiles%
%programfiles%\amazing

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

Windows 10 100.0%

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

xmlrtl70.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 0x0008ff2c
Image base 0x40370000

PE Sections:

Sections 8
Raw data 852480

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

CODE 585728 bytes · 68.7% of section data
MD5 6bb5d259eb2d7691aa6b267cb2f53de5
DATA 2048 bytes · 0.2% of section data
MD5 73de916446b5c0792df7d507e4c64640
BSS 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 16896 bytes · 2.0% of section data
MD5 4347517c465f40f7ae9a792f0a3d4f0c
.edata 194560 bytes · 22.8% of section data
MD5 bc10dff61416db4bd7d669f80ab3665a
.rdata 512 bytes · 0.1% of section data
MD5 28775baafe952f7d7b7923ea814b53e3
.reloc 45568 bytes · 5.3% of section data
MD5 3103e6a3e7f52ae372a98d1d092ea1d5
.rsrc 7168 bytes · 0.8% of section data
MD5 fe8fb739a3ed10f7a7545384369f604e

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