GridinSoft Threat Intelligence

qicns.dll file report

Under review File reputation report
MD5 84f6108effe203c4bf7edbeb0d83bd0f
Latest seen 2021-11-30 21:15:57 (4 years ago)
First seen 2017-05-21 15:02:46 (9 years ago)
Size 30 KB
Product Qt5

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 15:02:46 (9 years ago); latest analysis 2021-11-30 21:15:57 (4 years ago).

Publisher context

Company metadata: Digia Plc and/or its subsidiary(-ies). Product metadata: Qt5.

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.

qicns.dll is a Windows file recorded in the ThreatInfo database. It is associated with Qt5. The reported company name is Digia Plc and/or its subsidiary(-ies). The current detection status is Undefined, based on the latest analysis from 2021-11-30 21:15:57 (4 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: Qt5
Company Name: Digia Plc and/or its subsidiary(-ies)
MD5: 84f6108effe203c4bf7edbeb0d83bd0f
Size: 30 KB
First Published: 2017-05-21 15:02:46 (9 years ago)
Latest Published: 2021-11-30 21:15:57 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-30 21:15:57 (4 years ago)
%localappdata%\vghd\bin\imageformats
%localappdata%\vghd\bin
%profile%\dmin\local settings\application data\vghd\bin

ThreatInfo has observed qicns.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 68.5%
Windows 7 16.8%
Windows 8.1 9.7%
Windows 8 4.0%
Windows XP 0.7%
Windows Vista 0.3%

The most common operating system signal for qicns.dll is Windows 10 with 68.5% 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.

qicns.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 0x0000484f
Image base 0x10000000

PE Sections:

Sections 6
Raw data 30208

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

.text 16384 bytes · 54.2% of section data
MD5 d04ff70643776079472f3efa76bec0f4
.rdata 9216 bytes · 30.5% of section data
MD5 add42caa430b837d8d763d9bd1d68a4e
.data 1536 bytes · 5.1% of section data
MD5 87b1f97dea36dd18cb8861a42884e127
.qtmetad 512 bytes · 1.7% of section data
Uncommon name
MD5 f1cdc57663ab75e90aad05e0303b34de
.rsrc 1024 bytes · 3.4% of section data
MD5 27a14c0ff108ee12ff5abe9f2bda2fc5
.reloc 1536 bytes · 5.1% of section data
MD5 07cea9990ed7eca57d04c2413a9bfdde

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 84f6108effe203c4bf7edbeb0d83bd0f.
  • 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.