chrome_screen_ai.dll file report

MD5 d7ad5de66833d7780dc338ec0e6d9758
Latest seen 2025-11-22 23:00:48 (6 months ago)
First seen 2025-11-02 23:01:41 (6 months ago)
Size 32 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-11-02 23:01:41 (6 months ago); latest analysis 2025-11-22 23:00:48 (6 months 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.

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-11-22 23:00:48 (6 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.

Product Name: Chrome
Company Name: Google, Inc.
MD5: d7ad5de66833d7780dc338ec0e6d9758
Size: 32 MB
First Published: 2025-11-02 23:01:41 (6 months ago)
Latest Published: 2025-11-22 23:00:48 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-22 23:00:48 (6 months ago)
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.

%localappdata%\wavebrowser\user data\screen_ai
%localappdata%\onestart.ai\onestart\user data\screen_ai
%localappdata%\shift\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.

66.7%
33.3%

The strongest geographic signal for this file is United States with 66.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

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.

chrome_screen_ai.dll is identified as pe for 64 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.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000180000000
Entry Address: 0x01780880

PE Sections:

Name Size of data MD5
.text 24996864 70e0d688fcf392e439bd6ee56e2df64b
.rdata 6379008 a9a62b7161e6dab2badba1200e79ad9a
.data 1367552 74a9b9e7012f9a03b7dd08e7c9e33118
.pdata 458752 73bf3cf3a2e6e1e9b11e07e99e4dad4b
.fptable 512 bf619eac0cdf3f68d496ea9344137e8b
.tls 1536 ca6963265d9678b75bd5c0979a3676b4
_RDATA 512 cd3909688fd333e4593e9ffaeb27b314
flags_he 11776 893a8b6625b9f632e664939709c41a42
google_i 512 146a984b987217aab389607797b9f0f0
malloc_h 1024 1da2f0a59ccb857cd209a1d2b14a1f29
protodes 716800 b169b5bb9785f4db38cf369d5884c66f
.rsrc 2048 c5a0b24d5dfd625d52a1c9530cafb9cd
.reloc 232448 10ea8253aaa70e3f440309076ac21250

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.

More information: