L1C63x64.sys file report

MD5 d7b5e48c9c6582be234b5a8f6413b8cc
Latest seen 2021-01-15 07:24:51 (5 years ago)
First seen 2020-01-02 21:41:37 (6 years ago)
Size 158 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-02 21:41:37 (6 years ago); latest analysis 2021-01-15 07:24:51 (5 years ago).

Publisher context

Company metadata: Qualcomm Atheros, Inc.. Product metadata: Killer e2200 PCI-E Gigabit Ethernet Controller.

Digital signature

Signed by Rivet Networks LLC;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.

L1C63x64.sys is a Windows file recorded in the ThreatInfo database. It is associated with Killer e2200 PCI-E Gigabit Ethernet Controller. The reported company name is Qualcomm Atheros, Inc.. The current detection status is Undefined, based on the latest analysis from 2021-01-15 07:24:51 (5 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: Killer e2200 PCI-E Gigabit Ethernet Controller
Company Name: Qualcomm Atheros, Inc.
MD5: d7b5e48c9c6582be234b5a8f6413b8cc
Size: 158 KB
First Published: 2020-01-02 21:41:37 (6 years ago)
Latest Published: 2021-01-15 07:24:51 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-15 07:24:51 (5 years ago)

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

%commonappdata%\reviversoft\driver reviver\downloads\0d97f99e-6836-4a47-a908-dbf2743bd700
%commonappdata%\reviversoft\driver reviver\downloads\175
%localappdata%\slimware utilities inc\slimdrivers\backups\20200111t000322774471\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20191223t021833303584\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20201007t201927260947\pci
%localappdata%\slimware utilities inc\slimdrivers\backups\20201007t210044105988\pci

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

50.0%
33.3%
16.7%

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

Windows 10 100.0%

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

L1C63x64.sys is identified as pe for 64 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.

Subsystem: Native
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x00026124

PE Sections:

Name Size of data MD5
.text 120832 760e8d06e99c8b0bc9e885e97c1ab91e
.rdata 10240 49dd2acf180d6641e99a791eaf284336
.data 2560 3bcda36e5bf0c79487a4b7e4fbcc027a
.pdata 4608 b07cb5dc07110c8a05afc9c381c41b63
.gfids 512 e57c308021ec6875302727486b26bf8c
INIT 3584 8b8396d583c267e7838f532333b5538d
.rsrc 1024 89b40cb38a23726beb06ef67736e2796
.reloc 512 7e57f5e6df70f3b5de0bd83f197430bc

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.

More information: