GridinSoft Threat Intelligence

chrome_screen_ai.dll file report

Under review File reputation report
MD5 14bd0eaad1f0e5a4fe13e9ff436b5572
Latest seen 2025-05-15 23:09:23 (a year ago)
First seen 2025-05-15 23:09:23 (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-05-15 23:09:23 (a year ago); latest analysis 2025-05-15 23:09:23 (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-15 23:09:23 (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: 14bd0eaad1f0e5a4fe13e9ff436b5572
Size: 31 MB
First Published: 2025-05-15 23:09:23 (a year ago)
Latest Published: 2025-05-15 23:09:23 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-15 23:09:23 (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

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.

Top country Canada
Share 100.0%
Low High activity

The strongest geographic signal for this file is Canada 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:

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

PE Sections:

Sections 13
Raw data 33037312

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

.text 23948800 bytes · 72.5% of section data
Large raw data
MD5 19121c5d5081a2ae515262ff0bd5cae3
.rdata 6280704 bytes · 19.0% of section data
Large raw data
MD5 8016276f5284d2fc78a1eb76f34f91b3
.data 1394688 bytes · 4.2% of section data
MD5 8e856c3be07fc7c6ac5326b75df47936
.pdata 448000 bytes · 1.4% of section data
MD5 3edc17930b046cd4a47ae7c75403b844
.gxfg 15872 bytes · 0.0% of section data
Uncommon name
MD5 2376c38d8330c9d62c5b971e1ad28fc7
.tls 1536 bytes · 0.0% of section data
MD5 ca6963265d9678b75bd5c0979a3676b4
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 24aa096a98dbfa289825e3881e88054a
flags_he 9216 bytes · 0.0% of section data
Uncommon name
MD5 51f8189874c13bee8c05260b1948d05d
google_i 512 bytes · 0.0% of section data
Uncommon name
MD5 da00486172d13ebb6d5fc9e253f7fef5
malloc_h 1024 bytes · 0.0% of section data
Uncommon name
MD5 dfff64f9ab0f312e870d93c916f41004
protodes 703488 bytes · 2.1% of section data
Uncommon name
MD5 d4101946dba464e20fb1d2305d4c0132
.rsrc 2048 bytes · 0.0% of section data
MD5 a9f954f2642dc2c5e14969b95a64bb1c
.reloc 230912 bytes · 0.7% of section data
MD5 f97240c949a83b0a00b349218a99d819

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 14bd0eaad1f0e5a4fe13e9ff436b5572.
  • 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.