GridinSoft Threat Intelligence

CefSharp.BrowserSubprocess.Core.dll file report

Under review File reputation report
MD5 9914bc8dce417236340a42c4e9a32d16
Latest seen 2021-01-07 13:12:18 (5 years ago)
First seen 2020-07-25 16:26:49 (5 years ago)
Size 802 KB
Product CefSharp

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-07-25 16:26:49 (5 years ago); latest analysis 2021-01-07 13:12:18 (5 years ago).

Publisher context

Product metadata: CefSharp.

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.

CefSharp.BrowserSubprocess.Core.dll is a Windows file recorded in the ThreatInfo database. It is associated with CefSharp. The current detection status is Undefined, based on the latest analysis from 2021-01-07 13:12:18 (5 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: CefSharp
MD5: 9914bc8dce417236340a42c4e9a32d16
Size: 802 KB
First Published: 2020-07-25 16:26:49 (5 years ago)
Latest Published: 2021-01-07 13:12:18 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 13:12:18 (5 years ago)
%appdata%\temp\sme2020\winroot\misa jsc\misa sme.net 2020\bin
%localappdata%
%appdata%\temp\misa.sme2019\winroot\misa jsc\misa sme.net 2020\bin

ThreatInfo has observed CefSharp.BrowserSubprocess.Core.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.

Windows 7 60.0%
Windows 10 40.0%

The most common operating system signal for CefSharp.BrowserSubprocess.Core.dll is Windows 7 with 60.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.

CefSharp.BrowserSubprocess.Core.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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00060ef4
Image base 0x10000000

.NET Info:

MVID: e21d2fd4-c032-4d7e-aac0-f05bc48fbc6f

PE Sections:

Sections 6
Raw data 820736

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

.text 429568 bytes · 52.3% of section data
MD5 62babda4ad407c621e7ef1191099e885
.rdata 354816 bytes · 43.2% of section data
MD5 bc0b5730f077688c483a7affa41bb433
.data 9216 bytes · 1.1% of section data
MD5 604ef28218ded3f1650e0934c2f17bd6
.gfids 512 bytes · 0.1% of section data
Uncommon name
MD5 47465fa2831bdad93e045d1db91ebd54
.rsrc 1536 bytes · 0.2% of section data
MD5 da23f230a71184bfe830bc63587424d3
.reloc 25088 bytes · 3.1% of section data
MD5 e95f7738173fcac052788dc6c27d205e

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 9914bc8dce417236340a42c4e9a32d16.
  • 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.