GridinSoft Threat Intelligence

TeeDriverW8x64.sys file report

Under review File reputation report
MD5 0ac256421b38cef110fd2c6a22421e65
Latest seen 2024-11-11 23:00:51 (2 years ago)
First seen 2019-08-03 05:26:35 (6 years ago)
Size 201 KB
Publisher Intel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-08-03 05:26:35 (6 years ago); latest analysis 2024-11-11 23:00:51 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Management Engine Interface.

Digital signature

Signed by Intel(R) Embedded Subsystems and IP Blocks Group;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.

TeeDriverW8x64.sys is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Management Engine Interface. The reported company name is Intel Corporation. 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.

Product Name: Intel(R) Management Engine Interface
Company Name: Intel Corporation
MD5: 0ac256421b38cef110fd2c6a22421e65
Size: 201 KB
First Published: 2019-08-03 05:26:35 (6 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)

The signature on TeeDriverW8x64.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.

%localappdata%\slimware utilities inc\slimdrivers\backups\20190225t124548323122\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20190225t122925901861\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20181205t171123481558\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20181102t171421878921\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20190624t050442920191\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20191112t201706457656\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20171117t182721663389\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20171117t181216625182\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20211028t211155307087\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20180304t184618844900\pci

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

Windows 10 100.0%

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

TeeDriverW8x64.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 0x00023f24
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 185344

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

.text 146432 bytes · 79.0% of section data
MD5 7d8b0bf4c0652cd0ad857a38737a30b6
.rdata 9216 bytes · 5.0% of section data
MD5 3e5c5dfaa8d599f07290125a4ec36e97
.data 1024 bytes · 0.6% of section data
MD5 91befc33a510f405b163f00d9cf03883
.pdata 4096 bytes · 2.2% of section data
MD5 711fe50eec73993c43e1686c6cbb0a44
.gfids 512 bytes · 0.3% of section data
Uncommon name
MD5 64d1f04ee674327483852f238bb2c4a5
PAGE 12800 bytes · 6.9% of section data
Uncommon name
MD5 b229caa66aceda4057d4b17ff669bfea
INIT 2560 bytes · 1.4% of section data
Uncommon name
MD5 25f6a7022f5c4c71b5d2d692f2489781
.rsrc 8192 bytes · 4.4% of section data
MD5 fce428f8b38a141365326dc01f6da955
.reloc 512 bytes · 0.3% of section data
MD5 ec9c9a5dcc4f7c68b6b03414f8781a72

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 0ac256421b38cef110fd2c6a22421e65.
  • 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.