GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 ed5dc60c6dfda6b4ca321f147369de68
Latest seen 2025-07-04 23:01:14 (10 months ago)
First seen 2025-05-08 23:01:03 (a year ago)
Size 236 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-05-08 23:01:03 (a year ago); latest analysis 2025-07-04 23:01:14 (10 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.

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-07-04 23:01:14 (10 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: EpiBrowser
Company Name: EPI Software
MD5: ed5dc60c6dfda6b4ca321f147369de68
Size: 236 MB
First Published: 2025-05-08 23:01:03 (a year ago)
Latest Published: 2025-07-04 23:01:14 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-04 23:01:14 (10 months ago)
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.

%localappdata%\episoftware\epibrowser
%localappdata%\episoftware\epibrowser\134.0.6998.121\installer\epibrowser\epibrowser-bin

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.

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.

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 0x04966390
Image base 0x0000000180000000

PE Sections:

Sections 15
Raw data 247927808

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

.text 212032000 bytes · 85.5% of section data
Large raw data
MD5 85501dd65e51c569e059b8f005337eb2
.rdata 26889216 bytes · 10.8% of section data
Large raw data
MD5 bddebe70a30b29fbf12c698c6de8a69a
.data 770560 bytes · 0.3% of section data
MD5 957549e01ab5dca02e7e4fcce762f0bf
.pdata 6275584 bytes · 2.5% of section data
Large raw data
MD5 6d195521f7f809d3bf5bea179656965c
.gxfg 17408 bytes · 0.0% of section data
Uncommon name
MD5 7f4dce233f46ea7ca7441751b37c303e
.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 af8df527d7e75d0bf400a2079af3aafc
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 7926b1643803e280258d159f33334ff2
malloc_h 2048 bytes · 0.0% of section data
Uncommon name
MD5 53996a4b6570ecd131da891433abd03f
prot 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 287744 bytes · 0.1% of section data
MD5 532a4754855d64efcc1363501d9750fc
.reloc 1637888 bytes · 0.7% of section data
MD5 2341991bf10315306aafab7d574b381e

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