libcef.dll threat report

MD5 0ab1b4bc97a0142c482789ec640f9ed4
Latest seen 2024-03-25 23:04:28 (2 years ago)
First seen 2022-10-08 23:51:24 (3 years ago)
Size 162 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2024-03-25 23:04:28 (2 years ago)
File hash
0ab1b4bc97a0142c482789ec640f9ed4
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2022-10-08 23:51:24 (3 years ago); latest analysis 2024-03-25 23:04:28 (2 years ago).

Publisher context

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

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

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 Trojan.Heur!, based on the latest analysis from 2024-03-25 23:04:28 (2 years ago).

If libcef.dll appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

Product Name: Chromium Embedded Framework (CEF) Dynamic Link Library
MD5: 0ab1b4bc97a0142c482789ec640f9ed4
Size: 162 MB
First Published: 2022-10-08 23:51:24 (3 years ago)
Latest Published: 2024-03-25 23:04:28 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-03-25 23:04:28 (2 years ago)
libcef.dll detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%programfiles%\oculus\software\software\bigscreen-bigscreen\bigscreen_data\plugins\x86_64
%programfiles%\ragnarok\gamelauncher\roo_pc\ro_data\plugins
%programfiles%\ragnarok\gamelauncher\gamelauncher_data\plugins\x86_64
%programfiles%\oculus\software\software\bigscreen-bigscreen\bigscreen_data\plugins\x86_64
%programfiles%\oculus\software\software\bigscreen-bigscreen\bigscreen_data\plugins\x86_64
%programfiles%\oculus\software\software\bigscreen-bigscreen\bigscreen_data\plugins\x86_64
%sysdrive%\games\software\bigscreen-bigscreen\bigscreen_data\plugins\x86_64
%sysdrive%\games\ragnarok origin\gamelauncher\gamelauncher_data\plugins\x86

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.

37.5%
37.5%
12.5%
12.5%

The strongest geographic signal for this file is Brazil with 37.5% 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 64 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: 64
Image Base: 0x0000000180000000
Entry Address: 0x085a3630

PE Sections:

Name Size of data MD5
.text 140515328 36421b44fe08666a2d79c4fae358593e
.rdata 22178304 5011ee952e91916a143749aa873840a5
.data 579584 b786ee2d99f7dff0256b5845a66b96ef
.pdata 5213696 3f10cb485ac810bd5639b6dca74018e0
.00cfg 512 a49e58ac282f375ef747132e1c8c4158
.retplne 512 5aae1404b2d32c92d232eadc8296c323
.rodata 4608 5103ab26d7d806bfe65557abb8889d40
.tls 1024 356a47ba157dd74f404a9a0648c0aa24
.voltbl 512 22569f571692d56d9b5ac5b8dea43eef
CPADinfo 512 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 573cb632e93c4580e2c3f702fdb2338b
malloc_h 512 20950373a71784cf8032be1c3dcb92ab
.rsrc 144896 4fa800353e994b7c6d5e0bd18387b481
.reloc 1407488 5e37e4ee6a2fa133c61d3030d90eb99d

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: