GridinSoft Threat Intelligence

IDQBE32.DLL file report

Under review File reputation report
MD5 070e5886cf86c8ff00fe5e420517dccc
Latest seen 2021-02-16 16:13:18 (5 years ago)
First seen 2021-02-11 16:57:07 (5 years ago)
Size 412 KB
Publisher Inprise Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-02-11 16:57:07 (5 years ago); latest analysis 2021-02-16 16:13:18 (5 years ago).

Publisher context

Company metadata: Inprise Corporation.

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

IDQBE32.DLL is a Windows file recorded in the ThreatInfo database. The reported company name is Inprise Corporation. The current detection status is Undefined, based on the latest analysis from 2021-02-16 16:13:18 (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.

File Details

Company Name: Inprise Corporation
MD5: 070e5886cf86c8ff00fe5e420517dccc
Size: 412 KB
First Published: 2021-02-11 16:57:07 (5 years ago)
Latest Published: 2021-02-16 16:13:18 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-02-16 16:13:18 (5 years ago)

Common Places:

%programfiles%\borland\common files

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

Geographic signal

Observed country distribution

ThreatInfo has seen IDQBE32.DLL across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Canada
Share 50.0%
Low High activity

The strongest geographic signal for this file is Canada with 50.0% 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 100.0%

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

Analysis

IDQBE32.DLL is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x00001000
Image base 0x4c3e0000

PE Sections:

Sections 7
Raw data 420864

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

CODE 341504 bytes · 81.1% of section data
MD5 07e90e5f3606219ffbb1ba32f223798a
DATA 58880 bytes · 14.0% of section data
MD5 a3613123f603328afc0ce86ccfd50701
.INIT 3584 bytes · 0.9% of section data
Uncommon name
MD5 96e5edc64ed7f80fe32499cef3b215c9
.idata 2048 bytes · 0.5% of section data
MD5 133f993e79edc10310e902d7be822ddf
.edata 1536 bytes · 0.4% of section data
MD5 32d2b87481b4afea86c29c4aeee5b862
.reloc 12288 bytes · 2.9% of section data
MD5 72039ce6db5ef4b24efacadff0a54448
.rsrc 1024 bytes · 0.2% of section data
MD5 6b9d792c24cad93a2729b69d1c3fef35

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 070e5886cf86c8ff00fe5e420517dccc.
  • 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.