GridinSoft Threat Intelligence

I2cHkBurn.sys file report

Under review File reputation report
MD5 38c20ebb2621a86a5e9729eda8f0f126
Latest seen 2024-11-11 23:00:51 (2 years ago)
First seen 2019-04-06 17:50:29 (7 years ago)
Size 40 KB
Publisher FINTEK Corp.
Product FINTEK FitGpBus Device Driver
Signed by Feature Integration Technology;Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-04-06 17:50:29 (7 years ago); latest analysis 2024-11-11 23:00:51 (2 years ago).

Publisher context

Company metadata: FINTEK Corp.. Product metadata: FINTEK FitGpBus Device Driver.

Digital signature

Signed by Feature Integration Technology;Microsoft Windows Hardware Compatibility Publisher. The signature is reported as valid, but signed files can still be bundled or abused.

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.

File context

I2cHkBurn.sys is a Windows file recorded in the ThreatInfo database. It is associated with FINTEK FitGpBus Device Driver. The reported company name is FINTEK Corp.. The current detection status is Undefined, based on the latest analysis from 2024-11-11 23:00:51 (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

Product Name: FINTEK FitGpBus Device Driver
Company Name: FINTEK Corp.
MD5: 38c20ebb2621a86a5e9729eda8f0f126
Size: 40 KB
First Published: 2019-04-06 17:50:29 (7 years ago)
Latest Published: 2024-11-11 23:00:51 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-11-11 23:00:51 (2 years ago)

Overview

Signed By: Feature Integration Technology;Microsoft Windows Hardware Compatibility Publisher
Status: Valid

The signature on I2cHkBurn.sys 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:

%localappdata%\slimware utilities inc\slimdrivers\backups\20170322t192846101103
%localappdata%\slimware utilities inc\slimdrivers\backups\20180304t184618844900
%localappdata%\slimware utilities inc\slimdrivers\backups\20180304t192106125286

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

Geographic signal

Observed country distribution

ThreatInfo has seen I2cHkBurn.sys across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Poland
Share 100.0%
Low High activity

The strongest geographic signal for this file is Poland with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 80.0%
Windows 7 20.0%

The most common operating system signal for I2cHkBurn.sys is Windows 10 with 80.0% 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

I2cHkBurn.sys is identified as pe for 64-bit systems. The subsystem is Native. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Native
Entry point 0x0000a0d8
Image base 0x0000000000010000

PE Sections:

Sections 8
Raw data 24064

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

.text 16896 bytes · 70.2% of section data
MD5 94407b7429e7bfd005f03f3864237365
.rdata 1024 bytes · 4.3% of section data
MD5 85bddc3f7ca16ae11b530ad0421c9ae3
.data 1024 bytes · 4.3% of section data
MD5 163f055589569820b30771daacb44ce9
.pdata 512 bytes · 2.1% of section data
MD5 3606e5487321985ebc7a8b92553233f0
PAGE 1024 bytes · 4.3% of section data
Uncommon name
MD5 a2a70d442fef4c08b99f552a9294f9ac
INIT 1536 bytes · 6.4% of section data
Uncommon name
MD5 db0d9c3358d24c85323fde14140949cd
.rsrc 1536 bytes · 6.4% of section data
MD5 720d0ec5ea28cc5fa0f78ca803efa7b5
.reloc 512 bytes · 2.1% of section data
MD5 3cf9510706f18d530a9ffabdcb3c39d2

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 38c20ebb2621a86a5e9729eda8f0f126.
  • 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.