GridinSoft Threat Intelligence

chrome_elf.dll file report

Under review File reputation report
MD5 7f07fa77a2fbd90735dd09a7ca8ee362
Latest seen 2025-11-14 23:01:41 (6 months ago)
First seen 2025-02-10 23:01:49 (a year ago)
Size 1 MB
Publisher EPI Software
Product EpiBrowser
Signed by Byte Media Sdn. Bhd.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-02-10 23:01:49 (a year ago); latest analysis 2025-11-14 23:01:41 (6 months ago).

Publisher context

Company metadata: EPI Software. Product metadata: EpiBrowser.

Digital signature

Signed by Byte Media Sdn. Bhd.. 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.

File context

chrome_elf.dll is a Windows file recorded in the ThreatInfo database. It is associated with EpiBrowser. The reported company name is EPI Software. The current detection status is Undefined, based on the latest analysis from 2025-11-14 23:01:41 (6 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.

File Details

Product Name: EpiBrowser
Company Name: EPI Software
MD5: 7f07fa77a2fbd90735dd09a7ca8ee362
Size: 1 MB
First Published: 2025-02-10 23:01:49 (a year ago)
Latest Published: 2025-11-14 23:01:41 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-14 23:01:41 (6 months ago)

Overview

Signed By: Byte Media Sdn. Bhd.
Status: Valid

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

Common Places:

%localappdata%\episoftware\epibrowser\application

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

Geographic signal

Observed country distribution

ThreatInfo has seen chrome_elf.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country France
Share 40.0%
Low High activity

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

OS Version:

Windows 10 100.0%

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

Analysis

chrome_elf.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 0x0008bf50
Image base 0x0000000180000000

PE Sections:

Sections 12
Raw data 1312256

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

.text 1003520 bytes · 76.5% of section data
MD5 a3a434bf4345745c98b814093ad91f9e
.rdata 189952 bytes · 14.5% of section data
MD5 8dd40676eb7f4a353aa2c93a544ccb3d
.data 61440 bytes · 4.7% of section data
MD5 447898e0cff3f2859c5f0f74c1060b4f
.pdata 34816 bytes · 2.7% of section data
MD5 70271402f9d8eef2bd0db4729143b67b
.crthunk 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.gxfg 11776 bytes · 0.9% of section data
Uncommon name
MD5 5121a4f34116b838e06716fb9db5b33d
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 8c950f651287cbc1296bcb4e8cd7e990
.tls 512 bytes · 0.0% of section data
MD5 70291d67d3ce7bc11c682812d24697ab
CPADinfo 512 bytes · 0.0% of section data
Uncommon name
MD5 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 f32dd6e3a257813434ec3e69c50f3931
.rsrc 2048 bytes · 0.2% of section data
MD5 fa20da46dbe00efd70f35e12cf34b929
.reloc 6144 bytes · 0.5% of section data
MD5 2e435c3d8256cbd85cc8634118cc64dd

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