At the beginning of November, we became aware of the existence of a small device called Flipper Zero, which has the capacity to block any iPhone model. Sending mass pop-ups that crash the system and cause the device to reboot. Apparently it still works after Apple’s latest software updates.

Although Apple released the beta version of iOS 17.1.1 and iOS 17.2 after the discovery of this major security vulnerability, Flipper Zero can still lock iPhone with these software updates.

It is a small, portable tool that is very popular in its field. hack allowing users changing access control systems and radio protocols. To protect yourself from the iOS 17 security breach, we explain how you can protect yourself from this attack.

How does Flipper Zero work?

Flipper Zero can damage iPhone

In case an attacker downloads additional software to Flipper Zero, this tool Conduct (DoS) attacks by sending multiple Bluetooth notifications to iPhone and iPad devices.

Seems like, Flipper Zero uses a low energy (BLE) array. Therefore, the occurrence of a small number of pop-ups will not cause any type of system malfunction, but will result in a greater number of pop-ups.

The attack consists of: Send mass alerts or pop-ups for Bluetooth activity AirDrop, HomeKit etc. related to. The victim’s iPhone is a to flood The number of pop-ups increases and the device crashes. After a few minutes, the iPhone restarts.

How to protect your iPhone from Flipper Zero?

Unfortunately, there is nothing users can do to prevent a major attack from Flipper Zero. But there’s a little trick to keeping your iPhone secure. When you’re in public, Disable Bluetooth connection. This should prevent the attack from occurring.

If you’re in a coffee shop or other public place and your iPhone froze and you don’t know why… Check if Bluetooth connectivity is enabled and disable it. You may be experiencing a Flipper Zero attack. It is also important that you know this Flipper Zero’s range is 50 meters.

Apple should be aware of this security flaw in iOS 17. However, they have not yet commented on the issue. Software engineers are probably currently working on a patch to fix the vulnerability in future updates.