GridinSoft Threat Intelligence

sesvc.exe file report

Under review File reputation report
MD5 09eca1daf8af1c7d14b073a56934805b
Latest seen 2026-03-29 23:01:20 (2 months ago)
First seen 2026-03-29 23:01:19 (2 months ago)
Size 5 MB
Publisher 360.cn

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-03-29 23:01:19 (2 months ago); latest analysis 2026-03-29 23:01:20 (2 months ago).

Publisher context

Company metadata: 360.cn. Product metadata: 360安全浏览器 服务组件.

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.

sesvc.exe 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-03-29 23:01:20 (2 months 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安全浏览器 服务组件
Company Name: 360.cn
MD5: 09eca1daf8af1c7d14b073a56934805b
Size: 5 MB
First Published: 2026-03-29 23:01:19 (2 months ago)
Latest Published: 2026-03-29 23:01:20 (2 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-03-29 23:01:20 (2 months ago)
Signed By: Beijing Qihu Technology Co., Ltd.
Status: Valid

The signature on sesvc.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\components
%appdata%\360se6\application

ThreatInfo has observed sesvc.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 sesvc.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.

sesvc.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 0x0012b87f
Image base 0x00400000

PE Sections:

Sections 4
Raw data 6236672

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

.text 1463296 bytes · 23.5% of section data
MD5 f3c34fd8c540e064c8c4962ad5829881
.rdata 352256 bytes · 5.6% of section data
MD5 8103af047ef84b99871e0415ee4c05da
.data 48128 bytes · 0.8% of section data
MD5 2992fd020822a431a4c590acb7d938e4
.rsrc 4372992 bytes · 70.1% of section data
MD5 154a9802248ff60738ac4c25e323c86d

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 09eca1daf8af1c7d14b073a56934805b.
  • 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.