{"id":80,"date":"2008-01-27T02:51:28","date_gmt":"2008-01-27T10:51:28","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/2008\/01\/27\/pillaged-myspace-photos-show-up-in-bittorrent-download\/"},"modified":"2008-01-27T02:51:28","modified_gmt":"2008-01-27T10:51:28","slug":"pillaged-myspace-photos-show-up-in-bittorrent-download","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2008\/01\/27\/pillaged-myspace-photos-show-up-in-bittorrent-download\/","title":{"rendered":"Pillaged MySpace Photos Show Up in BitTorrent Download"},"content":{"rendered":"<p>    More than half of the million images that are private photos of MySpace users was stolen and uploaded onto BitTorrent. This is a huge privacy breach to MySpace users. The hacker, &#8220;DMaul&#8221;, said that he learned the security hole from the WIRED and used the method of attack. This security hole was surfaced last fall and because of this, various adversaries such as possible pedophiles, voyeurs, and advertisements were able to steal these photos. DeMaul ended up seeding these photos and advertised them as &#8220;pictures taken exclusively from private profiles&#8221;. It turns out that his attack cycles through the accounts by MySpace Friend ID numbers, thus did not target any specific group of people. Although, the attack did not target any specific group, this is a significant breach that affected users who are under 16 because their accounts are automatically set of private and their adversaries are more dangerous. Even though the attack result in leaks of a huge amount of pictures, it seems that MySpace didn&#8217;t follow up with the issue properly.<\/p>\n<p><!--more--><br \/>\nAfter reading this article, it occurs to me how insecure online profiles are. For example, the article also mentions various security holes that MySpace previously had. As more social network websites are created for various purposes, more and more types of assets will be compromise. If LinkedIn have any security breach, then the assets aren&#8217;t simply just pictures anymore. Adversaries will be able to steal information about users that are much more valuable. I believe one way to prevent such problem is design the security aspect heavily during the same design phase of the application. If they include a security review of the design of the application, there will be less security vulnerabilities. The way MySpace handled this attack makes me a worry that social networks might not care about the most important assets to the social networks, which are the users information.<\/p>\n<p>http:\/\/www.wired.com\/politics\/security\/news\/2008\/01\/myspace_torrent<\/p>\n","protected":false},"excerpt":{"rendered":"<p>More than half of the million images that are private photos of MySpace users was stolen and uploaded onto BitTorrent. This is a huge privacy breach to MySpace users. The hacker, &#8220;DMaul&#8221;, said that he learned the security hole from &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2008\/01\/27\/pillaged-myspace-photos-show-up-in-bittorrent-download\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":26,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,4,9],"tags":[],"class_list":["post-80","post","type-post","status-publish","format-standard","hentry","category-availability","category-current-events","category-privacy"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/80","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=80"}],"version-history":[{"count":0,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/80\/revisions"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=80"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=80"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=80"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}