GridinSoft Threat Intelligence

TeeDriverW8x64.sys file report

Under review File reputation report
MD5 f1e754deeb3369bcce2228d5c10de101
Latest seen 2026-02-25 23:00:36 (3 months ago)
First seen 2018-04-30 22:10:10 (8 years ago)
Size 201 KB
Publisher Intel Corporation
Product Intel(R) Management Engine Interface
Signed by Intel(R) Embedded Subsystems and IP Blocks Group

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-04-30 22:10:10 (8 years ago); latest analysis 2026-02-25 23:00:36 (3 months 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. 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

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 2026-02-25 23:00:36 (3 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.

File Details

Product Name: Intel(R) Management Engine Interface
Company Name: Intel Corporation
MD5: f1e754deeb3369bcce2228d5c10de101
Size: 201 KB
First Published: 2018-04-30 22:10:10 (8 years ago)
Latest Published: 2026-02-25 23:00:36 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-25 23:00:36 (3 months ago)

Overview

Signed By: Intel(R) Embedded Subsystems and IP Blocks Group
Status: Valid

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.

Common Places:

%appdata%\driverfinder\backup
%appdata%\uniblue\driverscanner\drivers\154832\me_corporate_win10_11.8.50.3426\windowsdriverpackages\mei\win10
%localappdata%\slimware utilities inc\slimdrivers\backups\20181025t160329309906\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20181025t161512831238\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20181025t161842737396\pci
%localappdata%\slimware utilities inc\driverupdate\backups\20180203t103645835\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t020619447489\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t021654859433\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t022812783705\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20180926t005633525833\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.

Geographic signal

Observed country distribution

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

Top country Brazil
Share 25.0%
Low High activity

The strongest geographic signal for this file is Brazil with 25.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 81.8%
Windows 8.1 15.2%
Windows 7 3.0%

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

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 0x00024014
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 185856

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

.text 146944 bytes · 79.1% of section data
MD5 9f0313488588bfa5c25cc35e5b835c56
.rdata 9216 bytes · 5.0% of section data
MD5 ea55027508fdf69aafd45c6f244c77be
.data 1024 bytes · 0.6% of section data
MD5 50863f52e48430ae82458a5af89d3ea7
.pdata 4096 bytes · 2.2% of section data
MD5 82e3d639223a981f98642354951e9d25
.gfids 512 bytes · 0.3% of section data
Uncommon name
MD5 1cf2856b26691be80e10679aee1138e4
PAGE 12800 bytes · 6.9% of section data
Uncommon name
MD5 b13d00a4b25678a1de79180309852c13
INIT 2560 bytes · 1.4% of section data
Uncommon name
MD5 8528c58b41d894fd210f440ccbae6fe9
.rsrc 8192 bytes · 4.4% of section data
MD5 d864e9dbd624f860b049664c5930bd79
.reloc 512 bytes · 0.3% of section data
MD5 ad308344e435ceb6ab0b24701cce2308

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