GridinSoft Threat Intelligence

chrome_pwa_launcher.exe file report

Under review File reputation report
MD5 da64d2346b80015ff9621f725843b6a6
Latest seen 2025-02-10 23:02:10 (a year 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-02-10 23:02:10 (a year 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_pwa_launcher.exe 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-02-10 23:02:10 (a year 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: da64d2346b80015ff9621f725843b6a6
Size: 1 MB
First Published: 2025-02-10 23:01:49 (a year ago)
Latest Published: 2025-02-10 23:02:10 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-10 23:02:10 (a year ago)

Overview

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

The signature on chrome_pwa_launcher.exe 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_pwa_launcher.exe 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_pwa_launcher.exe across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country France
Share 100.0%
Low High activity

The strongest geographic signal for this file is France with 100.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_pwa_launcher.exe 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_pwa_launcher.exe 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 0x0007af50
Image base 0x0000000140000000

PE Sections:

Sections 11
Raw data 1433088

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

.text 870912 bytes · 60.8% of section data
MD5 cc2624d5fada3737ea39d15c7d4bd5cd
.rdata 177152 bytes · 12.4% of section data
MD5 e138ebb5da18d2017c9c958b1e80070c
.data 59392 bytes · 4.1% of section data
MD5 70a9f9fbd82c22d86ffe9a6e9cb2eb6f
.pdata 30208 bytes · 2.1% of section data
MD5 7b616c50dfa379e6dcb50bd9719b4184
.gxfg 11264 bytes · 0.8% of section data
Uncommon name
MD5 4b54005defb762e5c806d8d7731f58b7
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 8c950f651287cbc1296bcb4e8cd7e990
.tls 512 bytes · 0.0% of section data
MD5 ae0e4d7e29628d02ec08c8c3854c3d3d
LZMADEC 4608 bytes · 0.3% of section data
Uncommon name
MD5 05e9eab8428a551a281ab278073669fa
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 5bc1e09d50e7c24e7cc05c44ded6622d
.rsrc 272384 bytes · 19.0% of section data
MD5 c413215d40df3b0fa3757e3624db802e
.reloc 5632 bytes · 0.4% of section data
MD5 10b6b51b628bfbcfe4d29179b23f02da

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