GridinSoft Threat Intelligence

chrome_screen_ai.dll file report

Under review File reputation report
MD5 7e537ba1ecd5e5ef76e7baa383c1d486
Latest seen 2025-05-04 23:02:37 (a year ago)
First seen 2025-04-09 23:00:24 (a year ago)
Size 31 MB
Publisher Google, Inc.
Product Chrome
Signed by Google LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-04-09 23:00:24 (a year ago); latest analysis 2025-05-04 23:02:37 (a year ago).

Publisher context

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

Digital signature

Signed by Google LLC. 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_screen_ai.dll is a Windows file recorded in the ThreatInfo database. It is associated with Chrome. The reported company name is Google, Inc.. The current detection status is Undefined, based on the latest analysis from 2025-05-04 23:02:37 (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: Chrome
Company Name: Google, Inc.
MD5: 7e537ba1ecd5e5ef76e7baa383c1d486
Size: 31 MB
First Published: 2025-04-09 23:00:24 (a year ago)
Latest Published: 2025-05-04 23:02:37 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-04 23:02:37 (a year ago)

Overview

Signed By: Google LLC
Status: Valid

The signature on chrome_screen_ai.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.

Common Places:

%localappdata%\onestart.ai\onestart\user data\screen_ai
%localappdata%\wavebrowser\user data\screen_ai

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

Geographic signal

Observed country distribution

ThreatInfo has seen chrome_screen_ai.dll across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 50.0%
Low High activity

The strongest geographic signal for this file is United States with 50.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_screen_ai.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.

Analysis

chrome_screen_ai.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 0x016415d0
Image base 0x0000000180000000

PE Sections:

Sections 14
Raw data 32758784

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

.text 23672832 bytes · 72.3% of section data
Large raw data
MD5 f11a981721e1e9702282ed4065bf57e3
.rdata 6276608 bytes · 19.2% of section data
Large raw data
MD5 19a68a86077702acab9d81396768c22e
.data 1394176 bytes · 4.3% of section data
MD5 25a52987f4430adbae3030a44ba00075
.pdata 449536 bytes · 1.4% of section data
MD5 8beb7f110b732026e79f2a17e9470db3
.gxfg 15872 bytes · 0.0% of section data
Uncommon name
MD5 2e8ba7c430ef713ad28ddbf4f03a94c5
.retplne 512 bytes · 0.0% of section data
Uncommon name
MD5 bcdee87f658a7bf4080188f07db97ca9
.tls 1536 bytes · 0.0% of section data
MD5 ca6963265d9678b75bd5c0979a3676b4
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 fcb9347c60d623a38bdbcd6becd07eae
flags_he 9216 bytes · 0.0% of section data
Uncommon name
MD5 2669214b56a1a9df91745420e2f2e4a8
google_i 512 bytes · 0.0% of section data
Uncommon name
MD5 4043ad31997faf302386676bf12159b9
malloc_h 1024 bytes · 0.0% of section data
Uncommon name
MD5 dfc9013671ccb41db7757d867384d53d
protodes 702976 bytes · 2.1% of section data
Uncommon name
MD5 3118b561eba01f0bf784851495932f34
.rsrc 2048 bytes · 0.0% of section data
MD5 3708ad5bb94c6c740d5ef2b3f08a2026
.reloc 231424 bytes · 0.7% of section data
MD5 6765d58d384fec4db26ce7bc8a3ebd13

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