but adb has to be explicitly enabled through developer options hidden in the about phone settings of the device. Even then an explicit trust must be authorized

but adb has to be explicitly enabled through developer options hidden in the about phone settings of the device. Even then an explicit trust must be authorized between the adb server and device, via a dialog displayed upon the screen (containing the fingerprint of the server). Both Android and iOS have protections against this kind of attack, I would be really interested to hear the technical nature of how these work - either there is some bizarrely widespread 0 day exploit in all these chargers, this attack primarily affects old devices, or this article is primarily bait.