GridinSoft Threat Intelligence
btath_rcp.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-11-13 09:14:17 (8 years ago); latest analysis 2022-04-22 23:38:05 (4 years ago).
Company metadata: Qualcomm Atheros. Product metadata: Blue Manager.
Signed by Qualcomm Atheros. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
btath_rcp.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:38:05 (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: | 859a116d748fba603af94c251dc5cf97 |
| Size: | 134 KB |
| First Published: | 2017-11-13 09:14:17 (8 years ago) |
| Latest Published: | 2022-04-22 23:38:05 (4 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2022-04-22 23:38:05 (4 years ago) |
Overview
| Signed By: | Qualcomm Atheros |
| Status: | Valid |
The signature on btath_rcp.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:
| %programfiles%\drivertoolkit\backup\bluetooth-avrcp-device-8.0.0.230 |
| %programfiles%\drivertoolkit\download\720bdb5aa2d2f242042a15c7e6f86940\bluetooth_atheros_8.0.1.340\bt_driveronly |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20170930t230945439381\bthenum |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20170930t230041220796\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\windows8.1-x64 |
| %programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows8-x64 |
| %programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows7-x64 |
ThreatInfo has observed btath_rcp.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_rcp.sys across 9 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Kyrgyzstan with 15.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for btath_rcp.sys is Windows 8.1 with 47.4% 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_rcp.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
7d96061bb83eb3aeb6a130bbec60581a
d678ea8218ad9f886ab090aad3069874
0e78dab67e2b22d3b478197b7b5b323f
ae9e2dbd2c6ea0d59da11c689ca608d3
ca32080f1d2eaea31f98897d914df5c4
0b39f34c165ae46977630313cf28f8e9
f0ad952efab632604d432fb501c3638b
82d8a8b07badc71585f87e200954f7e3
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.