Advertisement
Guest User

Untitled

a guest
Jun 13th, 2016
179
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.50 KB | None | 0 0
  1. Delivered-To: dfghfghfghdghgj@gmail.com
  2. Received: by 10.107.168.199 with SMTP id e68csp1831000ioj;
  3. Mon, 13 Jun 2016 19:42:14 -0700 (PDT)
  4. X-Received: by 10.200.49.248 with SMTP id i53mr18104086qte.49.1465872134737;
  5. Mon, 13 Jun 2016 19:42:14 -0700 (PDT)
  6. Return-Path: <noreply@new.myspace.com>
  7. Received: from mail6.new.myspace.com (mail6.new.myspace.com. [216.178.44.49])
  8. by mx.google.com with ESMTP id w128si17009159qke.143.2016.06.13.19.42.14
  9. for <dfghfghfghdghgj@gmail.com>;
  10. Mon, 13 Jun 2016 19:42:14 -0700 (PDT)
  11. Received-SPF: pass (google.com: domain of noreply@new.myspace.com designates 216.178.44.49 as permitted sender) client-ip=216.178.44.49;
  12. Authentication-Results: mx.google.com;
  13. dkim=pass header.i=@new.myspace.com;
  14. spf=pass (google.com: domain of noreply@new.myspace.com designates 216.178.44.49 as permitted sender) smtp.mailfrom=noreply@new.myspace.com
  15. DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=new; d=new.myspace.com;
  16. h=Message-ID:List-Unsubscribe:MIME-Version:From:To:Date:Subject:Content-Type; i=noreply@new.myspace.com;
  17. bh=qH9YfgdPpdSL1aTVsKp1X2FezqU=;
  18. b=hWRA/omCvDUbuBty5we99W9k9Q8DoavTYa5qutvZFQQEMGoHrVtWTz7EmeL1OtWwI0B05v5CjTm6
  19. OQSUBolwyTtiJ8YIU/WRQuPk1jhKOO/z9wAOFwM9aE1J2FQBkpQnSZMTogBOhZRq/kjBCvwq5Zmt
  20. TDBo3ZPtnKh0QYUJN2E=
  21. DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=new; d=new.myspace.com;
  22. b=sBWYYRCYR1+avWYGLvt78/Mvgfn7v1ZKMegScI+EKBBI6jyxrqm4NBXdQXs0gZhqD1omAh3w35LB
  23. MYGW/jjRct/7QycTRqYVin1X4JRp3L5IlM7dYfKoaSdhM6xG9/avG7FSTTy09oN7O6QSUGQN4SU2
  24. eSL+4dDWUBSzpVIeIOg=;
  25. Received: from ash2mrfljob0072 (10.56.128.43) by mail6.new.myspace.com id hbtngc16bqo2 for <dfghfghfghdghgj@gmail.com>; Mon, 13 Jun 2016 19:39:34 -0700 (envelope-from <noreply@new.myspace.com>)
  26. Message-ID: <281597d7af6f4ecbbc5873e6249b560e@mail6.new.myspace.com>
  27. X-rpcampaign: data_breachMay312016a
  28. List-Unsubscribe: <mailto:donotemail@myspace-inc.com?subject=unsubscribe&body=data>,<https://myspace.com/settings/notifications?data=&templateid=data_breachMay312016a&utm_source=orm&utm_medium=email&utm_term=unsub&utm_campaign=data_breachMay312016>
  29. MIME-Version: 1.0
  30. From: "Myspace Legal" <noreply@new.myspace.com>
  31. To: dfghfghfghdghgj@gmail.com
  32. Date: 13 Jun 2016 19:39:34 -0700
  33. Subject: Critical Information About Your Myspace Account
  34. Content-Type: multipart/alternative;
  35. boundary=--boundary_778477_20b21d1b-b556-4a04-9ff0-c376b3c54d2d
  36.  
  37.  
  38. ----boundary_778477_20b21d1b-b556-4a04-9ff0-c376b3c54d2d
  39. Content-Type: text/plain
  40. Content-Transfer-Encoding: quoted-printable
  41.  
  42. Notice of Data Breach=0D=0AYou may have heard reports recently ab=
  43. out a security incident involving Myspace. We would like to make =
  44. sure you have the facts about what happened, what information was=
  45. involved and the steps we are taking to protect your information=
  46. .=0D=0A=0D=0AWhat Happened?=0D=0AShortly before the Memorial Day =
  47. weekend (late May 2016), we became aware that stolen Myspace user=
  48. login data was being made available in an online hacker forum. T=
  49. he data stolen included user login data from a portion of account=
  50. s that were created prior to June 11, 2013 on the old Myspace pla=
  51. tform.=0D=0A=0D=0AWe believe the data breach is attributed to Rus=
  52. sian Cyberhacker =E2=80=98Peace.=E2=80=99 This same individual is=
  53. responsible for other recent criminal attacks such as those on L=
  54. inkedIn and Tumblr, and has claimed on the paid hacker search eng=
  55. ine LeakedSource that the data is from a past breach. This is an =
  56. ongoing investigation, and we will share more information as it b=
  57. ecomes available.=0D=0A=0D=0AWhat Information Was Involved?=0D=0A=
  58. Email addresses, Myspace usernames, and Myspace passwords for the=
  59. affected Myspace accounts created prior to June 11, 2013 on the =
  60. old Myspace platform are at risk. As you know, Myspace does not c=
  61. ollect, use or store any credit card information or user financia=
  62. l information of any kind. No user financial information was ther=
  63. efore involved in this incident; the only information exposed was=
  64. users=E2=80=99 email address and Myspace username and password. =
  65. =0D=0A=0D=0AWhat We Are Doing=0D=0AIn order to protect our users,=
  66. we have invalidated all user passwords for the affected accounts=
  67. created prior to June 11, 2013 on the old Myspace platform. Thes=
  68. e users returning to Myspace will be prompted to authenticate the=
  69. ir account and to reset their password by following instructions =
  70. at https://myspace.com/forgotpassword=0D=0A=0D=0AMyspace is also =
  71. using automated tools to attempt to identify and block any suspic=
  72. ious activity that might occur on Myspace accounts.=0D=0A=0D=0AWe=
  73. have also reported the incident to law enforcement authorities a=
  74. nd are cooperating to investigate and pursue this criminal act.=0D=0A=
  75. As part of the major site re-launch in the summer of 2013, Myspac=
  76. e took significant steps to strengthen account security.=C2=A0The=
  77. compromised data is related to the period before those measures =
  78. were implemented. We are currently utilizing advanced protocols i=
  79. ncluding double salted hashes (random data that is used as an add=
  80. itional input to a one-way function that "hashes" a password or p=
  81. assphrase) to store passwords.=C2=A0Myspace has taken additional =
  82. security steps in light of the recent report.=0D=0A=0D=0AWhat You=
  83. Can Do=0D=0AWe have several dedicated teams working diligently t=
  84. o ensure that the information our members entrust to Myspace rema=
  85. ins secure. Importantly, if you use passwords that are the same o=
  86. r similar to your Myspace password on other online services, we r=
  87. ecommend you set new passwords on those accounts immediately.=0D=0A=
  88. =0D=0AFor More Information=0D=0AIf you have any questions, please=
  89. feel free to contact our Data Security & Protection team at dsp_=
  90. help@myspace-inc.com or visit our blog at https://myspace.com/pag=
  91. es/blog.
  92. ----boundary_778477_20b21d1b-b556-4a04-9ff0-c376b3c54d2d
  93. Content-Type: text/html
  94. Content-Transfer-Encoding: quoted-printable
  95.  
  96. =0D=0A =0D=0A=0D=0A<html>=0D=0A<body>=0D=0A<h3>Notice of Data Bre=
  97. ach</h3>=0D=0A<p>=0D=0AYou may have heard reports recently about =
  98. a security incident involving Myspace. We would like to make sure=
  99. you have the facts about what happened, what information was inv=
  100. olved and the steps we are taking to protect your information.=0D=0A=
  101. </p>=0D=0A<h3>What Happened?</h3>=0D=0A<p>=0D=0AShortly before th=
  102. e Memorial Day weekend (late May 2016), we became aware that stol=
  103. en Myspace user login data was being made available in an online =
  104. hacker forum. The data stolen included user login data from a por=
  105. tion of accounts that were created prior to June 11, 2013 on the =
  106. old Myspace platform.=0D=0A</p>=0D=0A<p>=0D=0AWe believe the data=
  107. breach is attributed to Russian Cyberhacker =E2=80=98Peace.=E2=80=
  108. =99 This same individual is responsible for other recent criminal=
  109. attacks such as those on LinkedIn and Tumblr, and has claimed on=
  110. the paid hacker search engine LeakedSource that the data is from=
  111. a past breach. This is an ongoing investigation, and we will sha=
  112. re more information as it becomes available.=0D=0A</p>=0D=0A<h3>W=
  113. hat Information Was Involved?</h3>=0D=0A<p>=0D=0AEmail addresses,=
  114. Myspace usernames, and Myspace passwords for the affected Myspac=
  115. e accounts created prior to June 11, 2013 on the old Myspace plat=
  116. form are at risk. As you know, Myspace does not collect, use or s=
  117. tore any credit card information or user financial information of=
  118. any kind. No user financial information was therefore involved i=
  119. n this incident; the only information exposed was users=E2=80=99 =
  120. email address and Myspace username and password. =0D=0A</p>=0D=0A=
  121. <h3>What We Are Doing</h3>=0D=0A<p>=0D=0AIn order to protect our =
  122. users, we have invalidated all user passwords for the affected ac=
  123. counts created prior to June 11, 2013 on the old Myspace platform=
  124. . These users returning to Myspace will be prompted to authentica=
  125. te their account and to reset their password by following instruc=
  126. tions at <a href=3D"https://myspace.com/forgotpassword">https://m=
  127. yspace.com/forgotpassword</a>=0D=0A</p>=0D=0A<p>=0D=0AMyspace is =
  128. also using automated tools to attempt to identify and block any s=
  129. uspicious activity that might occur on Myspace accounts.=0D=0A</p=
  130. >=0D=0A<p>=0D=0AWe have also reported the incident to law enforce=
  131. ment authorities and are cooperating to investigate and pursue th=
  132. is criminal act.=0D=0AAs part of the major site re-launch in the =
  133. summer of 2013, Myspace took significant steps to strengthen acco=
  134. unt security.=C2=A0The compromised data is related to the period =
  135. before those measures were implemented. We are currently utilizin=
  136. g advanced protocols including double salted hashes (random data =
  137. that is used as an additional input to a one-way function that "h=
  138. ashes" a password or passphrase) to store passwords.=C2=A0Myspace=
  139. has taken additional security steps in light of the recent repor=
  140. t.=0D=0A</p>=0D=0A<h3>What You Can Do</h3>=0D=0A<p>=0D=0AWe have =
  141. several dedicated teams working diligently to ensure that the inf=
  142. ormation our members entrust to Myspace remains secure. Important=
  143. ly, if you use passwords that are the same or similar to your Mys=
  144. pace password on other online services, we recommend you set new =
  145. passwords on those accounts immediately.=0D=0A</p>=0D=0A<h3>For M=
  146. ore Information</h3>=0D=0A<p>=0D=0AIf you have any questions, ple=
  147. ase feel free to contact our Data Security &amp; Protection team =
  148. at <a href=3D"mailto:dsp_help@myspace-inc.com">dsp_help@myspace-i=
  149. nc.com</a> or visit our blog at <a href=3D"https://myspace.com/pa=
  150. ges/blog">https://myspace.com/pages/blog</a>.=0D=0A</p>=0D=0A<img=
  151. alt=3D"" width=3D"1" height=3D"1" src=3D"https://myspace.com/bea=
  152. con/v3?eyJhY3Rpb25UZXh0IjoiT3BlbiIsImJlYWNvblZlcnNpb25WYWx1ZSI6Ij=
  153. MiLCJlbWFpbFJlcXVlc3RJZCI6IjI4MTU5N2Q3LWFmNmYtNGVjYi1iYzU4LTczZTY=
  154. yNDliNTYwZSIsImVh0IjoiRW1haWwiLCJ0ZW1wbGF0ZUN1bHR1=
  155. cmVDb2RlIjoiZW4tVVMiLCJ0ZW1wbGF0ZU5hbWUiOiJkYXRhX2JyZWFjaE1heTMxM=
  156. jAxNmEiLCJyZWNpcGllbnRQcm9maWxlSWQiOjExNzMzNjMxNSwicmVjaXBpZW50RW=
  157. 1haWxBZGRyZXNzSWQiOiJ6YXRlNzVAZ21haWwuY29tIiwiY2FtcGFpZ25OYW1lIjo=
  158. iZGF0YV9icmVhY2gifQ%3d%3d" />=0D=0A<img alt=3D"" width=3D"1" heig=
  159. ht=3D"1" src=3D"https://mpp.vindicosuite.com/conv/v=3D5;m=3D1;t=3D=
  160. 19942;he=3D463aeda4f50f068d51401f2384f7d73e;ts=3D6360144357436249=
  161. 22" />=0D=0A<img alt=3D"" width=3D"1" height=3D"1" src=3D"https:/=
  162. /pixel.monitor1.returnpath.net/pixel.gif?r=3Dcfb2afade25395d892e8=
  163. 2bf7de228d20142b38ad&c=3Ddata_breach" />=0D=0A</body>=0D=0A</html=
  164. >=0D=0A
  165. ----boundary_778477_20b21d1b-b556-4a04-9ff0-c376b3c54d2d--
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement