GridinSoft Threat Intelligence

CefSharp.Core.dll file report

Under review File reputation report
MD5 51f5c0221887a742b7a5761e292bcfeb
Latest seen 2021-01-07 12:32:32 (5 years ago)
First seen 2019-06-06 17:34:35 (6 years ago)
Size 1 MB
Product CefSharp

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-06-06 17:34:35 (6 years ago); latest analysis 2021-01-07 12:32:32 (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.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 12:32:32 (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: 51f5c0221887a742b7a5761e292bcfeb
Size: 1 MB
First Published: 2019-06-06 17:34:35 (6 years ago)
Latest Published: 2021-01-07 12:32:32 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-07 12:32:32 (5 years ago)
%appdata%
%appdata%\temp\sme2020\winroot\misa jsc\misa sme.net 2020\bin
%appdata%\temp\misa.sme2019\winroot\misa jsc\misa sme.net 2020\bin

ThreatInfo has observed CefSharp.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 10 66.7%
Windows 7 33.3%

The most common operating system signal for CefSharp.Core.dll is Windows 10 with 66.7% 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.Core.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00083c86
Image base 0x0000000180000000

.NET Info:

MVID: 07ce8d21-d45e-478f-b62c-b78080cd0d7c

PE Sections:

Sections 8
Raw data 1733120

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

.text 556544 bytes · 32.1% of section data
MD5 dff0fab7a148d5ef53ae135df60d5139
.nep 35840 bytes · 2.1% of section data
Uncommon name
MD5 12cfdd8261d6c0342af7f6d062a9d0ec
.rdata 1054720 bytes · 60.9% of section data
MD5 6bbdadd709e37733a4674bfca0e7d341
.data 48128 bytes · 2.8% of section data
MD5 0dff1781f89419eda522ea89aa941a8f
.pdata 27136 bytes · 1.6% of section data
MD5 420eaa676468751d0f16229466112d7a
.gfids 512 bytes · 0.0% of section data
Uncommon name
MD5 db0e5d1f95b650e4a9e67ab7506a97a8
.rsrc 1536 bytes · 0.1% of section data
MD5 07ad8073466597bc55519f4986ecf7bc
.reloc 8704 bytes · 0.5% of section data
MD5 51f14d2b60b90aa1b11bfd07d3ead9a3

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 51f5c0221887a742b7a5761e292bcfeb.
  • 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.