GridinSoft Threat Intelligence

QQSysMonX64.sys file report

Under review File reputation report
MD5 4d9cb0de4e7bb4551580cd48c057fba6
Latest seen 2021-03-01 04:27:32 (5 years ago)
First seen 2020-04-30 11:01:08 (6 years ago)
Size 128 KB
Publisher PC Manager
Product QQSYSMON
Signed by Tencent Technology(Shenzhen) Company Limited

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 2020-04-30 11:01:08 (6 years ago); latest analysis 2021-03-01 04:27:32 (5 years ago).

Publisher context

Company metadata: PC Manager. Product metadata: QQSYSMON.

Digital signature

Signed by Tencent Technology(Shenzhen) Company Limited. 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

QQSysMonX64.sys is a Windows file recorded in the ThreatInfo database. It is associated with QQSYSMON. The reported company name is PC Manager. The current detection status is Undefined, based on the latest analysis from 2021-03-01 04:27:32 (5 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: QQSYSMON
Company Name: PC Manager
MD5: 4d9cb0de4e7bb4551580cd48c057fba6
Size: 128 KB
First Published: 2020-04-30 11:01:08 (6 years ago)
Latest Published: 2021-03-01 04:27:32 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-01 04:27:32 (5 years ago)

Overview

Signed By: Tencent Technology(Shenzhen) Company Limited
Status: Valid

The signature on QQSysMonX64.sys 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%\tencent\qqpcmgr

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

Top country Malaysia
Share 33.3%
Low High activity

The strongest geographic signal for this file is Malaysia with 33.3% 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 66.7%
Windows 7 33.3%

The most common operating system signal for QQSysMonX64.sys is Windows 10 with 66.7% 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

QQSysMonX64.sys is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x0001f3c8
Image base 0x0000000000010000

PE Sections:

Sections 7
Raw data 113152

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

.text 89088 bytes · 78.7% of section data
MD5 a7b52cb33754b0bf124474808d66ab21
.rdata 7680 bytes · 6.8% of section data
MD5 f87f5b7032fae6ad87f3bc3a01e9f4a8
.data 5632 bytes · 5.0% of section data
MD5 e3782099e96aa0265931477d2e51029e
.pdata 3072 bytes · 2.7% of section data
MD5 0242eb3700968ce91797025449b88c1b
INIT 6144 bytes · 5.4% of section data
Uncommon name
MD5 a7cc36f99f96ba66c8ac783bd64c4f0a
.rsrc 1024 bytes · 0.9% of section data
MD5 4ca772f0add85a5d7e3d2ba8f6e5c3f1
.reloc 512 bytes · 0.5% of section data
MD5 dbd522cfc692df98dda569ae0dcab94c

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 4d9cb0de4e7bb4551580cd48c057fba6.
  • 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.