GridinSoft Threat Intelligence
sqlite3.dll#10DE9A1A4C90E98E file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-05-22 09:03:33 (8 years ago); latest analysis 2024-04-09 23:01:49 (2 years ago).
Signed by BlueSprig, Inc.. The signature is reported as valid, but signed files can still be bundled or abused.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
sqlite3.dll#10DE9A1A4C90E98E is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2024-04-09 23:01:49 (2 years 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
| MD5: | 1088cd9f04933e8252d27fa9e143a8a3 |
| Size: | 563 KB |
| First Published: | 2017-05-22 09:03:33 (8 years ago) |
| Latest Published: | 2024-04-09 23:01:49 (2 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2024-04-09 23:01:49 (2 years ago) |
Overview
| Signed By: | BlueSprig, Inc. |
| Status: | Valid |
The signature on sqlite3.dll#10DE9A1A4C90E98E 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:
| %programfiles%\bluesprig\jetclean |
| %profile%\errick\my documents\downloads\jetclean portable |
| %sysdrive%\system volume information\_restore{fdf53523-082d-4662-8a1b-62a9c621d0b8}\rp1 |
| %appdata%\vos\jetclean\prog\%program files (x86)%\bluesprig\jetclean |
| %desktop%\current new\software\tech\cleaner software\misc\jetclean |
| %programfiles%\program files (x86)\bluesprig\jetclean |
| %profile%\downloads\programy portable\jetclean portable |
| %profile%\downloads\optimal\jetclean\jetcleanportable |
| %programfiles%\vasile 32\bluesprig\jetclean |
| %programfiles%\bluesprig |
ThreatInfo has observed sqlite3.dll#10DE9A1A4C90E98E 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.
File Names:
5 observed namesThis hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.
Geographic signal
Observed country distribution
ThreatInfo has seen sqlite3.dll#10DE9A1A4C90E98E across 79 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Poland with 13.2% 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 sqlite3.dll#10DE9A1A4C90E98E is Windows 10 with 47.2% 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
sqlite3.dll#10DE9A1A4C90E98E 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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
34e5d1cdf4e0fce2e570d093f4487a62
4f89e428e2e1171d53bf3e01d2f1202a
9f32b73e2dd07f7a68de8318437ac58b
00000000000000000000000000000000
f9b4c46b246174c27a633a526ef29999
d8886616cc691e3f022a5627afec4a07
e021b68463dae3e7a684cc8f76839377
ca407773c2c51399a48dbc0213ce5a89
933ac22ff520addd39862eef07b988be
5a1620a74f25c7cbb1e021d0b3efa1ba
004c0776d9fa8d19ec8a9fb73ff8e0a7
a48cf693d600085a37e3e743ad3f494c
b1ad82cc20ed62af983440266ca49ac9
df6dcae20d2c3ea05908d6a5ac43fe1d
7bb0d5f92e038c71e5407673630f81aa
f8bb541788979302a23cb30f97f3542f
14f8eb767d485e23c1afdee4dcb14cef
5c248458c05f0f700bf91ab04c2702cb
60ad4279e64e3057e9da309bc9e4a413
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.