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-29 23:01:41 (5 months ago); latest analysis 2025-12-29 23:01:41 (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-29 23:01:41 (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: | ae7b7524c6b381b2775c3fa00d273967 |
| Size: | 32 MB |
| First Published: | 2025-12-29 23:01:41 (5 months ago) |
| Latest Published: | 2025-12-29 23:01:41 (5 months ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-12-29 23:01:41 (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%\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 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 Kingdom 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.
629f36fa30ba4cd9d7df96454a279c9e
f1da34b5f6a8b78da6abb3f9c0e95566
fd5c27665208040f9e25a5a69ae250f7
469354779c9cda3798f80970ae8211f3
bf619eac0cdf3f68d496ea9344137e8b
a110695578218fd8f1c173be1d86e64b
ba3e0164adaab4d65d31b320198ea5d6
c940bb152f863c806b99002ff008f6d6
0055d25f925821825fe50f594e3447f8
c9ffdea9c0a73839cb5bb376c4f4afe3
c16aabfb11f94c406267f00b04497463
5f26715b27955c6db4d9e38882d2e224
92e1ee9cdce2f2dfd22f46c936d727f5
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.