libcef.dll file report

MD5 2ad45b5ff667ae0b944c9f574555f95b
Latest seen 2021-01-02 00:13:46 (5 years ago)
First seen 2019-06-29 13:38:31 (6 years ago)
Size 54 MB
Signed by YY Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-06-29 13:38:31 (6 years ago); latest analysis 2021-01-02 00:13:46 (5 years ago).

Publisher context

Product metadata: Chromium Embedded Framework (CEF) Dynamic Link Library.

Digital signature

Signed by YY Inc.. 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.

libcef.dll is a Windows file recorded in the ThreatInfo database. It is associated with Chromium Embedded Framework (CEF) Dynamic Link Library. The current detection status is Undefined, based on the latest analysis from 2021-01-02 00:13:46 (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: Chromium Embedded Framework (CEF) Dynamic Link Library
MD5: 2ad45b5ff667ae0b944c9f574555f95b
Size: 54 MB
First Published: 2019-06-29 13:38:31 (6 years ago)
Latest Published: 2021-01-02 00:13:46 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-02 00:13:46 (5 years ago)
Signed By: YY Inc.
Status: Valid

The signature on libcef.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.

%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev
%appdata%\duowan\yy\yycomstore\2052\com.yy.cefdev

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

33.3%
22.2%
11.1%
11.1%
11.1%
11.1%

The strongest geographic signal for this file is Taiwan with 33.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

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

libcef.dll is identified as pe for 32 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.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x01eab959

PE Sections:

Name Size of data MD5
.text 44979200 e0fad58f29f77013827949a7ee079b4d
.rdata 9932288 35aa0c2ef9607c3de7fbb3b79de620ec
.data 201728 2eed75cda45b0c935b22ebb912c81ced
.tls 512 bf619eac0cdf3f68d496ea9344137e8b
_RDATA 7680 320690bfa5a71498e1ff4e120799e10b
.rodata 7680 79a83467bf49fb9e049fb2e57e7a1818
.rsrc 53248 aa9648f57b32e35e872e766ab18ff599
.reloc 1584640 77b61cc04c08874ac2e3a8295017794d

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.

More information: