GridinSoft Threat Intelligence

dlkrnl.dll file report

Under review File reputation report
MD5 7a9326b8bae535f18cb2669d50db9659
Latest seen 2025-07-08 23:00:59 (10 months ago)
First seen 2025-06-14 23:00:21 (a year ago)
Size 288 KB
Publisher Datalode, Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-06-14 23:00:21 (a year ago); latest analysis 2025-07-08 23:00:59 (10 months ago).

Publisher context

Company metadata: Datalode, Inc.. Product metadata: Datalode Agent Kernel.

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.

dlkrnl.dll is a Windows file recorded in the ThreatInfo database. It is associated with Datalode Agent Kernel. The reported company name is Datalode, Inc.. The current detection status is Undefined, based on the latest analysis from 2025-07-08 23:00:59 (10 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.

Product Name: Datalode Agent Kernel
Company Name: Datalode, Inc.
MD5: 7a9326b8bae535f18cb2669d50db9659
Size: 288 KB
First Published: 2025-06-14 23:00:21 (a year ago)
Latest Published: 2025-07-08 23:00:59 (10 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-07-08 23:00:59 (10 months ago)
%programfiles%\encore\hoyle card games 2011
%programfiles%\encore\hoyle casino games 2011
%programfiles%\encore\hoyle casino games 2011\pc_enc_reg_hoyle casino
%programfiles%\encore\hoyle casino 2010\pc_enc_reg_hoyle casino

ThreatInfo has observed dlkrnl.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 10 85.7%
Windows 7 14.3%

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

dlkrnl.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x0002099a
Image base 0x10000000

PE Sections:

Sections 6
Raw data 290816

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

.text 147456 bytes · 50.7% of section data
MD5 ffc0670fe4863a39dae44992a3e51b0d
.rdata 32768 bytes · 11.3% of section data
MD5 9a8f14f32ec4da1f0978ed20ad031f48
.data 61440 bytes · 21.1% of section data
MD5 d54203cd75b8a4d00046b271ba67331b
SharedMe 4096 bytes · 1.4% of section data
Uncommon name
MD5 620f0b67a91f7f74151bc5be745b7110
.rsrc 4096 bytes · 1.4% of section data
MD5 160988e6811e9510c7ac4a1c6025e773
.reloc 40960 bytes · 14.1% of section data
MD5 6af9e5785ff75e4f603cdeeac9ebef93

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 7a9326b8bae535f18cb2669d50db9659.
  • 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.