GridinSoft Threat Intelligence

chrome_pwa_launcher.exe file report

Under review File reputation report
MD5 7308637292b6e167085b862a63eb63e0
Latest seen 2025-07-17 23:01:00 (10 months ago)
First seen 2024-09-04 23:01:45 (2 years ago)
Size 1 MB
Publisher Adaptive Bee
Product UR
Signed by AdaptiveBee SAS

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-09-04 23:01:45 (2 years ago); latest analysis 2025-07-17 23:01:00 (10 months ago).

Publisher context

Company metadata: Adaptive Bee. Product metadata: UR.

Digital signature

Signed by AdaptiveBee SAS. 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 UR. The reported company name is Adaptive Bee. The current detection status is Undefined, based on the latest analysis from 2025-07-17 23:01:00 (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.

File Details

Product Name: UR
Company Name: Adaptive Bee
MD5: 7308637292b6e167085b862a63eb63e0
Size: 1 MB
First Published: 2024-09-04 23:01:45 (2 years ago)
Latest Published: 2025-07-17 23:01:00 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-17 23:01:00 (10 months ago)

Overview

Signed By: AdaptiveBee SAS
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%\urbrowser\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 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Egypt
Share 33.3%
Low High activity

The strongest geographic signal for this file is Egypt with 33.3% 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 66.7%
Windows 8.1 33.3%

The most common operating system signal for chrome_pwa_launcher.exe is Windows 10 with 66.7% 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 0x0007ea50
Image base 0x0000000140000000

PE Sections:

Sections 12
Raw data 1431040

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

.text 886272 bytes · 61.9% of section data
MD5 a312c991b5bfb7a8c0b9da91dd6d296d
.rdata 158208 bytes · 11.1% of section data
MD5 a43731262ccea2cd5049779a0e38d75d
.data 63488 bytes · 4.4% of section data
MD5 913a604d2eafe83f8fa62c43f81d6e9d
.pdata 31744 bytes · 2.2% of section data
MD5 64f8423985dc21dd86ccce58e50af076
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 1275644d7ceb87ebd8ed61acf3c8518f
.gxfg 11264 bytes · 0.8% of section data
Uncommon name
MD5 baf4c7a4e16f1929457475be231f072b
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 67ca2fdbe374e0103cf24d8bfee7140e
.tls 512 bytes · 0.0% of section data
MD5 1f354d76203061bfdd5a53dae48d5435
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 d6a4c3d9b6a0fa9ad4d9a91ec508cd54
malloc_h 512 bytes · 0.0% of section data
Uncommon name
MD5 52545caeae3a5a1ab84bbc62aed49e40
.rsrc 272384 bytes · 19.0% of section data
MD5 23f161f29d2d2f473a2a8f455d552e6b
.reloc 5120 bytes · 0.4% of section data
MD5 279c682856c1fee2a4d873aa76bdeec0

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 7308637292b6e167085b862a63eb63e0.
  • 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.