Snapchat and Twitter are also feeling the effects of a malicious iMessage code that was first seen only in the iMessage app.
Snapchat and Twitter have officially been made a part of the malicious crash message that has been making its way around iPhones. Originally, the message appeared in iPhone’s and was a series of unique Unicode. When the Unicode would arrive, the device would then crash. The only solution that was found, as Apple slowly reacted to it was utilizing Siri to change the status of the message to read, and then later responding to the message.
While Apple has finally responded to the criticisms of the message, pointing out that the flaw is something of a security bug to those who are trying to deal with a bad message. Now though, other iOS-based apps seem to have been impacted by the malicious message. Interestingly though, the primary apps that have been impacted are both Twitter and Snapchat. These apps have been impacted through their direct messaging platforms, or there instant messaging platforms.
Just as in iMessage, when the malicious message is sent the recipients smartphone then goes into a crash and power cycles repeatedly. Mark James of ESET pointed out that, “I am sure we have all had our desktop machines reboot after a seemingly random event has triggered the dreaded reboot. These mobile computers we call phones today have the same core instructions – if all else fails then reboot. This does not necessarily mean it’s a security flaw or indeed an exploitable bug but Apple will none the less try and rectify this as soon as they possibly can.”
As far as Apple is concerned, they released a statement soon after the malicious text was noticed pointing out, “Apple is aware of an iMessage issue caused by a specific series of unicode characters and we will make a fix available in a software update. Until the update is available, you can use these steps to re-open the Messages app.” At this point it’s unclear what Apple is going to do to remedy the situation. It’s not entirely clear if this is something that Apple will be able to fix without a great deal of challenge or complexity.
Some believe that this is just something that was rooted inside Apple code, and that the iPhone is really just reacting to something that is hardwired into the device. That being said though, it might be something that will have to wait to be corrected until after the actual launch of Apple iOS 9.