MD5 eb2773d4f7ca6f760acf4a2ed8927c85
Latest seen 2023-01-16 23:05:52 (3 years ago)
First seen 2022-06-12 23:15:42 (3 years ago)
Size 219 KB
Publisher 电脑管家
Product QQSYSMON
Signed by Tencent Technology(Shenzhen) Company Limited;Microsoft Windows Hardware Compatibility Publisher

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-06-12 23:15:42 (3 years ago); latest analysis 2023-01-16 23:05:52 (3 years ago).

Publisher context

Company metadata: 电脑管家. Product metadata: QQSYSMON.

Digital signature

Signed by Tencent Technology(Shenzhen) Company Limited;Microsoft Windows Hardware Compatibility Publisher. 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

404D.tmp is a Windows file recorded in the ThreatInfo database. It is associated with QQSYSMON. The reported company name is 电脑管家. The current detection status is Undefined, based on the latest analysis from 2023-01-16 23:05:52 (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: QQSYSMON
Company Name: 电脑管家
MD5: eb2773d4f7ca6f760acf4a2ed8927c85
Size: 219 KB
First Published: 2022-06-12 23:15:42 (3 years ago)
Latest Published: 2023-01-16 23:05:52 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-01-16 23:05:52 (3 years ago)

Overview

Signed By: Tencent Technology(Shenzhen) Company Limited;Microsoft Windows Hardware Compatibility Publisher
Status: Valid

The signature on 404D.tmp 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
%sysdrive%\qqpcmgr

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

Top country Malaysia
Share 50.0%
Low High activity

The strongest geographic signal for this file is Malaysia with 50.0% 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 404D.tmp 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

404D.tmp 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 0x000373c8
Image base 0x0000000000010000

PE Sections:

Sections 8
Raw data 198144

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

.text 162816 bytes · 82.2% of section data
MD5 9997cd0bd26c308d414023c9f6131171
.rdata 12288 bytes · 6.2% of section data
MD5 12ba1e15dc7d46ee6118e589fd24ff8a
.data 7168 bytes · 3.6% of section data
MD5 2506d54d43ee83e124b5a2bcca464306
.pdata 5120 bytes · 2.6% of section data
MD5 51a3ba278513d937c17835f9f13899df
PAGE 1024 bytes · 0.5% of section data
Uncommon name
MD5 efc296e76a92fd1a512354f763708eee
INIT 7680 bytes · 3.9% of section data
Uncommon name
MD5 7f4da62e0bffacfc623d583ddb6ab125
.rsrc 1024 bytes · 0.5% of section data
MD5 07395d77e2c0c41640bd6b208cd15d3b
.reloc 1024 bytes · 0.5% of section data
MD5 733cb5515df43dc40fb09b1269c4d03f

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