GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 93402aaec5ec8bbec80d35465cc0fb7f
Latest seen 2025-11-14 23:00:58 (6 months ago)
First seen 2025-02-10 23:01:49 (a year ago)
Size 229 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:00:58 (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.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:00:58 (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: 93402aaec5ec8bbec80d35465cc0fb7f
Size: 229 MB
First Published: 2025-02-10 23:01:49 (a year ago)
Latest Published: 2025-11-14 23:00:58 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-14 23:00:58 (6 months ago)

Overview

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

The signature on chrome.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.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.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.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.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 0x046c7810
Image base 0x0000000180000000

PE Sections:

Sections 15
Raw data 240773120

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

.text 205843456 bytes · 85.5% of section data
Large raw data
MD5 5e252b9d51d804b24912c804e2ed04c2
.rdata 26106368 bytes · 10.8% of section data
Large raw data
MD5 989388b74964c36ffa835deaae553a7f
.data 759808 bytes · 0.3% of section data
MD5 530c4e6cb82287c8d3d146fa7db47049
.pdata 6136320 bytes · 2.5% of section data
Large raw data
MD5 c8a5d03d0f66253c86e36b38a47dbc40
.gxfg 17408 bytes · 0.0% of section data
Uncommon name
MD5 51c052cf529999849e8e9bf74fcaaaae
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 4ac76059ee0060187998770785026e3a
.rodata 4608 bytes · 0.0% of section data
MD5 c642bc1527b5873b6dbf56c4a87d20cb
.tls 4096 bytes · 0.0% of section data
MD5 d43baec359bfae08735c34d508501e66
CPADinfo 512 bytes · 0.0% of section data
Uncommon name
MD5 60d3ea61d541c9be2e845d2787fb9574
LZMADEC 4608 bytes · 0.0% of section data
Uncommon name
MD5 05e9eab8428a551a281ab278073669fa
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 a534ed2e28ff1d7354ce8d831211b427
malloc_h 1536 bytes · 0.0% of section data
Uncommon name
MD5 776f934650e9dfbe15cff5a772d050bd
prot 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 287744 bytes · 0.1% of section data
MD5 56e47e01089926d7632d6ee11b45eadf
.reloc 1605120 bytes · 0.7% of section data
MD5 5bd8bc1d3dc9c8f7950c55040af235f3

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 93402aaec5ec8bbec80d35465cc0fb7f.
  • 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.