GridinSoft Threat Intelligence

GTCDOM.dll file report

Under review File reputation report
MD5 dba896302d1f5660f072035aa403a55d
Latest seen 2024-01-01 23:20:53 (2 years ago)
First seen 2024-01-01 23:02:02 (2 years ago)
Size 112 KB
Publisher Graitec
Product AdvanceSteel
Signed by GRAITEC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-01-01 23:02:02 (2 years ago); latest analysis 2024-01-01 23:20:53 (2 years ago).

Publisher context

Company metadata: Graitec. Product metadata: AdvanceSteel.

Digital signature

Signed by GRAITEC. 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.

GTCDOM.dll is a Windows file recorded in the ThreatInfo database. It is associated with AdvanceSteel. The reported company name is Graitec. The current detection status is Undefined, based on the latest analysis from 2024-01-01 23:20:53 (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: AdvanceSteel
Company Name: Graitec
MD5: dba896302d1f5660f072035aa403a55d
Size: 112 KB
First Published: 2024-01-01 23:02:02 (2 years ago)
Latest Published: 2024-01-01 23:20:53 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-01 23:20:53 (2 years ago)
Signed By: GRAITEC
Status: Valid

The signature on GTCDOM.dll 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.

%commondir%

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

Windows 10 100.0%

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

GTCDOM.dll 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 0x0000a855
Image base 0x10000000

PE Sections:

Sections 5
Raw data 106496

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

.text 49152 bytes · 46.2% of section data
MD5 ca1b9c35fe0da5f665753a387dee17e1
.rdata 36864 bytes · 34.6% of section data
MD5 fb8f5611fd3067514c7ee22abd0efe70
.data 4096 bytes · 3.8% of section data
MD5 fe7be53a74497a7175b8fea0bb52cc9a
.rsrc 8192 bytes · 7.7% of section data
MD5 c9c0c00b1dfbbe8dc82c7b2d3933de86
.reloc 8192 bytes · 7.7% of section data
MD5 1e4916612cfd1ebe1bc75c0912c96464

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