GridinSoft Threat Intelligence

chrome_screen_ai.dll file report

Under review File reputation report
MD5 db5c89099c700656dd6e39967037785d
Latest seen 2025-09-08 23:01:04 (8 months ago)
First seen 2025-09-01 23:01:06 (8 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-09-01 23:01:06 (8 months ago); latest analysis 2025-09-08 23:01:04 (8 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.

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-09-08 23:01:04 (8 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: Chrome
Company Name: Google, Inc.
MD5: db5c89099c700656dd6e39967037785d
Size: 32 MB
First Published: 2025-09-01 23:01:06 (8 months ago)
Latest Published: 2025-09-08 23:01:04 (8 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-09-08 23:01:04 (8 months 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%\shift\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 66.7%
Low High activity

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.

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 0x017412c0
Image base 0x0000000180000000

PE Sections:

Sections 13
Raw data 33949696

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

.text 24735744 bytes · 72.9% of section data
Large raw data
MD5 f98476a41c105b88b2b09e351ae1eb9b
.rdata 6394368 bytes · 18.8% of section data
Large raw data
MD5 846c4dea59c947f94d0eb7233aa211cd
.data 1399808 bytes · 4.1% of section data
MD5 49922c13957ae70b41ff07cb2b37506d
.pdata 460800 bytes · 1.4% of section data
MD5 edc4a155a9b8a7f94bda9b472f9c1077
.fptable 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.tls 1536 bytes · 0.0% of section data
MD5 ca6963265d9678b75bd5c0979a3676b4
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 c3b28219dbc0965b814367684e0af253
flags_he 9728 bytes · 0.0% of section data
Uncommon name
MD5 ea8c73bc43a87da8665eb55f1db3e44f
google_i 512 bytes · 0.0% of section data
Uncommon name
MD5 3b64d1c4cdd0c48e94ee328d51f95f9b
malloc_h 1024 bytes · 0.0% of section data
Uncommon name
MD5 127d858bbd16de4d759ff2b7238e2cb2
protodes 710144 bytes · 2.1% of section data
Uncommon name
MD5 2ab1319f017fe3310dafcf0661350ac8
.rsrc 2048 bytes · 0.0% of section data
MD5 184fcf7774d2c8bf6d172944e243e701
.reloc 232960 bytes · 0.7% of section data
MD5 75da014038cccaa8a293f13674ebd2fb

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