GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 eef64d93526fc8512af03dc4d435be7f
Latest seen 2022-07-03 23:55:21 (3 years ago)
First seen 2022-07-03 23:55:21 (3 years ago)
Size 54 MB
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:55:21 (3 years ago); latest analysis 2022-07-03 23:55:21 (3 years ago).

Publisher context

Company metadata: MyPlayCity, Inc.. Product metadata: PlayFree Browser.

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 PlayFree Browser. The reported company name is MyPlayCity, Inc.. The current detection status is Undefined, based on the latest analysis from 2022-07-03 23:55:21 (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: PlayFree Browser
Company Name: MyPlayCity, Inc.
MD5: eef64d93526fc8512af03dc4d435be7f
Size: 54 MB
First Published: 2022-07-03 23:55:21 (3 years ago)
Latest Published: 2022-07-03 23:55:21 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-07-03 23:55:21 (3 years ago)
%localappdata%\playfree browser\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.

Windows 7 100.0%

The most common operating system signal for chrome.dll 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.dll 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 0x00006fab
Image base 0x01c30000

PE Sections:

Sections 8
Raw data 56624128

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

.text 40793600 bytes · 72.0% of section data
Large raw data
MD5 a3e423af72a4ba912f989842c3f035f6
.rdata 8544256 bytes · 15.1% of section data
Large raw data
MD5 4be7265fcb9c023a72240805f1460b05
.data 503808 bytes · 0.9% of section data
MD5 2afca7b285d67bdc2c8d79019b3ac72f
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.unwante 4096 bytes · 0.0% of section data
Uncommon name
MD5 55c7b26b61033e8b8a4cd5dd919305fc
.rodata 5632 bytes · 0.0% of section data
MD5 6e372f73f1ff8fe53f477f06d9e05f22
.rsrc 4734464 bytes · 8.4% of section data
MD5 770385c753ec79949101e6b88d16f6df
.reloc 2037760 bytes · 3.6% of section data
MD5 fe2a76f809cd857840835049c9cfef0f

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