{"id":25157,"date":"2026-01-21T15:44:50","date_gmt":"2026-01-21T11:44:50","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/?p=25157"},"modified":"2026-01-21T15:44:50","modified_gmt":"2026-01-21T11:44:50","slug":"whisperpair-blueooth-headset-location-tracking","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/whisperpair-blueooth-headset-location-tracking\/25157\/","title":{"rendered":"Are your Bluetooth headphones spying on you?"},"content":{"rendered":"<p>A newly discovered vulnerability named WhisperPair can turn Bluetooth headphones and headsets from many well-known brands into personal tracking beacons \u2014 regardless of whether the accessories are currently connected to an iPhone, Android smartphone, or even a laptop. Even though the technology behind this flaw was originally developed by Google for Android devices, the tracking risks are actually much higher for those using vulnerable headsets with other operating systems \u2014 like iOS, macOS, Windows, or Linux. For iPhone owners, this is especially concerning.<\/p>\n<p>Connecting Bluetooth headphones to Android smartphones became a whole lot faster when Google rolled out Fast Pair, a technology now used by dozens of accessory manufacturers. To pair a new headset, you just turn it on and hold it near your phone. If your device is relatively modern (produced after 2019), a pop-up appears inviting you to connect and download the accompanying app, if it exists. One tap, and you\u2019re good to go.<\/p>\n<p>Unfortunately, it seems quite a few manufacturers didn\u2019t pay attention to the particulars of this tech when implementing it, and now their accessories can be hijacked by a stranger\u2019s smartphone in seconds \u2014 even if the headset isn\u2019t actually in pairing mode. This is the core of the WhisperPair vulnerability, recently discovered by researchers at KU Leuven and recorded as <a href=\"https:\/\/nvd.nist.gov\/vuln\/detail\/CVE-2025-36911\" target=\"_blank\" rel=\"noopener nofollow\">CVE-2025-36911<\/a>.<\/p>\n<p>The attacking device \u2014 which can be a standard smartphone, tablet or laptop \u2014 broadcasts Google Fast Pair requests to any Bluetooth devices within a 14-meter radius. As it turns out, a long list of headphones from Sony, JBL, Redmi, Anker, Marshall, Jabra, OnePlus, and even Google itself (the Pixel Buds 2) will respond to these pings even when they aren\u2019t looking to pair. On average, the attack takes just 10 seconds.<\/p>\n<p>Once the headphones are paired, the attacker can do pretty much anything the owner can: listen in through the microphone, blast music, or \u2014 in some cases \u2014 locate the headset on a map if it supports Google Find Hub. That latter feature, designed strictly for finding lost headphones, creates a perfect opening for stealthy remote tracking. And here\u2019s the twist: it\u2019s actually most dangerous for Apple users and anyone else rocking non-Android hardware.<\/p>\n<h2>Remote tracking and the risks for iPhones<\/h2>\n<p>When headphones or a headset first shake hands with an Android device via the Fast Pair protocol, an owner key tied to that smartphone\u2019s Google account is tucked away in the accessory\u2019s memory. This info allows the headphones to be found later by leveraging data collected from millions of Android devices. If any random smartphone spots the target device nearby via Bluetooth, it reports its location to the Google servers. This feature \u2014 Google Find Hub \u2014 is essentially the Android version of Apple\u2019s Find My, and it introduces the same <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-find-airtag-and-other-location-trackers-on-android-2024\/51908\/\" target=\"_blank\" rel=\"noopener nofollow\">unauthorized tracking risks as a rogue AirTag<\/a>.<\/p>\n<p>When an attacker hijacks the pairing, their key can be saved as the headset owner\u2019s key \u2014 but only if the headset targeted via WhisperPair hasn\u2019t previously been linked to an Android device and has only been used with an iPhone, or other hardware like a laptop with a different OS. Once the headphones are paired, the attacker can stalk their location on a map at their leisure \u2014 crucially, anywhere at all (not just within the 14-meter range).<\/p>\n<p>Android users who\u2019ve already used Fast Pair to link their vulnerable headsets are safe from this specific move, since they\u2019re already logged in as the official owners. Everyone else, however, should probably double-check their manufacturer\u2019s documentation to see if they\u2019re in the clear \u2014 thankfully, not every device vulnerable to the exploit actually supports Google Find Hub.<\/p>\n<h2>How to neutralize the WhisperPair threat<\/h2>\n<p>The only truly effective way to fix this bug is to update your headphones\u2019 firmware, provided an update is actually available. You can typically check for and install updates through the headset\u2019s official companion app. The researchers have compiled a list of vulnerable devices on <a href=\"https:\/\/whisperpair.eu\/vulnerable-devices\" target=\"_blank\" rel=\"noopener nofollow\">their site<\/a>, but it\u2019s almost certainly not exhaustive.<\/p>\n<p>After updating the firmware, you absolutely must perform a factory reset to wipe the list of paired devices \u2014 including any unwanted guests.<\/p>\n<p>If no firmware update is available and you\u2019re using your headset with iOS, macOS, Windows, or Linux, your only remaining option is to track down an Android smartphone (or find a trusted friend who has one) and use it to reserve the role of the original owner. This will prevent anyone else from adding your headphones to Google Find Hub behind your back.<\/p>\n<h2>The update from Google<\/h2>\n<p>In January 2026, Google pushed an Android update to patch the vulnerability on the OS side. Unfortunately, the specifics haven\u2019t been made public, so we\u2019re left guessing exactly what they tweaked under the hood. Most likely, updated smartphones will no longer report the location of accessories hijacked via WhisperPair to the Google Find Hub network. But given that not everyone is exactly speedy when it comes to installing Android updates, it\u2019s a safe bet that this type of headset tracking will remain viable for at least another couple of years.<\/p>\n<blockquote><p>Want to find out how else your gadgets might be spying on you? Check out these posts:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/airtag-and-stalkerware-protection-on-android\/52652\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>How to protect yourself from Bluetooth stalking and more<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/protecting-from-tracking-via-findmy-airtag\/53245\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>How to track anyone via the Find My network<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-find-airtag-and-other-location-trackers-on-android-2024\/51908\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>How to stop being tracked via Bluetooth beacons like AirTag<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/disable-mobile-app-ad-tracking\/53096\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>How smartphones build a dossier on you<\/strong><\/a><\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-remove-yourself-from-data-brokers-people-search-sites\/54209\/\" target=\"_blank\" rel=\"noopener nofollow\"><strong>Why data brokers build dossiers on you, and how to stop them doing so<\/strong><\/a><\/li>\n<\/ul>\n<\/blockquote>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kisa-generic-3\">\n","protected":false},"excerpt":{"rendered":"<p>Breaking down the WhisperPair attack, which allows victims to be tracked via ordinary Bluetooth headphones.<\/p>\n","protected":false},"author":2722,"featured_media":25158,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1486],"tags":[2545,105,14,381,2226,22,1061,43,738,521,783],"class_list":{"0":"post-25157","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-airtag","9":"tag-android","10":"tag-apple","11":"tag-bluetooth","12":"tag-geolocation","13":"tag-google","14":"tag-ios","15":"tag-privacy","16":"tag-surveillance","17":"tag-threats","18":"tag-tracking"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/whisperpair-blueooth-headset-location-tracking\/25157\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/whisperpair-blueooth-headset-location-tracking\/30094\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/whisperpair-blueooth-headset-location-tracking\/29973\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/whisperpair-blueooth-headset-location-tracking\/28918\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/whisperpair-blueooth-headset-location-tracking\/30415\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/whisperpair-blueooth-headset-location-tracking\/41185\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/whisperpair-blueooth-headset-location-tracking\/14210\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/whisperpair-blueooth-headset-location-tracking\/55162\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/whisperpair-blueooth-headset-location-tracking\/23531\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/whisperpair-blueooth-headset-location-tracking\/24680\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/whisperpair-blueooth-headset-location-tracking\/30179\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/whisperpair-blueooth-headset-location-tracking\/35858\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/whisperpair-blueooth-headset-location-tracking\/35513\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/bluetooth\/","name":"Bluetooth"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/25157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2722"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=25157"}],"version-history":[{"count":1,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/25157\/revisions"}],"predecessor-version":[{"id":25159,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/25157\/revisions\/25159"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/25158"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=25157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=25157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=25157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}