GridinSoft Threat Intelligence

btath_flt.sys file report

Clean record File reputation report
MD5 65dd42a358451920a703eeec1ab4995b
Latest seen 2022-04-22 23:27:02 (4 years ago)
First seen 2018-01-11 20:08:59 (8 years ago)
Size 87 KB
Publisher Qualcomm Atheros
Product Blue Manager
Signed by Qualcomm Atheros

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-01-11 20:08:59 (8 years ago); latest analysis 2022-04-22 23:27:02 (4 years ago).

Publisher context

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

Digital signature

Signed by Qualcomm Atheros. 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.

File context

btath_flt.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:27:02 (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.

File Details

Product Name: Blue Manager
Company Name: Qualcomm Atheros
MD5: 65dd42a358451920a703eeec1ab4995b
Size: 87 KB
First Published: 2018-01-11 20:08:59 (8 years ago)
Latest Published: 2022-04-22 23:27:02 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-04-22 23:27:02 (4 years ago)

Overview

Signed By: Qualcomm Atheros
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.

Common Places:

%programfiles%\drivertoolkit\download\720bdb5aa2d2f242042a15c7e6f86940\bluetooth_atheros_8.0.1.340\bt_driveronly
%localappdata%\slimware utilities inc\slimdrivers\backups\20181108t012021307714\bthenum
%programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows7-x64
%localappdata%\slimware utilities inc\slimdrivers\backups\20191227t205757779767\bthenum
%localappdata%\slimware utilities inc\slimdrivers\backups\20180122t203448791978\bthenum

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

Top country Germany
Share 33.3%
Low High activity

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

OS Version:

Windows 7 83.3%
Windows 8.1 16.7%

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

btath_flt.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 0x00019104
Image base 0x0000000000010000

PE Sections:

Sections 8
Raw data 80896

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

.text 50688 bytes · 62.7% of section data
MD5 a6ee30b9de21c6288eb5c9acbcb5a293
.rdata 22016 bytes · 27.2% of section data
MD5 db77f8afd8b8ceeecff135f61e5b6a63
.data 1024 bytes · 1.3% of section data
MD5 3b20d3e1b03318b77927772c2fdf40e8
.pdata 2048 bytes · 2.5% of section data
MD5 301310f5fa92eaa9cfc49f1c2d495b9d
PAGE 512 bytes · 0.6% of section data
Uncommon name
MD5 ba488e6ab148ccc80573a6743cb07a5f
INIT 2048 bytes · 2.5% of section data
Uncommon name
MD5 0bb6ad31508e08b0085170a9e86ccb7a
.rsrc 1024 bytes · 1.3% of section data
MD5 f27f7e6b2bc2d24ad1cd6dba50b8f2a0
.reloc 1536 bytes · 1.9% of section data
MD5 bd83856188a165cf3b7a7d89e68ae782

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 65dd42a358451920a703eeec1ab4995b.
  • 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.