GridinSoft Threat Intelligence

sqlcese35.dll file report

Clean record File reputation report
MD5 958582542e5827c3b1b191f1c6c123f4
Latest seen 2024-03-12 23:02:21 (2 years ago)
First seen 2018-01-15 09:10:54 (8 years ago)
Size 353 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:21 (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.

sqlcese35.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:21 (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: 958582542e5827c3b1b191f1c6c123f4
Size: 353 KB
First Published: 2018-01-15 09:10:54 (8 years ago)
Latest Published: 2024-03-12 23:02:21 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-03-12 23:02:21 (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 sqlcese35.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 sqlcese35.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.

sqlcese35.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 0x0004b08e
Image base 0x7d550000

PE Sections:

Sections 5
Raw data 354816

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

.text 325632 bytes · 91.8% of section data
MD5 85b1f5506c53fc41970e42a77f0211ef
PAGELK 4608 bytes · 1.3% of section data
Uncommon name
MD5 9f1076f5226aa9fb8482142aaa6084d8
.data 9216 bytes · 2.6% of section data
MD5 01e0bef0136cd302d0f63231304ab861
.rsrc 2048 bytes · 0.6% of section data
MD5 f82a9dadc1dffd96b2ad0f9db1a56f08
.reloc 13312 bytes · 3.8% of section data
MD5 1d06248443009c415b36db4ab1830e5e

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 958582542e5827c3b1b191f1c6c123f4.
  • 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.