GridinSoft Threat Intelligence

qwindows.dll file report

Under review File reputation report
MD5 44e7891a257d61686ec933c43e2ffb7a
Latest seen 2023-01-14 23:52:29 (3 years ago)
First seen 2022-10-11 23:04:23 (3 years ago)
Size 1 MB
Publisher The Qt Company Ltd.
Product Qt5
Signed by J.onaxh Network Technology Co., Ltd.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2022-10-11 23:04:23 (3 years ago); latest analysis 2023-01-14 23:52:29 (3 years ago).

Publisher context

Company metadata: The Qt Company Ltd.. Product metadata: Qt5.

Digital signature

Signed by J.onaxh Network Technology Co., Ltd.. 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.

File context

qwindows.dll is a Windows file recorded in the ThreatInfo database. It is associated with Qt5. The reported company name is The Qt Company Ltd.. The current detection status is Undefined, based on the latest analysis from 2023-01-14 23:52:29 (3 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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

Product Name: Qt5
Company Name: The Qt Company Ltd.
MD5: 44e7891a257d61686ec933c43e2ffb7a
Size: 1 MB
First Published: 2022-10-11 23:04:23 (3 years ago)
Latest Published: 2023-01-14 23:52:29 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-01-14 23:52:29 (3 years ago)

Overview

Signed By: J.onaxh Network Technology Co., Ltd.
Status: Valid

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

Common Places:

%programfiles%\hylite
%sysdrive%\vpings
%sysdrive%\vpingsresources\vpings

ThreatInfo has observed qwindows.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 qwindows.dll across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Peru
Share 66.7%
Low High activity

The strongest geographic signal for this file is Peru with 66.7% 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 qwindows.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

qwindows.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 0x000b4427
Image base 0x10000000

PE Sections:

Sections 8
Raw data 1096192

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

.text 739328 bytes · 67.4% of section data
MD5 e23139d19ea8b1ee946d6b7b860c78cd
.rdata 308736 bytes · 28.2% of section data
MD5 59172cdbf35a44b54a8ed78be2ba2f76
.data 5632 bytes · 0.5% of section data
MD5 5c2acb006f443bed95eb8c0bdd152f87
.qtmetad 512 bytes · 0.0% of section data
Uncommon name
MD5 ffb6acbe9b4e6c28b7a2b4909df2286e
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 9d0ad8ae3745349ed887ecf7bcb42253
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
.rsrc 1024 bytes · 0.1% of section data
MD5 a4f4e66841fdf131934e822884880e44
.reloc 39936 bytes · 3.6% of section data
MD5 799cd1740d2155952622fb5ef0eecc76

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 44e7891a257d61686ec933c43e2ffb7a.
  • 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. Use the PUP category to compare similar reports.