GridinSoft Threat Intelligence

yhregd.dll.locale file report

Under review File reputation report
MD5 bf04aa0738d5d7d89b2c8f92074fda45
Latest seen 2023-02-06 23:28:44 (3 years ago)
First seen 2017-05-31 04:06:16 (8 years ago)
Size 10 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-31 04:06:16 (8 years ago); latest analysis 2023-02-06 23:28:44 (3 years ago).

Publisher context

Company metadata: Qihu 360 Software Co., Ltd.. Product metadata: 360 Total Security.

Digital signature

Signed by QIHU 360 SOFTWARE CO. LIMITED. 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.

yhregd.dll.locale is a Windows file recorded in the ThreatInfo database. It is associated with 360 Total Security. The reported company name is Qihu 360 Software Co., Ltd.. The current detection status is Undefined, based on the latest analysis from 2023-02-06 23:28:44 (3 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: 360 Total Security
Company Name: Qihu 360 Software Co., Ltd.
MD5: bf04aa0738d5d7d89b2c8f92074fda45
Size: 10 KB
First Published: 2017-05-31 04:06:16 (8 years ago)
Latest Published: 2023-02-06 23:28:44 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-02-06 23:28:44 (3 years ago)
Signed By: QIHU 360 SOFTWARE CO. LIMITED
Status: Valid

The signature on yhregd.dll.locale 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.

%programfiles%\psafe\total\i18n\en\ipc
%programfiles%\psafe\total\i18n\en

ThreatInfo has observed yhregd.dll.locale 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 7 88.0%
Windows 10 8.0%
Windows 8.1 4.0%

The most common operating system signal for yhregd.dll.locale is Windows 7 with 88.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.

yhregd.dll.locale 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
Image base

PE Sections:

Sections 2
Raw data 3072

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

.rdata 512 bytes · 16.7% of section data
MD5 730f09f573351281dd2e1f80c9068db6
.rsrc 2560 bytes · 83.3% of section data
MD5 a194bce7f27da86cb089debd63a19add

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