GridinSoft Threat Intelligence
btath_hcrp.sys file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-01-11 20:09:00 (8 years ago); latest analysis 2022-04-22 23:35:13 (4 years ago).
Company metadata: Qualcomm Atheros. Product metadata: Blue Manager.
Signed by Atheros Communications Inc.. ThreatInfo marks this publisher as trusted for this record.
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_hcrp.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:35:13 (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: | 4af7c20f94dac343c01ed671c82dcb99 |
| Size: | 175 KB |
| First Published: | 2018-01-11 20:09:00 (8 years ago) |
| Latest Published: | 2022-04-22 23:35:13 (4 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2022-04-22 23:35:13 (4 years ago) |
Overview
| 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.
Common Places:
| %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-x64 |
| %programfiles%\drivertoolkit\download\26382971d4fdbba6c3becf5eb2e714fd\drivers\production\windows8.1-x64 |
| %localappdata%\slimware utilities inc\slimdrivers\backups\20150416t225554955650\bthenum |
ThreatInfo has observed btath_hcrp.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_hcrp.sys across 7 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 20.0% 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_hcrp.sys is Windows 7 with 46.7% 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_hcrp.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.
cc7904aef8525d6b15ca6748e557f1b9
eecb11de35d8c6d981951a1035741bf1
04f2b96cd1ed915eee422b7076a929e3
4e8ce8f44c5b1159543ae11a0d6939b3
5d8dbe8628a30849e3d036cdd690561e
f6b37e01db4321e41cb0dfe4f71929fb
e962d668a2769c7e0ac41379130ec846
87ef3eed1ae5a1b3af342ac0ff593ce5
6de6220cdbd202fb8ae6a7408cdc0e0a
6bdba808a47ac49a3eaa6db39e4f3ab4
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.