GridinSoft Threat Intelligence

QBSafe.dll file report

Under review File reputation report
MD5 8150c608375e4ba7bf83c0c3c9638e52
Latest seen 2021-10-12 20:33:17 (4 years ago)
First seen 2017-05-26 09:05:35 (9 years ago)
Size 351 KB
Publisher Tencent Inc.
Product QQ浏览器

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-26 09:05:35 (9 years ago); latest analysis 2021-10-12 20:33:17 (4 years ago).

Publisher context

Company metadata: Tencent Inc.. Product metadata: QQ浏览器.

Digital signature

Signed by Tencent Technology(Shenzhen) Company Limited. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

QBSafe.dll is a Windows file recorded in the ThreatInfo database. It is associated with QQ浏览器. The reported company name is Tencent Inc.. The current detection status is Undefined, based on the latest analysis from 2021-10-12 20:33:17 (4 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: QQ浏览器
Company Name: Tencent Inc.
MD5: 8150c608375e4ba7bf83c0c3c9638e52
Size: 351 KB
First Published: 2017-05-26 09:05:35 (9 years ago)
Latest Published: 2021-10-12 20:33:17 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-10-12 20:33:17 (4 years ago)

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

%sysdrive%\system volume information\_restore{f14a1c2c-a641-43f9-a293-b0cb265a4677}\rp1244
%localappdata%\tencent\qqbrowser\user data\moduledll\{0508df1f-2ab6-4fac-a99e-45bbbf24e1e6}\9.0.0.8
%system%\config\systemprofile\appdata\local\tencent\qqbrowser\user data\moduledll\{0508df1f-2ab6-4fac-a99e-45bbbf24e1e6}
%localappdata%\tencent\qqbrowser\user data\moduledll\{0508df1f-2ab6-4fac-a99e-45bbbf24e1e6}
%sysdrive%\adwcleaner\quarantine\files\bzwajyrohsclzbhozthzkoqptqntfyph\qqbrowser\user data\moduledll\{0508df1f-2ab6-4fac-a99e-45bbbf24e1e6}
%programfiles%\tencent

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

A0428014.dll QBSafe.dll

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 10 68.1%
Windows 7 27.7%
Windows Server 2012 R2 2.1%
Windows XP 1.1%
Windows 8.1 1.1%

The most common operating system signal for QBSafe.dll is Windows 10 with 68.1% 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.

QBSafe.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 0x0001ddb2
Image base 0x61bc0000

PE Sections:

Sections 6
Raw data 350720

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

.text 233984 bytes · 66.7% of section data
MD5 e611be6c31008b5cb7c0725dcf19b9bb
.rdata 88576 bytes · 25.3% of section data
MD5 880204422cffedabbabe49b576b6c482
.data 10752 bytes · 3.1% of section data
MD5 9fc3bba0592da5533571c99938a4249c
.shared 512 bytes · 0.1% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 bytes · 0.4% of section data
MD5 1daedae3713852b559cfc1aa59a7cee7
.reloc 15360 bytes · 4.4% of section data
MD5 56c70a26ef4a13d702ce86644d48e190

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 8150c608375e4ba7bf83c0c3c9638e52.
  • 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.