Hackers Claim to Have 12 Million Apple Device Records

hans

Banned
319px-Apple_bitten.svg.png

Hackers have released a file that they say contains more than one million identification numbers for Apple iPhones, iPads and iPod Touch devices. They claim to have obtained the file by hacking into the computer of a federal agent.

The hacking group, known as AntiSec a subset of the loose hacking collective known as Anonymous posted copies of the file on Sunday and, in an online message, claimed to have a total of more than 12 million Apple identification numbers and associated personal data in their possession. They said they obtained the file in March by hacking into the laptop of a Federal Bureau of Investigation agent in the bureaus New York field office.


The F.B.I. denied that the file was obtained from one of its agents.


<<<<< Actual Dump >>>>>>> <<<< web Source: http://pastebin.com/nfVT7b0Z >>>>>




  1. CANDY! CANDY! CANDY!...............candy.


  2. Download links:

  3. http://freakshare.com/files/6gw0653b/Rxdzz.txt.html
  4. http://u32.extabit.com/go/28du69vxbo4ix/?upld=1
  5. http://d01.megashares.com/dl/22GofmH/Rxdzz.txt
  6. http://minus.com/l3Q9eDctVSXW3
  7. https://minus.com/mFEx56uOa
  8. http://uploadany.com/?d=50452CCA1
  9. http://www.ziddu.com/download/20266246/Rxdzz.txt.html
  10. http://www.sendmyway.com/2bmtivv6vhub/Rxdzz.txt.html

  11. HOW TO GET THE CANDY ONCE YOU HAVE DOWNLOADED THE FILE

  12. first check the file MD5:
  13. e7d0984f7bb632ee19d8dda1337e9fba

  14. (lol yes, a "1337" there for the lulz, God is in the detail)

  15. then decrypt the file using openssl:
  16. openssl aes-256-cbc -d -a -in file.txt -out decryptedfile.tar.gz

  17. password is:
  18. antis3cs5clockTea#579d8c28d34af73fea4354f5386a06a6

  19. then uncompress:
  20. tar -xvzf decryptedfile.tar.gz

  21. and then check file integrity using the MD5 included in the password u used to
  22. decrypt before:
  23. 579d8c28d34af73fea4354f5386a06a6
  24. ^ yeah that one.

  25. if everything looks fine
  26. then perhaps it is.

  27. enjoy it!

  28. there you have. 1,000,001 Apple Devices UDIDs linking to their users and their
  29. APNS tokens.
  30. the original file contained around 12,000,000 devices. we decided a million would be
  31. enough to release.
  32. we trimmed out other personal data as, full names, cell numbers, addresses,
  33. zipcodes, etc.
  34. not all devices have the same amount of personal data linked. some devices
  35. contained lot of info.
  36. others no more than zipcodes or almost anything. we left those main columns we
  37. consider enough to help a significant amount of users to look if their devices
  38. are listed there or not. the DevTokens are included for those mobile hackers
  39. who could figure out some use from the dataset.


  40. file contains details to identify Apple devices.
  41. ordered by:

  42. Apple Device UDID, Apple Push Notification Service DevToken, Device Name,
  43. Device Type.



  44. We never liked the concept of UDIDs since the beginning indeed.
  45. Really bad decision from Apple.
  46. fishy thingie.


  47. so the big question:
  48. why exposing this personal data?
  49. well we have learnt it seems quite clear nobody pays attention if you just come
  50. and say 'hey, FBI is using your device details and info and who the **** knows
  51. what the hell are they experimenting with that', well sorry, but nobody will care.
  52. FBI will, as usual, deny or ignore this uncomfortable thingie and everybody will
  53. forget the whole thing at amazing speed. so next option, we could have released
  54. mail and a very small extract of the data. some people would eventually pick up
  55. the issue but well, lets be honest, that will be ephemeral too.
  56. So without even being sure if the current choice will guarantee that people
  57. will pay attention to this ******* shouted
  58. '******* FBI IS USING YOUR DEVICE INFO FOR A TRACKING PEOPLE PROJECT OR SOME
  59. ****' well at least it seems our best bet, and even in this
  60. case we will probably see their damage control teams going hard lobbying media
  61. with bullshits to discredit this, but well, whatever, at least we tried and
  62. eventually, looking at the massive number of devices concerned, someone should
  63. care about it. Also we think it's the right moment to release this knowing that
  64. Apple is looking for alternatives for those UDID currently and since a while
  65. blocked axx to it, but well, in this case it's too late for those concerned
  66. owners on the list. we always thought it was a really bad idea. that hardware
  67. coded IDs for devices concept should be erradicated from any device on the
  68. market in the future.

  69. so now candy was delivered.
  70. few words, and just a few, about how the **** came. we don't like too much
  71. about disclosing this part, we understood it would be needed, so, ****
  72. whatever. lost asset. Hope it serves for something.


  73. During the second week of March 2012, a Dell Vostro notebook, used by
  74. Supervisor Special Agent Christopher K. Stangl from FBI Regional Cyber Action
  75. Team and New York FBI Office Evidence Response Team was breached using the
  76. AtomicReferenceArray vulnerability on Java, during the shell session some files
  77. were downloaded from his Desktop folder one of them with the name of
  78. "NCFTA_iOS_devices_intel.csv" turned to be a list of 12,367,232 Apple iOS
  79. devices including Unique Device Identifiers (UDID), user names, name of device,
  80. type of device, Apple Push Notification Service tokens, zipcodes, cellphone
  81. numbers, addresses, etc. the personal details fields referring to people
  82. appears many times empty leaving the whole list incompleted on many parts. no
  83. other file on the same folder makes mention about this list or its purpose.

 
Advertisement
Sponsored Link