📱

Get Our Mobile App

Take your business learning on the go!

Download on the App StoreGet it on Google Play

Police Warning: Turn Off THIS Bluetooth Setting NOW

Mobile Alert23:50

Transcription

This went live two days ago, and the tech world is still processing it. A vulnerability that has existed inside every Bluetooth-enabled device since 2014, phones, laptops, earbuds, smartwatches, has just been formally documented by the FBI's cyber division. And the advisory they released is one of the most serious consumer warnings they have ever published. The setting they are telling you to disable is one you have never once been warned about. Until now.

And before you assume this is one of those videos that builds up to something obvious, before you assume you already know what this is about, I need you to stay with me for the next few minutes because what I am about to show you is not what you think it is. This is not about public Wi-Fi. This is not about phishing emails. This is not about weak passwords. This is about a radio signal your phone is emitting right now in your pocket, in your bag, on your desk. A signal that most people do not even know exists, that has been exploited by criminals, documented by researchers, flagged by governments, and is actively being used at this exact moment in cities across the world to surveil, track, and steal from ordinary people who did absolutely nothing wrong except leave one setting turned on.

So, let's start at the beginning. Let's start with what Bluetooth actually is. Not what you think it is, but what it actually is at a technical level. Because once you understand how it works under the hood, everything else I'm going to tell you will make immediate visceral sense.

Bluetooth is a short-range wireless communication protocol. It operates on the 2.4 GHz radio frequency band, the same band as your microwave oven, the same band as most Wi-Fi routers, the same band as baby monitors and cordless phones. Was developed in the late 1990s by a Swedish engineer at Ericsson named Jaap Haartsen. And it was named after a 10th-century Danish king Harald Bluetooth, who was famous for uniting warring tribes. The metaphor was intentional. Bluetooth was designed to unite devices, to make them talk to each other seamlessly without cables. And in that narrow mission, it succeeded brilliantly.

But the security architecture behind it, the decisions made about how devices was would identify themselves, how they would advertise their presence, how they would handle trust, those decisions were made in a different era, an era before smartphones, an era before everyone carried a computer in their pocket everywhere they went, an era before criminal organizations had cybersecurity divisions, and we are still living with those decisions today.

Here is the fundamental thing you need to understand about how Bluetooth works. When Bluetooth is enabled on your device, not when you are actively connected to something, not when you're pairing, just when it is turned on and sitting in the background, your device enters what the protocol calls an advertising state. In this state, your device broadcasts a packet of information into the surrounding air at regular intervals. This packet contains your device's MAC address, a unique hardware identifier assigned to your specific Bluetooth chip. It contains information about what kind of device you are. It contains information about what services you support. And depending on your device settings and your operating system, it may also contain your device name, which for millions of people is something like John's iPhone or Sarah's Galaxy S24, broadcasting your first name to every Bluetooth scanner within range, continuously, without pause, for as long as Bluetooth is switched on.

This advertising process is not a bug. It is not a flaw in the implementation. It is a feature. It is how Bluetooth is supposed to work. Devices need to announce themselves as so that other devices can find them. The problem is not the feature itself. The problem is that this feature was designed for a world where Bluetooth scanning required specialized hardware, where the range was limited, where the cost of building Geo Rogue scanner was prohibitive for anyone except large institutions. That world no longer exists. The hardware required to scan for Bluetooth advertising packets, to sit in a public space and silently log every device that comes within range, costs less than $30. It fits in a jacket pocket. It runs on batteries. It requires no technical expertise to operate. You can buy it on Amazon and have it delivered tomorrow. And with a free software tool downloaded from GitHub, you can be logging Bluetooth device identifiers from every phone, laptop, and smart watch within a 100-ft radius within about 15 minutes of unboxing it. That is the attack surface. That is what law enforcement is now formally warning about.

And it gets significantly worse when you understand what attackers can actually do with this information. The most immediate and documented threat is tracking. Physical, real-world tracking of individual people using their Bluetooth MAC address as a fingerprint. The way an attacker or a retail analytics company, or a stalker, because this technology does not care who is holding it, places Bluetooth scanners at multiple fixed locations, as a parking lot entrance, a shopping mall quarter, a train station platform, a street corner. Each scanner logs every Bluetooth MAC address it sees along with a timestamp. When the same MAC address appears at multiple scanners, the system can reconstruct that person's physical movement through space with startling precision without ever touching their device, without ever interacting with them, without them ever knowing it happened.

This is not theoretical. This has been documented. In 2018, researchers at the University of California published a paper demonstrating exactly this kind of tracking in a real urban environment. In 2019, a security conference presentation showed how a network of low-cost Bluetooth sniffers could track individuals across a college campus with accuracy exceeding 90%. And in 2022, court documents from a federal stalking case in the United States revealed that the defendant had used to your said commercially available Bluetooth scanning hardware to track his victim's movements for over 4 months without her knowledge. 4 months. Using a device he bought online, using a feature on her phone that she had never once thought about.

Now, some of you may have heard that modern smartphones, particularly iPhones running iOS 14 and above, and Android devices running more recent versions have implemented something called MAC address randomization. This is a real feature and it was introduced specifically to address the tracking problem. Instead of always broadcasting the same hardware MAC address, the phone periodically rotates to a randomized address making it harder to build a persistent fingerprint. And this is genuinely good. This was the right move. But here is the part that most people do not know and here is the part that makes the FBI's recent advisory so significant. MAC randomization does not solve the problem. It reduces it. It does not eliminate it. The reason is that MAC address is only one of several identifiers that Bluetooth advertising packets contain. Researchers have demonstrated that devices can be re-identified even with randomized MACs by analyzing other stable characteristics s of their advertising packets. The timing intervals between broadcasts, the specific combination of services advertised, the signal strength patterns, the manufacturer specific data fields that many apps and operating systems embed in advertising packets. These characteristics form what research errors call a behavioral fingerprint and unlike a MAC address, you cannot rotate a behavioral fingerprint. It is intrinsic to the device and the software stack running on it. A 2020 uh paper from the University of California, San Diego demonstrated that they could re-identify smartphones with randomized MA C addresses with accuracy rates above 95% using only these passive packet characteristics. 95% with randomized addresses using passive scanning that leaves zero trace on the target device. So, the privacy protection you thought you had is significantly weaker than you were led to believe. And the companies that built these systems, Apple, Google, the chipset manufacturers, they know this. The research is published, the papers are public, the vulnerability is documented, and yet here we are.

But tracking is just the beginning because Bluetooth is not only an advertising protocol, it is a communication protocol. And when it is used to establish actual connections, the attack surface expands dramatically. Let's talk about what security researchers call bluesnarfing. This is an attack that exploits vulnerabilities in the object push profile and the OBEX protocol, two Bluetooth standards that govern how devices exchange files and data. In a successful bluesnarfing attack, an attacker gains unauthorized access to information on a target device. Contacts, calendar entries, emails, text messages, without the user's knowledge or consent and without the user needing to accept any connection request. The device thinks it is doing a routine Bluetooth operation. The user sees nothing. The data leaves the phone silently.

Bluesnarfing was first documented in 2003 by security researcher Adam Laurie. He demonstrated it live at a security conference and the response from the mobile industry was essentially, "This is a theoretical vulnerability. The conditions required to exploit it in the real world are too specific to be a practical threat." That was 2003. In 2004, a German security researcher named Martin Herfurt demonstrated a related attack called Bluebug, which went further. Not only reading data from the device, but using it to make phone calls, send text messages, and access mobile services, all without the victim's knowledge. Still, the industry response was muted. Still, the underlying vulnerabilities in the protocol were not fundamentally addressed. And over the following two decades, as Bluetooth became embedded in every device on Earth, as billions more attack surfaces came online, the researchers kept finding new variants, new exploits, new ways to weaponize the same fundamental architectural weaknesses.

In 2017, a security firm called Armis published research on a suite of eight Bluetooth vulnerabilities they collectively named BlueBorne. BlueBorne was different from everything that came before it because it required no pairing, no connection request, no user interaction of any kind. An attacker within range could take complete control of a device, not just read data, full REMA, OTA code execution, simply because Bluetooth was enabled. The attack propagated through the air. It jumped between devices without any human action. Armis estimated that at the time of publication, BlueBorne affected over 5 billion devices worldwide. 5 billion. And the vector was simply Bluetooth was on. Microsoft, Google, Apple, and Linux all issued patches within weeks. But here is the uncomfortable reality about patches. They only protect the devices that receive them. As of 2024, there are estimated to be over 15 billion active Bluetooth devices in the world. Billions of those devices, older Android phones, IoT devices, cheap wireless earbuds, smart home gadgets, Connie, heck, did car systems are running firmware that has never been updated and will never be updated because the manufacturers no longer support them. Those devices are still out there, still broadcasting, still vulnerable to exploits that were publicly documented years ago.

And then in 2019, researchers at the École Polytechnique Fédérale de Lausanne published their findings on what they called the KNOB attack, key negotiation of Bluetooth. This one hit differently because it did not target a specific implementation or a specific device. It targeted the Bluetooth core specification itself, the foundation. A low standard that every Bluetooth device on Earth is required to implement. The KNOB attack exploits the way Bluetooth negotiates the encryption key length between two connecting devices. The spec allows for key lengths between 1 byte and 16 bytes. 1 byte of encryption is essentially no encryption. It can be brute-forced in milliseconds. And the protocol, as written, allows a man-in-the-middle attacker to silently force both devices to negotiate down to the minimum key length without either device detecting that anything unusual has happened. Both devices proceed with a connection believing they have established secure encrypted communication. They have not. The attacker can decrypt everything in real time. The Bluetooth Special Interest Group, the organization that governs the Bluetooth standard, issued an advisory acknowledging the vulnerability. They updated the spec to require a minimum key length of 7 bytes, which is minuscule and saw kingfully better than one, but still considered weak by modern cryptographic standards. But again, the device is already deployed in the world, the billions of devices running old firmware still implement the old spec, still vulnerable, still in people's pockets and homes and cars.

Now I want to talk about something that has received far less media coverage, but is in some ways the most immediately practical threat for most people watching this. And that is Bluetooth-based relay attacks on keyless entry systems, specifically car theft. Modern keyless entry systems, the kind where you just walk up to your car and it unlocks because your key fob is in your pocket, use a form of short-range radio communication that overlaps significantly with Bluetooth and its architecture and vulnerabilities. Your key fob is constantly broadcasting a low-power signal. Your car is constantly listening for that key hat signal. When the car detects the fob within a certain range, it unlocks. Simple, convenient, elegant, and catastrophically easy to defeat with a relay attack.

Here is how it works. Two attackers coordinate. One stands near your house, your office, your gym, wherever your key fob is. The other stands next to your car in the parking lot. The first attacker uses a relay device to capture your key fob signal and transmit it to the second attacker's device in real time. The second attacker's device re-broadcasts that signal next to your car. The car thinks the key fob is right there. It unlocks. They drive away. Start to finish, this takes under 20 seconds. No physique or caliber can no broken windows, no alarm triggered, no evidence. And the hardware required, widely available, openly sold, used, and documented in criminal cases across the UK, Germany, the United States, Canada, and Australia. The UK's National Police Chiefs' Council issued a formal advisory on relay attacks in 2022. They noted a direct correlation between the rise in keyless car theft and the proliferation of cheap relay hardware. In London alone, relay-assisted vehicle theft increased by over 200% between 2019 and 2023. 200%. And the countermeasures the manufacturers have put in place, motion sensors and key fobs, ultra-wideband positioning systems in newer vehicles, are effective only in the cars that have them, which is a small fraction of the total fleet on the road today.

So, we have passive tracking through advertising packets. We have data theft through legacy protocol vulnerabilities. We have full device compromise through unpatched firmware. We have NCR encryption downgrade attacks through spec level flaws. We have physical vehicle theft through relay exploitation. And all of it, every single one of these attack vectors, requires one thing, Bluetooth being on. That is the common thread. That is the attack surface. No Bluetooth signal, no attack.

This is why the FBI advisory matters, because the FBI does not issue consumer hardware advisories casually. Their cyber division is focused on nation-state threats, ransomware operations, critical infrastructure attacks. When they turn their attention to a consumer protocol and issue a formal public warning, telling ordinary people to change a specific setting on their personal devices, it is because the threat has crossed a threshold. It is because the exploitation is no longer confined to research papers and conference presentations. It is operational. It is widespread. It is happening to real people in real cities right now. And the specific setting they flagged, the setting at the center of this entire threat landscape, is not Bluetooth itself. They're not telling you to permanently disable Bluetooth. They're not telling you to go back to wired and cable fill e-transfers. What they are telling you is to turn off Bluetooth discoverability when you are not actively using it, to disable Bluetooth entirely in public environments where you have no active use for it, and critically, to audit the applications on your device that have been granted Bluetooth permissions.

Because this is where the story gets a dimension that almost no one is talking about. Applications on your phone, apps you downloaded months or years ago, apps you use regularly, apps you may have forgotten about, can request Bluetooth access. And on both iOS and Android, Bluetooth permission has historically been one of the most loosely governed permissions in the entire system. On older versions of Android, an app with Bluetooth access could scan for nearby devices without any additional permissions. No location permission required, even though the data it was collecting was functionally equivalent to location data. This was a known issue. Researchers flagged it. Google had addressed it partially in Android 12, requiring apps that scan for Bluetooth devices to declare a location permission. But, the apps already installed on older devices, the apps running on the billions of Android phones that have not been updated to Android 12 or above, those apps can still do it silently in the background every time you open them.

Think about the scope of this for a moment. There are applications on the Google Play Store that have been downloaded over a billion times. Retail apps. Loyalty, see, already apps, navigation apps, social media apps. Many of them have Bluetooth permissions. And what they are doing with that access, what data they are collecting, how long they are retaining it, who they are selling it to, is buried in privacy policies that no one reads, written in legal language designed to obscure rather than illuminate, and governed by regulations that vary wildly between jurisdictions and change slower than technology evolves. A 2021 investigation by The Markup found that dozens of popular Android apps were using Bluetooth scanning to build location profiles of their users without those users ever granting location permission. They were not asking where you were. They were asking who your Bluetooth neighbors were, i.e., which devices were near you, and then cross-referencing those device identifiers against databases of known device locations to infer where you were with high precision. No GPS, no cell tower triangulation, just Bluetooth. The data was being sold to data brokers who sold it to advertisers who used it to serve you targeted ads based on the physical locations you had visited. The coffee shop you stopped at on Tuesday, the hospital you visited on Thursday, the political rally you attended on Saturday, all inferred, all sold, all happening because you had Bluetooth on and an app had permission to use it.

Now, let me give you the practical information because everything I have told you is important context, but context without action is just anxiety, and that is not why you are here.

The first thing you need to do right now today before you close this video is go into your Bluetooth settings and check your discoverability status. On iPhone, open settings, go to Bluetooth. If Bluetooth is on and you are not actively connected to a device, your phone is already in a limited advertising mode. Apple has done a reasonable job of restricting persistent discoverability on iOS, but it is not zero exposure. The more important action on iPhone is to go to settings, then privacy and security, then Bluetooth, and audit every single app that has been granted Bluetooth access. Go through that list. For every app that does not have an obvious, immediate reason to need Bluetooth, a retail app, a game, a social media app, a news reader, revoke the permission. Tap the app, switch Bluetooth to off. Do this now. This is not optional. This is hygiene.

On Android, open settings, go to connected devices or connections, depending on your manufacturer, then Bluetooth. Go into the advanced settings or additional settings and look for device visibility or discoverability. Make sure it is set to not visible or hidden when you are not actively pairing. Then go to settings, apps, and for each app, go to permissions and check Bluetooth. Same process. Revoke it from anything that does not have a clear and immediate need for it. If you are running Android 12 or above, you have finer-grained control over oh oh over which apps can scan for nearby devices versus which apps can connect to paired devices. Use that distinction. Scanning permission is the dangerous one. Revoke scanning from everything except apps that genuinely require it.

The second thing, and this is behavioral rather than technical, stop leaving Bluetooth on when you are not using it. I understand this feels inconvenient. I understand you are used to your PH-1 automatically connecting to your car when you get in, to your earbuds when you take them out of the case, to your smartwatch throughout the day. But the threat model has changed. In e-environments where you have no active use for Bluetooth, walking through an airport, sitting on public transit, moving through a shopping center, attending a large event, the radio silence of Bluetooth off being off is worth more than the convenience of automatic connection. It takes 3 seconds to turn it on when you need it. It takes a criminal with a $30 device 8 seconds to capture your device fingerprint when you leave it on. The math is straightforward.

The third thing, if you own a car with keyless entry, take the relay attack threat seriously. The simplest countermeasure costs about $10. A signal blocking pouch, often called a Faraday pouch or cage, lined with metallic fabric that blocks radio signals completely. Put your key fob in it when you're not driving. The signal cannot escape the pouch. The relay device has nothing to capture. The attack cannot happen. This is low-tech. It is low-cost and it works. Some manufacturers also offer key fob covers with built-in signal blocking. And if your fob has a motion sensor option, some Volkswagen and BMW key fobs have this, enable it. When the fob detects it has not moved for a set period, it stops broadcasting until you physically pick it up.

The fourth thing, update your devices. I know you have heard this before. I know it sounds like generic advice. But in the context of Bluetooth specifically, firmware are the only mechanism by which the patched versions of these vulnerabilities, BlueBorne, KNOB, and the dozens of others that have been discovered and are being discovered right now, reach your device. If your phone manufacturer is still issuing security updates, install them immediately. If your phone is old enough that the manufacturer has stopped issuing updates, that is a serious consideration in your next purchasing decision. An unpatched Android phone is not just personally vulnerable, it is a node in a potential propagation network for airborne Bluetooth exploits.

And the fifth thing, think about your wider device ecosystem. Your phone is the most obvious Bluetooth device you own, but it is probably not the only one. You, our laptop, your wireless earbuds, your smart watch, your smart TV, your wireless speaker, your connected car system, your wireless keyboard and mouse. Every one of these devices has a Bluetooth radio. Every one of them has a firmware stack that may or may not be up to date. Every one of them is advertising its presence. Whoosh. When Bluetooth is enabled, the attack surface is not one device. It is the entire constellation of connected hardware in your life. Go through it systematically. Disable Bluetooth on devices where you rarely use it. Update the firmware on devices that support updates. And for devices that cannot be updated, cheap IoT devices, old smart home hardware, seriously consider whether the convenience they provide is worth the attack surface they represent.

Here is the thing that I want you to sit with as we come to the end of this. The FBI did not issue this warning because Bluetooth is a new technology. They issued it because the exploitation of Bluetooth is newly industrialized. The same way that fishing went from a curiosity to a multi-billion dollar criminal industry. The same way that T ransomware went from a theoretical concept to the dominant form of organized cybercrime. Bluetooth exploitation is making that transition right now. The hardware is cheap. The software is free and openly available. The attack surface is everywhere. And the awareness is almost zero among ordinary people who are not following cybersecurity research. That asymmetry between how easy it is to exploit and how little most people know about it is exactly what makes a threat dangerous. And it is exactly what makes the FBI's decision to issue a public warning significant. They're not in the business of generating consumer anxiety. They're in the business of responding to documented operational widespread threats. And TS, they looked at the data on Bluetooth exploitation, the tracking cases, the data theft incidents, the vehicle theft statistics, the app permission abuse, the unpatched device population, and they decided the public needed to know.

Now you know. And knowing, as the saying goes, is the first step, but only the first step. Go into your settings today, revoke those app permissions, turn off discoverability, build the habit of switching Bluetooth off in public spaces, get a Faraday pouch for your key fob, update your firmware. These are not dramatic interventions. They are not expensive. They do not require technical expertise. They require about 20 minutes of your time and a small shift in how you think about the invisible radio environment surrounding you at all times. Because that environment is not neutral. It is not passive. It is being actively probed, cataloged, and exploited by people who understand it far better than most of their targets ever will. The only question is whether you are going to be one of those targets. Turn off the setting. Do it today.