GridinSoft Threat Intelligence

Qt5Core1.dll file report

Clean record File reputation report
MD5 ec22385d8e5c09e13ce85f5fcb733baa
Latest seen 2022-04-05 23:34:34 (4 years ago)
First seen 2022-04-05 23:34:34 (4 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-04-05 23:34:34 (4 years ago); latest analysis 2022-04-05 23:34:34 (4 years ago).

Digital signature

Signed by LG Electronics Inc.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

Qt5Core1.dll is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2022-04-05 23:34:34 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

MD5: ec22385d8e5c09e13ce85f5fcb733baa
Size: 2 MB
First Published: 2022-04-05 23:34:34 (4 years ago)
Latest Published: 2022-04-05 23:34:34 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-04-05 23:34:34 (4 years ago)
Signed By: LG Electronics Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%sysdrive%\cheetah-team

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

Qt5Core1.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 0x00f53000
Image base 0x00400000

PE Sections:

Sections 7
Raw data 2242560

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

146432 bytes · 6.5% of section data
Uncommon name
MD5 08f6fa5d37c1292ab5ea0729d554b842
.rsrc 254464 bytes · 11.3% of section data
MD5 f0ee80af506f0569580fb95be27d8e40
.idata 512 bytes · 0.0% of section data
Uncommon name
MD5 ff7278cddf94adc00ff7cb3d048057a7
512 bytes · 0.0% of section data
Uncommon name
MD5 08ef2c30f648a2a182207ec6b48ddeea
ezafqhmp 1831424 bytes · 81.7% of section data
Uncommon name
MD5 1b3e406b8a48c1e06aa4b0fc54c5caed
jduwsfvo 512 bytes · 0.0% of section data
Uncommon name
MD5 1c45038cb5a1b89a78463fe72bb0580a
.taggant 8704 bytes · 0.4% of section data
Uncommon name
MD5 48ace2f0952a8856469c011d1383612b

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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