GridinSoft Threat Intelligence

sqlceme35.dll file report

Clean record File reputation report
MD5 1ac99f626c7b67616123887eaba4780c
Latest seen 2024-03-12 23:02:13 (2 years ago)
First seen 2018-01-15 09:10:54 (8 years ago)
Size 61 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-01-15 09:10:54 (8 years ago); latest analysis 2024-03-12 23:02:13 (2 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft SQL Server Compact.

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

sqlceme35.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft SQL Server Compact. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2024-03-12 23:02:13 (2 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Microsoft SQL Server Compact
Company Name: Microsoft Corporation
MD5: 1ac99f626c7b67616123887eaba4780c
Size: 61 KB
First Published: 2018-01-15 09:10:54 (8 years ago)
Latest Published: 2024-03-12 23:02:13 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-03-12 23:02:13 (2 years ago)
Signed By: Microsoft Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%sysdrive%\kreapixel
%sysdrive%

ThreatInfo has observed sqlceme35.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.

Windows 7 87.5%
Windows 10 12.5%

The most common operating system signal for sqlceme35.dll is Windows 7 with 87.5% 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.

sqlceme35.dll is identified as pe for 32-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 32-bit
Subsystem Windows CUI
Entry point 0x00006e9a
Image base 0x7d350000

PE Sections:

Sections 4
Raw data 56320

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

.text 42496 bytes · 75.5% of section data
MD5 a8f2b3c28037c176cf31276cdbc7dd4b
.data 1024 bytes · 1.8% of section data
MD5 e6e3d57bf0c94c79c3de9715f4e51f3a
.rsrc 10752 bytes · 19.1% of section data
MD5 50c0c41b29125352141d2972e21d80f6
.reloc 2048 bytes · 3.6% of section data
MD5 72c50c17bc383e73bde6cf76bda3052a

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 1ac99f626c7b67616123887eaba4780c.
  • 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.