GridinSoft Threat Intelligence
safe505.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-07-25 08:12:56 (8 years ago); latest analysis 2026-05-09 23:01:13 (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
safe505.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:13 (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: | 631c46619d31f985225c68a4fa2770de |
| Size: | 223 KB |
| First Published: | 2017-07-25 08:12:56 (8 years ago) |
| Latest Published: | 2026-05-09 23:01:13 (2 weeks ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2026-05-09 23:01:13 (2 weeks ago) |
Overview
| Signed By: | Qihoo 360 Software (Beijing) Company Limited |
| Status: | Valid |
The signature on safe505.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.406 |
| %appdata%\360se6\application\9.2.0.106 |
| %appdata%\360se6\application\9.1.0.338 |
| %appdata%\360se6\application\8.1.1.258 |
| %appdata%\360se6\user data\v3update\download |
| %appdata%\360se6\application\9.1.0.350 |
| %appdata%\360se6\application\8.1.1.248 |
| %appdata%\360se6\application\9.1.0.348 |
| %appdata%\360se6\application\9.1.0.346 |
| %localappdata%\360chrome\chrome\application\8.7.0.306 |
ThreatInfo has observed safe505.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 safe505.dll across 29 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 45.3% 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 safe505.dll is Windows 10 with 60.5% 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
safe505.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.
cf78e61ad199c6c38af01903b0da3e55
fd5e96f9fee962f21ca78ccbf693f40d
3a8cca9c79cb5e5ae5c540a4ca460570
c9ea476fc3ed4f3a4065a8d5d2ffed29
73d2c14d3bbea3830da004288feacd74
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.