GridinSoft Threat Intelligence

360bdoctor.exe file report

Under review File reputation report
MD5 de2bee9090c1e18da36b1cc9c70f82ca
Latest seen 2026-05-09 23:01:10 (2 weeks ago)
First seen 2025-11-26 23:01:26 (6 months ago)
Size 2 MB
Publisher 360.cn

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-11-26 23:01:26 (6 months ago); latest analysis 2026-05-09 23:01:10 (2 weeks ago).

Publisher context

Company metadata: 360.cn. Product metadata: 360BDoctor Module.

Digital signature

Signed by Beijing Qihu 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.

360bdoctor.exe is a Windows file recorded in the ThreatInfo database. It is associated with 360BDoctor Module. The reported company name is 360.cn. The current detection status is Undefined, based on the latest analysis from 2026-05-09 23:01:10 (2 weeks 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: 360BDoctor Module
Company Name: 360.cn
MD5: de2bee9090c1e18da36b1cc9c70f82ca
Size: 2 MB
First Published: 2025-11-26 23:01:26 (6 months ago)
Latest Published: 2026-05-09 23:01:10 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-05-09 23:01:10 (2 weeks ago)
Signed By: Beijing Qihu Technology Co., Ltd.
Status: Valid

The signature on 360bdoctor.exe 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.

%appdata%\360se6\application

ThreatInfo has observed 360bdoctor.exe 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 360bdoctor.exe 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.

360bdoctor.exe 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 0x000d0434
Image base 0x00400000

PE Sections:

Sections 5
Raw data 2216960

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

.text 1124864 bytes · 50.7% of section data
MD5 91986f43b2c083ea2e1fd234d5b1aaa3
.rdata 230400 bytes · 10.4% of section data
MD5 0282ef930188cf8e19e780a1a51fbbe6
.data 52224 bytes · 2.4% of section data
MD5 7ab236d2ffa4bada395ff822742c8d01
.rsrc 720384 bytes · 32.5% of section data
MD5 8f31360ba3402dc8f63c00e95655c8bd
.reloc 89088 bytes · 4.0% of section data
MD5 38564516bdeaca663262998b047f823f

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