GridinSoft Threat Intelligence

iaLPSS_I2C.sys file report

Under review File reputation report
MD5 7c0799f686e38ed6af0fc0df2c3de7ee
Latest seen 2023-06-07 23:03:29 (2 years ago)
First seen 2023-06-07 23:03:29 (2 years ago)
Size 147 KB
Publisher Intel Corporation
Product Intel(R) Serial IO Driver
Signed by Intel Corporation - Client Components Group;Microsoft Windows Hardware Compatibility Publisher

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-06-07 23:03:29 (2 years ago); latest analysis 2023-06-07 23:03:29 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Serial IO Driver.

Digital signature

Signed by Intel Corporation - Client Components 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.

File context

iaLPSS_I2C.sys is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Serial IO Driver. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-06-07 23:03:29 (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: Intel(R) Serial IO Driver
Company Name: Intel Corporation
MD5: 7c0799f686e38ed6af0fc0df2c3de7ee
Size: 147 KB
First Published: 2023-06-07 23:03:29 (2 years ago)
Latest Published: 2023-06-07 23:03:29 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-06-07 23:03:29 (2 years ago)

Overview

Signed By: Intel Corporation - Client Components Group;Microsoft Windows Hardware Compatibility Publisher
Status: Valid

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

%commonappdata%\outbyte\driver updater\2.x\temp

ThreatInfo has observed iaLPSS_I2C.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 iaLPSS_I2C.sys across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country French Polynesia
Share 100.0%
Low High activity

The strongest geographic signal for this file is French Polynesia 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 100.0%

The most common operating system signal for iaLPSS_I2C.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.

Analysis

iaLPSS_I2C.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 0x000150b0
Image base 0x0000000140000000

PE Sections:

Sections 8
Raw data 112128

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

.text 88576 bytes · 79.0% of section data
MD5 8174a23cc0c8b4830aff80282c2dfdfe
.rdata 4608 bytes · 4.1% of section data
MD5 a15329e89bf1d95b305e3881a0761055
.data 1024 bytes · 0.9% of section data
MD5 29925bb4548ec11fdac6de2a17d1beda
.pdata 2048 bytes · 1.8% of section data
MD5 4d9ccb5b33f6096fefc35437c63099ec
PAGE 1536 bytes · 1.4% of section data
Uncommon name
MD5 6f9c7d93515be38ff875d4726e461786
INIT 1536 bytes · 1.4% of section data
Uncommon name
MD5 59ba39d4a7a5b6dea269e4519894e784
.rsrc 12288 bytes · 11.0% of section data
MD5 089cdf94fbfa7ade0a267eff46429dc3
.reloc 512 bytes · 0.5% of section data
MD5 369f847316708858044e7bc5de3f1f09

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