GridinSoft Threat Intelligence
360Base.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-05-21 06:06:19 (9 years ago); latest analysis 2026-05-09 23:01:15 (2 weeks ago).
Signed by Qihoo 360 Software (Beijing) Company Limited. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
360Base.dll is a Windows file recorded in the ThreatInfo database. It is associated with 360安全卫士. The reported company name is 360.cn. The current detection status is Undefined, based on the latest analysis from 2026-05-09 23:01:15 (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.
File Details
| Product Name: | 360安全卫士 |
| Company Name: | 360.cn |
| MD5: | a73cf0457df35fab74ef3393d2766667 |
| Size: | 900 KB |
| First Published: | 2017-05-21 06:06:19 (9 years ago) |
| Latest Published: | 2026-05-09 23:01:15 (2 weeks ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2026-05-09 23:01:15 (2 weeks ago) |
Overview
| Signed By: | Qihoo 360 Software (Beijing) Company Limited |
| Status: | Valid |
The signature on 360Base.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.
Common Places:
| %appdata%\360se6\application\8.1.1.256\360bdoctorext |
| %appdata%\360se6\application\9.1.0.318 |
| %appdata%\360se6\application\9.2.0.106 |
| %appdata%\360se6\application\9.1.0.338 |
| %appdata%\360se6\application\9.1.0.350 |
| %appdata%\360se6\application\9.1.0.346 |
| %appdata%\360se6\application\9.1.0.348 |
| %appdata%\360se6\application\9.1.0.356 |
| %appdata%\360se6\application\9.1.0.354 |
| %appdata%\360se6\application\9.1.0.352 |
ThreatInfo has observed 360Base.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.
Geographic signal
Observed country distribution
ThreatInfo has seen 360Base.dll across 27 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is China with 46.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for 360Base.dll is Windows 10 with 64.6% 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
360Base.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
368f052f50ad9b9f1ec5dfc1a93a6e1a
7ac2c4daa670366370cbdcfffb662b4f
43bfcfe9de499a09a619f5c64a234555
2d3a7193c7151217b5f58300ba883b2f
ab663a6c40b48ea44815392d159e5809
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.