GridinSoft Threat Intelligence

chrome_launcher.exe file report

Under review File reputation report
MD5 84ca3e948fc4b7ebe92fac6a50a37bbb
Latest seen 2022-07-03 23:49:48 (3 years ago)
First seen 2022-07-03 23:49:48 (3 years ago)
Size 80 KB
Publisher MyPlayCity, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-07-03 23:49:48 (3 years ago); latest analysis 2022-07-03 23:49:48 (3 years ago).

Publisher context

Company metadata: MyPlayCity, Inc.. Product metadata: Google Chrome Frame.

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_launcher.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google Chrome Frame. The reported company name is MyPlayCity, Inc.. The current detection status is Undefined, based on the latest analysis from 2022-07-03 23:49:48 (3 years 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: Google Chrome Frame
Company Name: MyPlayCity, Inc.
MD5: 84ca3e948fc4b7ebe92fac6a50a37bbb
Size: 80 KB
First Published: 2022-07-03 23:49:48 (3 years ago)
Latest Published: 2022-07-03 23:49:48 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-07-03 23:49:48 (3 years ago)
%localappdata%\playfree browser\application

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

Windows 7 100.0%

The most common operating system signal for chrome_launcher.exe is Windows 7 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_launcher.exe is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x000047b6
Image base 0x00400000

PE Sections:

Sections 5
Raw data 80896

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

.text 46592 bytes · 57.6% of section data
MD5 1ae8d06e0095aa079435e9716ae43f4e
.rdata 21504 bytes · 26.6% of section data
MD5 fb8bbdbb4b27e7f3b00cd90bc454aaf5
.data 4096 bytes · 5.1% of section data
MD5 b504c411fcdf287b3d09ec2314130191
.rsrc 2048 bytes · 2.5% of section data
MD5 8bb1a660cc9449ced67110bf929e4772
.reloc 6656 bytes · 8.2% of section data
MD5 7c0eca1f6e4d744bb615576260a71d77

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 84ca3e948fc4b7ebe92fac6a50a37bbb.
  • 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.