GridinSoft Threat Intelligence
bcbtums.sys file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2020-12-26 19:54:27 (5 years ago); latest analysis 2023-04-02 23:12:08 (3 years ago).
Company metadata: Broadcom Corporation.. Product metadata: Bluetooth Software.
Signed by Broadcom Corporation;Microsoft Windows Hardware Compatibility Publisher. 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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
bcbtums.sys is a Windows file recorded in the ThreatInfo database. It is associated with Bluetooth Software. The reported company name is Broadcom Corporation.. The current detection status is Undefined, based on the latest analysis from 2023-04-02 23:12:08 (3 years 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.
File Details
| Product Name: | Bluetooth Software |
| Company Name: | Broadcom Corporation. |
| MD5: | 6d41c9cfad59f5fd46ae71a12d50f1d2 |
| Size: | 212 KB |
| First Published: | 2020-12-26 19:54:27 (5 years ago) |
| Latest Published: | 2023-04-02 23:12:08 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2023-04-02 23:12:08 (3 years ago) |
Overview
| Signed By: | Broadcom Corporation;Microsoft Windows Hardware Compatibility Publisher |
| Status: | Valid |
The signature on bcbtums.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:
| %localappdata%\slimware utilities inc\driverupdate\backups\20201226t140351098877\usb |
| %commonappdata%\outbyte\driver updater\2.x\temp |
ThreatInfo has observed bcbtums.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 bcbtums.sys across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Poland with 66.7% 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 bcbtums.sys is Windows 7 with 66.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
bcbtums.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.
fd26702dccd0c236e838caa901edd4ed
2dd3c44ac832ba57da6b510d2e5dbbef
08c78ee668fa0fa3aa469150a4c5cf74
32a5408edc4e170d642faf9e8ba18a8f
015001d38f968bea3a786c52c8116223
717e3691b4468271863053122dd17257
9ba8f77ee2ec301a3887e5897092a6a0
250f0d73aa37a49ed96e1b32b4724629
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.