Android 16

Android 16 Arrives with Protection Against Fake Cell Towers and Network Snooping

Mobile Security

Android 16: Your Phone's New Guardian Against Fake Cell Towers

In today's world, keeping our personal information safe can feel like a constant battle. We all know the basics: strong passwords, careful app permissions, and sticking to trusted app sources. But what about the threats we can't easily see? I'm talking about sophisticated attacks that can silently compromise your phone's security.

One such attack involves tricking your phone into connecting to a fake, insecure mobile network. It's like a wolf in sheep's clothing, and it can be incredibly difficult for the average person to detect. However, with the new Android 16 update, Google is giving us a powerful tool to fight back: a feature that warns you when someone is trying to snoop on you using this tactic. I think that it is a great feature that will bring more security to end users.

This kind of attack typically involves a device called a "stingray." An attacker will strategically place this device near their target, and it will then impersonate a legitimate cell tower. The stingray then tricks nearby phones into connecting to it, allowing the attacker to collect unique identifiers like your IMEI. Even worse, they can force your phone onto older, more vulnerable communication protocols. Imagine your phone being forced to use an outdated security system – that's what a stingray does.

While law enforcement agencies have been known to use "stingray" devices, these technologies can also fall into the wrong hands. While some say they're needed to track criminals, the potential for abuse is huge. They could be used to secretly gather data on ordinary people, which is something I find deeply concerning. Because of this, Google has been working on ways to protect Android users from this kind of surveillance.

Google has been steadily building up our defenses against these attacks. With Android 12, they introduced the ability to disable 2G connectivity. Later, Android 14 added support for disabling unencrypted connections. Now, Android 15 takes it a step further by alerting the OS when a network tries to grab your unique identifiers or force a new encryption algorithm. The goal is to directly counter the tactics used by stingrays, which often rely on downgrading connections to 2G or using no encryption at all, making your data an easy target.

It's a layered approach, and it's good to see Google taking these threats seriously. The problem is, making these features work requires updates to your phone's modem driver. The identifier request notification, for instance, needs a modem that supports version 3.0 of Android's IRadio hardware abstraction layer (HAL). This is why some security features are missing on current Pixel phones and other devices, and likely the reason why Google delayed the launch of the "mobile network security" settings page that was planned for Android 15.

The Android 16 Solution

However, there's good news on the horizon. Android 16 will require new devices to support version 3.0 of Android’s IRadio HAL, which means Google is bringing back the "mobile network security" settings page in the Safety Center (Settings > Security & privacy). This page will include two key features:

  • A toggle to disable 2G network protection
  • The "network notifications" feature

When enabled, the "Network notifications" feature will send you an alert whenever your phone switches between encrypted and unencrypted networks. It will also warn you if a network is trying to access your phone's unique identifiers, giving you details like the time and number of times the request was made.

The "Mobile network security" page will only appear on devices that support both features, explaining why current Pixel devices running Android 16 won't see it yet, as they lack the necessary modem support for notifications. Because of Google Requirements Freeze (GRF) program, current devices probably won't be updated to support the notifications feature. We'll likely have to wait for new phones launching with Android 16, like the Pixel 10 series, to see this protection in action.

Source: AndroidAuthority