GridinSoft Threat Intelligence

ouc.exe file report

Clean record File reputation report
MD5 64d94f1ed2dcb199948f614367cd2636
Latest seen 2021-03-08 16:12:27 (5 years ago)
First seen 2018-08-15 01:07:53 (7 years ago)
Size 113 KB
Product ouc.exe

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-08-15 01:07:53 (7 years ago); latest analysis 2021-03-08 16:12:27 (5 years ago).

Publisher context

Company metadata: Huawei Technologies Co., Ltd.. Product metadata: ouc.exe.

Digital signature

Signed by HUAWEI Technologies Co., Ltd.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

ouc.exe is a Windows file recorded in the ThreatInfo database. It is associated with ouc.exe. The reported company name is Huawei Technologies Co., Ltd.. The current detection status is Clean, based on the latest analysis from 2021-03-08 16:12:27 (5 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: ouc.exe
Company Name: Huawei Technologies Co., Ltd.
MD5: 64d94f1ed2dcb199948f614367cd2636
Size: 113 KB
First Published: 2018-08-15 01:07:53 (7 years ago)
Latest Published: 2021-03-08 16:12:27 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-08 16:12:27 (5 years ago)
Signed By: HUAWEI Technologies Co., Ltd.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%appdata%
%programfiles%\blueconnect

ThreatInfo has observed ouc.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 7 83.3%
Windows 10 16.7%

The most common operating system signal for ouc.exe is Windows 7 with 83.3% 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.

ouc.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 0x00008fe3
Image base 0x00400000

PE Sections:

Sections 4
Raw data 106496

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

.text 81920 bytes · 76.9% of section data
MD5 bbeecf8860080c6845c3bc3a1a165d01
.rdata 16384 bytes · 15.4% of section data
MD5 ea60b29dacc092aa412c7209855e5032
.data 4096 bytes · 3.8% of section data
MD5 42709c16a69e80cf91061a79a6e60a46
.rsrc 4096 bytes · 3.8% of section data
MD5 4b92cf841d60aea88f21a9e5d1c89b93

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 64d94f1ed2dcb199948f614367cd2636.
  • 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.