GridinSoft Threat Intelligence

WirelessButtonDriver64.sys file report

Under review File reputation report
MD5 569fb3d619213f226cbb60f9cb8fe1bd
Latest seen 2024-12-27 23:01:41 (a year ago)
First seen 2019-07-09 16:09:17 (6 years ago)
Size 29 KB
Publisher HP

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-07-09 16:09:17 (6 years ago); latest analysis 2024-12-27 23:01:41 (a year ago).

Publisher context

Company metadata: HP. Product metadata: HP Wireless Button Driver.

Digital signature

Signed by HP Inc.;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.

WirelessButtonDriver64.sys is a Windows file recorded in the ThreatInfo database. It is associated with HP Wireless Button Driver. The reported company name is HP. The current detection status is Undefined, based on the latest analysis from 2024-12-27 23:01:41 (a year 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: HP Wireless Button Driver
Company Name: HP
MD5: 569fb3d619213f226cbb60f9cb8fe1bd
Size: 29 KB
First Published: 2019-07-09 16:09:17 (6 years ago)
Latest Published: 2024-12-27 23:01:41 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-12-27 23:01:41 (a year ago)

The signature on WirelessButtonDriver64.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\driverupdate\backups\20180129t060446230\acpi
%localappdata%\slimware utilities inc\driverupdate\backups\20180129t162132442\acpi
%localappdata%\slimware utilities inc\driverupdate\backups\20180129t163755819\acpi
%localappdata%\slimware utilities inc\driverupdate\backups\20180129t165033166\acpi
%localappdata%\slimware utilities inc\driverupdate\backups\20180129t172235368\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t015357560265\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t020619447489\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t022812783705\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20171204t021654859433\acpi
%localappdata%\slimware utilities inc\slimdrivers\backups\20180213t073951595498\acpi

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

WirelessButtonDriver64.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 0x00008000
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 13824

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

.text 6144 bytes · 44.4% of section data
MD5 463b732cd220e6bb96947c7ab260a58a
.rdata 2048 bytes · 14.8% of section data
MD5 23dd0741fed1f0a89f10b03e7b353263
.data 512 bytes · 3.7% of section data
MD5 482cd4de8e7f127a2903d70e95415896
.pdata 512 bytes · 3.7% of section data
MD5 0e3dca9b4fc4fd6ca47e251b580d46ca
.gfids 512 bytes · 3.7% of section data
Uncommon name
MD5 5f002fe8c14502edbf9f335948392949
PAGE 1536 bytes · 11.1% of section data
Uncommon name
MD5 b68a51d7b8a90444e9ade0d0635b388b
INIT 1024 bytes · 7.4% of section data
Uncommon name
MD5 3a11d06f79c0473ae4a1b2e80c7487da
.rsrc 1024 bytes · 7.4% of section data
MD5 5d7250775088094a06c660df0aae548c
.reloc 512 bytes · 3.7% of section data
MD5 43899e504a81c69b13a5a480bda72c8e

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 569fb3d619213f226cbb60f9cb8fe1bd.
  • 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.