Hackers Claim FBI Has Tracking Information For 12 Million iPhones And iPads
Yesterday, while many of us were grilling various meats and dreading the inevitable return to work, hackers posted what they claim are 1 million unique identifiers for iPads and iPhones. According to the hackers, the source of this information is a significantly larger database held by the FBI.
The pastebin post linking to the leaked information claims that during the second week of March, hackers were able to breach a notebook belonging to a FBI agent based out of New York City.
From the post:
"[D]uring the shell session some files were downloaded from his Desktop folder one of them with the name of 'NCFTA_iOS_devices_intel.csv' turned to be a list of 12,367,232 Apple iOS devices including Unique Device Identifiers (UDID), user names, name of device, type of device, Apple Push Notification Service tokens, zipcodes, cellphone numbers, addresses, etc. the personal details fields referring to people appears many times empty leaving the whole list incompleted on many parts. no other file on the same folder makes mention about this list or its purpose."
All iOS devices are associated with a UDID, intended to allow for easier tracking by developers and advertisers. Apple has come under fire in recent months after it was revealed that some third parties were receiving this tracking information without consent.
Hackers leak 1 million Apple UDIDs allegedly stolen from FBI laptop
A group of hackers released a file containing unique identification data for over 1 million Apple iOS devices and claim that the information is part of a larger...
By Lucian Constantin Sep 4, 2012 10:10 AM
A group of hackers released a file containing unique identification data for over 1 million Apple iOS devices and claim that the information is part of a larger database stolen from the compromised laptop of an FBI agent.
"During the second week of March 2012, a Dell Vostro notebook, used by Supervisor Special Agent Christopher K. Stangl from FBI Regional Cyber Action Team and New York FBI Office Evidence Response Team was breached using the AtomicReferenceArray vulnerability in Java," the hackers, who claimed affiliation to Anonymous and its Operation Antisec campaign, said Monday in a statement published on Pastebin.
"During the shell session some files were downloaded from his Desktop folder," the hackers said. "One of them with the name of 'NCFTA_iOS_devices_intel.csv' turned to be a list of 12,367,232 Apple iOS devices including Unique Device Identifiers (UDID), user names, name of device, type of device, Apple Push Notification Service tokens, zipcodes, cellphone numbers, addresses, etc."
As proof, the hackers released a stripped-down version of that file that only contained 1 million UDIDs, with associated Apple Push Notification Service tokens and device names. The other personal data that accompanied many of the UDIDs was intentionally removed, the hackers said.
The FBI declined to comment on the alleged security breach.
However, the leaked UDIDs -- random-looking codes made up of letters and numbers that are unique to every iOS device -- appear to be authentic.
"I have confirmed three of my devices in the leaked data," Peter Kruse, an electronic crime specialist at Denmark-based security firm CSIS Security Group, said Tuesday on Twitter.
A check of a random sample of UDIDs using the publicly accessible API (application programming interface) of OpenFeint, a social networking platform for iOS games, revealed that many of them correspond to devices whose owners have OpenFeint player profiles.
According to security researcher Aldo Cortesi, the founder of New Zealand-based security consultancy firm Nullcube, the leak of UDIDs can have serious privacy implications.
In the past, Cortesi investigated how UDIDs were being used by app developers and what information was being associated with them.
In May 2011, he reported that, when supplied with an UDID, the OpenFeint's API returned GPS coordinates and information that could reveal the user's Facebook profile.
In September 2011, he reported that other popular iOS gaming platforms had similar data leak issues. In one case, a platform's API even allowed attackers to take over a user's Facebook and Twitter account by knowing only their iOS device's UDID.
"It's disheartening to say it, but some of the companies mentioned in my posts still have unfixed problems (they were all notified well in advance of any publication)," Cortesi said in a blog post published Tuesday in light of the new UDID leak, which he described as a "privacy catastrophe."
"There are a number of far more serious problems still unfixed in the gaming social networks I discussed, but I would like to avoid describing those directly," Cortesi said Tuesday via email. "I [also] know of similar vulnerabilities in a number of non-gaming applications."
One of the problems is that user information linked to UDIDs has been aggregated in thousands of databases that now exist all over the Web, Cortesi said. "It takes only a single leak or security incident for data like this to be exposed."
"It's common, for instance, for app developers to use a UDID as a pseudo-identifier for users, and then to use that for tracking and analytics," Cortesi said. "The result would be a database of UDIDs with some associated behavioral information."
The use of UDIDs has been deprecated since iOS 5.0 and Apple has started rejecting App Store submissions for apps that access UDIDs since March.
The UDID was a bad idea from the beginning and Apple should have realized its privacy implications, Cortesi said. "I believe that they're doing what they can to move the application ecosystem away from using UDIDs as quickly as possible. They've just not quite been quick enough."
Apple did not return a request for comment regarding the leak of 1 million UDIDs.
As I described in a previous column, advertisers have been coming up with so called “alternative UDIDs” that circumvent Apple’s new policy — and raise additional privacy concerns.
Consumers can look up their device UDID by following the steps described here and then check to see if their number was among those released in the leak by using a tool developed by The Next Web.