GridinSoft Threat Intelligence

btath_lwflt.sys file report

Clean record File reputation report
MD5 785c38070043beee9e9d591de4067244
Latest seen 2022-04-22 23:28:18 (4 years ago)
First seen 2018-01-11 20:08:56 (8 years ago)
Size 75 KB
Publisher Qualcomm Atheros
Product Blue Manager

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-01-11 20:08:56 (8 years ago); latest analysis 2022-04-22 23:28:18 (4 years ago).

Publisher context

Company metadata: Qualcomm Atheros. Product metadata: Blue Manager.

Digital signature

Signed by Atheros Communications Inc.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

btath_lwflt.sys is a Windows file recorded in the ThreatInfo database. It is associated with Blue Manager. The reported company name is Qualcomm Atheros. The current detection status is Clean, based on the latest analysis from 2022-04-22 23:28:18 (4 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Blue Manager
Company Name: Qualcomm Atheros
MD5: 785c38070043beee9e9d591de4067244
Size: 75 KB
First Published: 2018-01-11 20:08:56 (8 years ago)
Latest Published: 2022-04-22 23:28:18 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-04-22 23:28:18 (4 years ago)
Signed By: Atheros Communications Inc.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\drivertoolkit\download\720bdb5aa2d2f242042a15c7e6f86940\bluetooth_atheros_8.0.1.340\bt_driveronly
%localappdata%\slimware utilities inc\slimdrivers\backups\20170930t230041220796\bthenum
%localappdata%\slimware utilities inc\slimdrivers\backups\20170930t230945439381\bthenum
%localappdata%\slimware utilities inc\slimdrivers\backups\20181108t012021307714\bthenum
%localappdata%\slimware utilities inc\slimdrivers\backups\20160731t124311495331\bthenum
%localappdata%\slimware utilities inc\slimdrivers\backups\20160731t125156672838\bthenum
%programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows7-x64
%programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows8.1-x64
%programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows8-x64
%localappdata%\slimware utilities inc\slimdrivers\backups\20150416t225554955650\bthenum

ThreatInfo has observed btath_lwflt.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 8.1 50.0%
Windows 7 38.9%
Windows 10 11.1%

The most common operating system signal for btath_lwflt.sys is Windows 8.1 with 50.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.

btath_lwflt.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 0x00015144
Image base 0x0000000000010000

PE Sections:

Sections 8
Raw data 69632

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

.text 58880 bytes · 84.6% of section data
MD5 5fb0f7be04e7f37eaafd71952a95998a
.rdata 3072 bytes · 4.4% of section data
MD5 50a203197f237048d36308f90383bb99
.data 1024 bytes · 1.5% of section data
MD5 cac401a04fa91af47e6b2089b5574960
.pdata 2048 bytes · 2.9% of section data
MD5 1b5e764e19de7661df256971303a3179
PAGE 512 bytes · 0.7% of section data
Uncommon name
MD5 dd3a36ae70944ff070a96e9b98586bbd
INIT 2560 bytes · 3.7% of section data
Uncommon name
MD5 8b89c9d52c47dae4e924fd42540818e9
.rsrc 1024 bytes · 1.5% of section data
MD5 45d0afbd89b7329caa7e4b23a1b9a4de
.reloc 512 bytes · 0.7% of section data
MD5 2b39dfbb5f0e9228fce9d981fa985b47

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 785c38070043beee9e9d591de4067244.
  • 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.