Apple will reportedly try to succeed where Humane failed (miserably). On Wednesday, The Information reported that the iPhone maker is working on an AI pin. The wearable is said to resemble a slightly thicker AirTag and include multiple cameras, a speaker, microphones, and wireless charging.

The report coincides with another from Bloomberg that claims that Apple will revamp Siri as a ChatGPT-style chatbot. When combined with the recent announcement that Google's Gemini will power Siri AI, it looks like the company is finally making a more defined play for a piece of the generative AI pie. On the other hand, the wearable pin is reportedly only in the very early stages and could still be canceled.

The pin is described as a thin, flat, circular disc with an aluminum and glass exterior. It includes two cameras (standard and wide-angle) for taking photos and videos of the user's surroundings. It also has three microphones. It includes a speaker and a physical button along one edge. It has a magnetic inductive charging interface, similar to the Apple Watch's charging mechanism.

Given the way Apple markets itself as a privacy-focused company, it will be interesting to see how the company pitches the public on what sounds like an incognito recording device. Although on that note, the App Store still hosts the Grok app, which egregiously violates privacy by generating nearly-nude deepfakes of real people — despite Apple's rules explicitly prohibiting such apps.

The Information says Apple could release its AI pin as early as 2027. The company sounds confident in the device's appeal, as it reportedly plans to produce around 20 million units at launch.

Now would be a good time to update all your Bluetooth audio devices. On Thursday, Wired reported on a security flaw in 17 headphone and speaker models that could allow hackers to access your devices, including their microphones. The vulnerability stems from a faulty implementation of Google's one-tap (Fast Pair) protocol.

Security researchers at Belgium's KU Leuven University Computer Security and Industrial Cryptography group, who discovered the security hole, named the flaw WhisperPair. They say a hacker within Bluetooth range would only require the accessory's (easily attainable) device model number and a few seconds.

"You're walking down the street with your headphones on, you're listening to some music. In less than 15 seconds, we can hijack your device," KU Leuven researcher Sayon Duttagupta told Wired. "Which means that I can turn on the microphone and listen to your ambient sound. I can inject audio. I can track your location." The researchers notified Google about WhisperPair in August, and the company has been working with them since then.

Fast Pair is supposed to only allow new connections while the audio device is in pairing mode. (A proper implementation of this would have prevented this flaw.) But a Google spokesperson told Engadget that the vulnerability stemmed from an improper implementation of Fast Pair by some of its hardware partners. This could then allow a hacker's device to pair with your headphones or speaker after it's already paired with your device.

"We appreciate collaborating with security researchers through our Vulnerability Rewards Program, which helps keep our users safe," a Google spokesperson wrote in a statement sent to Engadget. "We worked with these researchers to fix these vulnerabilities, and we have not seen evidence of any exploitation outside of this report's lab setting. As a best security practice, we recommend users check their headphones for the latest firmware updates. We are constantly evaluating and enhancing Fast Pair and Find Hub security."

The researchers created the video below to demonstrate how the flaw works

In an email to Engadget, Google said the steps required to access the device’s microphone or audio are complex and involve multiple stages. The attackers would also need to remain within Bluetooth range. The company added that it provided its OEM partners with recommended fixes in September. Google also updated its Validator certification tool and its certification requirements.

The researchers say that, in some cases, the risk applies even to those who don't use Android phones. For example, if the audio accessory has never been paired with a Google account, a hacker could use WhisperPair to not only pair with the audio device but also link it to their own Google account. They could then use Google's Find Hub tool to track the device's (and therefore your) location.

Google said it rolled out a fix to its Find Hub network to address that particular scenario. However, the researchers told Wired that, within hours of the patch’s rollout, they found a workaround.

The 17 affected devices are made by 10 different companies, all of which received Google Fast Pair certification. They include Sony, Jabra, JBL, Marshall, Xiaomi, Nothing, OnePlus, Soundcore, Logitech and Google. (Google says its affected Pixel Buds are already patched and protected.) The researchers posted a search tool that lets you see if your audio accessories are vulnerable.

In a statement sent to Engadget, OnePlus said it's investigating the issue and "will take appropriate action to protect our users' security and privacy." Marshall said it patched the issue in November and is working with Google to avoid similar issues in the future (see full statement below). We also contacted the other accessory makers and will update this story if we hear back.

The researchers recommend updating your audio devices regularly. However, one of their concerns is that many people will never install the third-party manufacturer's app (required for updates), leaving their devices vulnerable.

The full report from Wired has much more detail and is worth a read.

Update, January 15 2026, 4:04PM ET: “We can confirm that Marshall has issued the necessary firmware updates and security patches to address the headphones potentially affected,” a company representative told Engadget. “These updates have been available since November and have been offered to all users since then. While this is an industry-wide issue, we take it seriously and are working closely with Google to reduce the risk of similar vulnerabilities in the future.”