GridinSoft Threat Intelligence

conkeeper.dll file report

Under review File reputation report
MD5 6bdc72ccaef3749e8fd2c6325060b15b
Latest seen 2022-05-30 23:37:56 (3 years ago)
First seen 2017-05-22 11:18:43 (9 years ago)
Size 186 KB
Publisher iMBC
Product Conkeeper

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 11:18:43 (9 years ago); latest analysis 2022-05-30 23:37:56 (3 years ago).

Publisher context

Company metadata: iMBC. Product metadata: Conkeeper.

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.

conkeeper.dll is a Windows file recorded in the ThreatInfo database. It is associated with Conkeeper. The reported company name is iMBC. The current detection status is Undefined, based on the latest analysis from 2022-05-30 23:37:56 (3 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.

Product Name: Conkeeper
Company Name: iMBC
MD5: 6bdc72ccaef3749e8fd2c6325060b15b
Size: 186 KB
First Published: 2017-05-22 11:18:43 (9 years ago)
Latest Published: 2022-05-30 23:37:56 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-05-30 23:37:56 (3 years ago)
%programfiles%\fileham.com\mureka
%programfiles%\me2disk
%programfiles%\daoki
%programfiles%\pdpopx
%programfiles%\sharebox
%programfiles%\filecast
%programfiles%
%programfiles%\fileham.com

ThreatInfo has observed conkeeper.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 69.7%
Windows 7 27.2%
Windows 8.1 2.4%
Windows XP 0.4%
Windows 8 0.2%

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

conkeeper.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 0x00007462
Image base 0x10000000

PE Sections:

Sections 5
Raw data 189440

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

.text 112128 bytes · 59.2% of section data
MD5 0c70055f48f128bab8803a11b6a80763
.rdata 37376 bytes · 19.7% of section data
MD5 acce3b4aa24da18e6f790fbcb5dd52cb
.data 6656 bytes · 3.5% of section data
MD5 64ab75e883cc24006959136027e84e8a
.rsrc 1536 bytes · 0.8% of section data
MD5 36b2009cbc715e4543284cc52dfd98b6
.reloc 31744 bytes · 16.8% of section data
MD5 c63eb95bf883313c23efc90fbb734bc8

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 6bdc72ccaef3749e8fd2c6325060b15b.
  • 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.