GridinSoft Threat Intelligence

cefsharp.wpf.dll file report

Under review File reputation report
MD5 aad64a1fb1d52fa9081959193630c244
Latest seen 2025-12-30 23:00:50 (5 months ago)
First seen 2022-09-02 23:11:35 (3 years ago)
Size 80 KB
Product CefSharp
Signed by Driver Support

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-09-02 23:11:35 (3 years ago); latest analysis 2025-12-30 23:00:50 (5 months ago).

Publisher context

Company metadata: The CefSharp Authors. Product metadata: CefSharp.

Digital signature

Signed by Driver Support. 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.

cefsharp.wpf.dll is a Windows file recorded in the ThreatInfo database. It is associated with CefSharp. The reported company name is The CefSharp Authors. The current detection status is Undefined, based on the latest analysis from 2025-12-30 23:00:50 (5 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: CefSharp
Company Name: The CefSharp Authors
MD5: aad64a1fb1d52fa9081959193630c244
Size: 80 KB
First Published: 2022-09-02 23:11:35 (3 years ago)
Latest Published: 2025-12-30 23:00:50 (5 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-12-30 23:00:50 (5 months ago)
Signed By: Driver Support
Status: Valid

The signature on cefsharp.wpf.dll 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%

ThreatInfo has observed cefsharp.wpf.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 100.0%

The most common operating system signal for cefsharp.wpf.dll 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.

cefsharp.wpf.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point
Image base

.NET Info:

MVID: 3b0c5f6d-4d47-42bf-8b9e-94430fdb35a9

PE Sections:

Sections 2
Raw data 63488

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

.text 62464 bytes · 98.4% of section data
MD5 6b629f1d1b6cb08b3c563a240685ea98
.rsrc 1024 bytes · 1.6% of section data
MD5 a29b26f8271e234b649f9cfe1da957ed

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