GridinSoft Threat Intelligence
chrome_screen_ai.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2025-12-22 23:02:28 (5 months ago); latest analysis 2025-12-22 23:02:28 (5 months ago).
Company metadata: Google, Inc.. Product metadata: Chrome.
Signed by Google LLC. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- 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-12-22 23:02:28 (5 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: | c5ab028c0bc66a5bc442c3a2cb7c0c7c |
| Size: | 32 MB |
| First Published: | 2025-12-22 23:02:28 (5 months ago) |
| Latest Published: | 2025-12-22 23:02:28 (5 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-12-22 23:02:28 (5 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 |
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 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
fb4dfa188c226bca470e36c2c446dfd1
cfe30fbbb14c3e33f2ca4a67b5bed440
b1bf0b3206508d2a883e950f47eec401
472eb7864da4d58a7dc3c2c0be93ea95
bf619eac0cdf3f68d496ea9344137e8b
a110695578218fd8f1c173be1d86e64b
f6bd48c9d245a23b91b91aec43c1ae5a
a1382bbc7b00d666274499f2351a545a
f62f7e6b49d401ae75765c9a52708e7a
d12a21aeb632e0800d91095178ddc4c7
869b6d056d7a3946921850b9e9e708f8
b12cf3e2e8656a6ce671eec3757a501a
7c596fb721e1d9b961547950a6e1ad92
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.