GridinSoft Threat Intelligence

QsShell.dll file report

Under review File reputation report
MD5 79e1af245170fa48b54e59554faf0fc7
Latest seen 2024-08-09 23:02:41 (2 years ago)
First seen 2024-08-09 23:02:41 (2 years ago)
Size 324 KB
Product QuickSee

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-08-09 23:02:41 (2 years ago); latest analysis 2024-08-09 23:02:41 (2 years ago).

Publisher context

Company metadata: 天津斐文网络科技有限公司. Product metadata: QuickSee.

Digital signature

Signed by 天津斐文网络科技有限公司. 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.

QsShell.dll is a Windows file recorded in the ThreatInfo database. It is associated with QuickSee. The reported company name is 天津斐文网络科技有限公司. The current detection status is Undefined, based on the latest analysis from 2024-08-09 23:02:41 (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: QuickSee
Company Name: 天津斐文网络科技有限公司
MD5: 79e1af245170fa48b54e59554faf0fc7
Size: 324 KB
First Published: 2024-08-09 23:02:41 (2 years ago)
Latest Published: 2024-08-09 23:02:41 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-09 23:02:41 (2 years ago)
Signed By: 天津斐文网络科技有限公司
Status: Valid

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

%programfiles%

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

QsShell.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 0x00014de3
Image base 0x10000000

PE Sections:

Sections 5
Raw data 315904

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

.text 198144 bytes · 62.7% of section data
MD5 681fb15e8ae52e151cd2595060d48f09
.rdata 88064 bytes · 27.9% of section data
MD5 f439d13b1cf73b0bdc22e4c2d4fd865b
.data 6656 bytes · 2.1% of section data
MD5 dcc7db9820cb328938a54ae66bad6ab8
.rsrc 8192 bytes · 2.6% of section data
MD5 6d4956c74e4d1866d1cef8dac8879c33
.reloc 14848 bytes · 4.7% of section data
MD5 ef089b015523d63d76058bd5638deae7

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 79e1af245170fa48b54e59554faf0fc7.
  • 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.