{"id":8811,"date":"2017-08-18T08:45:25","date_gmt":"2017-08-18T16:45:25","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2017\/08\/18\/news-2584\/"},"modified":"2017-08-18T08:45:25","modified_gmt":"2017-08-18T16:45:25","slug":"news-2584","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2017\/08\/18\/news-2584\/","title":{"rendered":"Breaking Down the HBO Hacks: From Game of Thrones To a Twitter Takeover"},"content":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/59961adcd5c2fb3991a1a05f\/master\/pass\/HBO-breach-03-FeatureArt.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Fri, 18 Aug 2017 15:46:32 +0000<\/strong><\/p>\n<p data-reactid=\"247\"><span class=\"lede\" data-reactid=\"248\"><!-- react-text: 249 -->They say April <!-- \/react-text --><\/span><!-- react-text: 250 -->is the cruelest month, but HBO may beg to differ. The company kicked off August with an apparently <!-- \/react-text --><a href=\"https:\/\/www.wired.com\/story\/game-of-thrones-leak-hbo-hack\/\" data-reactid=\"251\"><!-- react-text: 252 -->massive breach of its servers<!-- \/react-text --><\/a><!-- react-text: 253 -->, in which hackers pilfered everything from full episodes of unreleased shows to <!-- \/react-text --><a href=\"https:\/\/www.wired.com\/story\/hbo-hack-ransom-note\/\" data-reactid=\"254\"><!-- react-text: 255 -->sensitive internal documents<!-- \/react-text --><\/a><!-- react-text: 256 -->. Not long after, in separate and distinct incidents, two episodes of <!-- \/react-text --><em data-reactid=\"257\"><!-- react-text: 258 -->Game of Thrones<!-- \/react-text --><\/em><!-- react-text: 259 --> leaked out early. And Thursday, <!-- \/react-text --><a href=\"https:\/\/www.wired.com\/2016\/06\/meet-ourmine-security-group-hacking-ceos-celebs\/\" data-reactid=\"260\"><!-- react-text: 261 -->hacker  group OurMine<!-- \/react-text --><\/a><!-- react-text: 262 --> hijacked HBO\u2019s main Twitter account, along with those of several HBO shows. It\u2019s been a hell of a couple of weeks.<!-- \/react-text --><\/p>\n<p data-reactid=\"263\"><!-- react-text: 264 -->But HBO\u2019s rocky patch of hacks and leaks also serves as an important reminder of just how hard it is for any company to lock things down these days. While the attacks blur together, they\u2019re in fact four distinct incidents, each with their own set of lessons.<!-- \/react-text --><\/p>\n<p data-reactid=\"265\"><!-- react-text: 266 -->\u201cThey have some supply chain issues, they have malicious insiders, they had accidental insiders, they have an account compromised,\u201d says Richard Ford, chief scientist at security software company Forcepoint. \u201cIt crosses a range of issues that highlight the challenges that a big organization like HBO faces.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"267\"><!-- react-text: 268 -->Focusing on the variety of threats out there doesn\u2019t just provide some much-needed clarity around HBO\u2019s current dilemma\u2014it may help other companies prevent a similar mess down the road.<!-- \/react-text --><\/p>\n<p data-reactid=\"271\"><!-- react-text: 272 -->HBO\u2019s trouble actually began at the tail end of June, when <!-- \/react-text --><a href=\"https:\/\/www.wired.com\/story\/game-of-thrones-leak-hbo-hack\/\" data-reactid=\"273\"><!-- react-text: 274 -->hackers identified only as Mr. Smith<!-- \/react-text --><\/a><!-- react-text: 275 --> dropped four unreleased episodes of HBO shows\u2014including one, <!-- \/react-text --><em data-reactid=\"276\"><!-- react-text: 277 -->Barry<!-- \/react-text --><\/em><!-- react-text: 278 -->, not slated to debut until next year\u2014as well as the script to an unreleased episode of <!-- \/react-text --><em data-reactid=\"279\"><!-- react-text: 280 -->Game of Thrones<!-- \/react-text --><\/em><!-- react-text: 281 -->. They suggested they had 1.5 terabytes of HBO data in total, ranging from more shows to financial statements and other sensitive documents.<!-- \/react-text --><\/p>\n<p data-reactid=\"282\"><!-- react-text: 283 -->A week later, the same person or group followed up with a ransom note demanding millions of dollars in exchange for the leaks to stop, as well as a screenshot to a file directory that implied they had access to either information about or episodes of shows like <!-- \/react-text --><em data-reactid=\"284\"><!-- react-text: 285 -->Curb Your Enthusiasm<!-- \/react-text --><\/em><!-- react-text: 286 --> and <!-- \/react-text --><em data-reactid=\"287\"><!-- react-text: 288 -->Insecure<!-- \/react-text --><\/em><!-- react-text: 289 -->.<!-- \/react-text --><\/p>\n<p class=\"article-list-item-embed-component__title\" data-reactid=\"305\">HBO Hackers Release Ransom Note and New Trove of Stolen Data<\/p>\n<p class=\"article-list-item-embed-component__title\" data-reactid=\"315\">Hack Brief: HBO Shows and a <em>Game of Thrones<\/em> Script Land Online<\/p>\n<p class=\"article-list-item-embed-component__title\" data-reactid=\"325\">That <em>Orange Is the New Black<\/em> Leak Was Never Going to Pay Off<\/p>\n<p data-reactid=\"326\"><!-- react-text: 327 -->Here\u2019s where things get a little confusing. In between those two hyped hacker releases, a full episode of <!-- \/react-text --><em data-reactid=\"328\"><!-- react-text: 329 -->Game of Thrones<!-- \/react-text --><\/em><!-- react-text: 330 --> leaked two days before the air date. It came not from Mr. Smith, as one might have assumed, but from four men in India who <!-- \/react-text --><a href=\"http:\/\/money.cnn.com\/2017\/08\/15\/media\/game-of-thrones-episode-leak-star-india-arrests\/index.html\" target=\"_blank\" data-reactid=\"331\"><!-- react-text: 332 -->allegedly smuggled the episode<!-- \/react-text --><\/a><!-- react-text: 333 --> out of Prime Focus Technologies, a company that works with Star India, which carries HBO in that country.<!-- \/react-text --><\/p>\n<p data-reactid=\"334\"><!-- react-text: 335 -->While not a traditional attack, in which hackers breach a system, the Star India heist represents an increasingly common scourge for the entertainment industry and beyond: The not-quite-inside job. However secure HBO can make itself, it has little say in how Star India protects its data, and even less in what Prime Focus Technologies does.<!-- \/react-text --><\/p>\n<p data-reactid=\"336\"><!-- react-text: 337 -->\u201cThe whole business model today has exacerbated the insider threat, because there\u2019s a lot more insiders,\u201d says Stephen Cobb, senior security researcher at ESET, a global IT security firm. \u201cIf you sit down in a movie theater at the end and watch the thousands of people involved in that movie, most of them don\u2019t actually work at Paramount, or Sony, or whoever\u2019s name is on the picture\u2026 You\u2019ve got a lot of people having access to property which is very valuable.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"338\"><!-- react-text: 339 -->HBO\u2019s in no way alone in this; Netflix recently faced\u2014and declined\u2014a ransom shakedown when <!-- \/react-text --><a href=\"https:\/\/www.wired.com\/2017\/05\/orange-is-the-new-black-leak\/\" data-reactid=\"340\"><!-- react-text: 341 -->hackers lifted episodes from the upcoming season of <!-- \/react-text --><em data-reactid=\"342\"><!-- react-text: 343 -->Orange Is the New Black<!-- \/react-text --><\/em><\/a><!-- react-text: 344 --> from a third-party production studio. And the ease with which unscrupulous employees can smuggle that property out of the building exacerbates the issue.<!-- \/react-text --><\/p>\n<p data-reactid=\"349\"><!-- react-text: 350 -->\u201cIf you look at what is involved in an insider leaking intellectual property, it used to involve physically carrying something out of the building that was big and heavy. Or in the case of a movie, a can of film,\u201d says Ford. \u201cNow it\u2019s a file transfer.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"351\"><!-- react-text: 352 -->Taken together, the Mr. Smith hack and that initial <!-- \/react-text --><em data-reactid=\"353\"><!-- react-text: 354 -->Game of Thrones<!-- \/react-text --><\/em><!-- react-text: 355 --> leak would have already constituted one of the most high-profile month of security lapses the entertainment industry\u2019s recent history. But remember, that was just week one.  Two lesser\u2014but still damaging, and embarrassing\u2014trip-ups still followed.<!-- \/react-text --><\/p>\n<p data-reactid=\"356\"><!-- react-text: 357 -->On August 16, HBO played itself. In an incident unrelated to the Mr. Smith hack, or the Star India leak, HBO Nordic and HBO Espa\u00f1a aired this Sunday\u2019s episode of <!-- \/react-text --><em data-reactid=\"358\"><!-- react-text: 359 -->Game of Thrones<!-- \/react-text --><\/em><!-- react-text: 360 --> for an hour\u2014plenty of time for it to land on torrent sites.<!-- \/react-text --><\/p>\n<p data-reactid=\"361\"><!-- react-text: 362 -->\u201cThe error appears to have originated with a third-party vendor and the episode was removed as soon as it was recognized,\u201d <!-- \/react-text --><a href=\"https:\/\/www.usatoday.com\/story\/life\/tv\/2017\/08\/17\/hbo-game-thrones-twitter-accounts-hacked-ourmine\/575498001\/\" target=\"_blank\" data-reactid=\"363\"><!-- react-text: 364 -->said<!-- \/react-text --><\/a><!-- react-text: 365 --> HBO Europe spokesperson Tom Nielsen in a statement. The key phrase, again, being \u201cthird-party.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"366\"><!-- react-text: 367 -->Lastly, or at least most recently, came the OurMine hack. The group caused minimal damage, leaving a message that read, \u201cHi, OurMine are here, we are just testing your security, HBO team please contact us to upgrade the security.\u201d HBO regained control of its account within an hour.<!-- \/react-text --><\/p>\n<p data-reactid=\"368\"><!-- react-text: 369 -->\u201cThe infringement on our social media accounts was recognized and rectified quickly,\u201d says HBO spokesperson Jeff Cusson.<!-- \/react-text --><\/p>\n<p data-reactid=\"370\"><!-- react-text: 371 -->But the OurMine incident, in addition to adding literal insult to injury, also shows two distinct types of security threats.<!-- \/react-text --><\/p>\n<p data-reactid=\"376\"><!-- react-text: 377 -->&#x27;You\u2019ve got a lot of people having access to property which is very valuable.&#x27; \u2014Stephen Cobb, ESET&#x27;<!-- \/react-text --><\/p>\n<p data-reactid=\"378\"><!-- react-text: 379 -->First, companies under fire tend to draw attention from other hackers. Sony, for instance, <!-- \/react-text --><a href=\"https:\/\/www.forbes.com\/sites\/andygreenberg\/2011\/06\/20\/in-sonys-20th-breach-in-two-months-hacker-claims-177000-sony-emails-compromised\/\" target=\"_blank\" data-reactid=\"380\"><!-- react-text: 381 -->suffered 20 breaches<!-- \/react-text --><\/a><!-- react-text: 382 --> in two months following its <!-- \/react-text --><a href=\"https:\/\/www.wired.com\/2014\/12\/sony-hack-what-we-know\/\" data-reactid=\"383\"><!-- react-text: 384 -->devastating 2014 hack<!-- \/react-text --><\/a><!-- react-text: 385 -->.<!-- \/react-text --><\/p>\n<p data-reactid=\"386\"><!-- react-text: 387 -->\u201cAny high-profile hack will create elements of a dogpile and copycat, if we want to include both dog and cat in our analoty,\u201d says Cobb. \u201cThat organization is suddenly in the limelight. You also have copycats, where you have people out there saying wow, some of these big studios don\u2019t have perfect security.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"388\"><!-- react-text: 389 -->On a more practical level, the OurMine Twitter takeover offers a textbook example of credential-stealing, a pervasive attack that can cause a lot more damage than just social media exposure.<!-- \/react-text --><\/p>\n<p data-reactid=\"390\"><!-- react-text: 391 -->\u201cSpearphishing attacks are increasingly common and with the right amount of reconnaissance on the target, they can be the quickest way to obtain credentials for email accounts, cloud storage or even social media profiles,\u201d says J\u00e9r\u00f4me Segura, lead malware intelligence analyst at security firm Malwarebytes. It\u2019s unclear if OurMine used that method specifically, but it seems like a likely route.<!-- \/react-text --><\/p>\n<p data-reactid=\"394\"><!-- react-text: 395 -->If any silver lining can emerge from HBO\u2019s stormy few weeks, it may be that it illustrates just how many attacks a company has to defend against\u2014and how to deal with them when they do occur.<!-- \/react-text --><\/p>\n<p data-reactid=\"398\"><!-- react-text: 399 -->\u201cWhat you\u2019re looking at here, with a digital business like HBO, is an ever-expanding attack surface. You have complexity, you have applications, third-party partners, social media,\u201d says Jeff Pollard, security analyst at Forrester Research. \u201cAny one of those could be the pathway for an attacker to get in.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"402\"><!-- react-text: 403 -->As HBO has learned, defending against all of those threats simultaneously can feel a bit like defending King\u2019s Landing against dragons and White Walkers and whatever Little Finger\u2019s up to. But it\u2019s at least possible to adopt a mindset that helps minimize the damage.<!-- \/react-text --><\/p>\n<p data-reactid=\"404\"><!-- react-text: 405 -->\u201cFrom a defense standpoint, it\u2019s all about being able to protect your data wherever it\u2019s gone, and understanding how that data is ultimately leaving your control,\u201d says Forcepoint\u2019s Ford. \u201cA lot of the time in security we\u2019re focused on inbound, we\u2019re very threat-centric. But looking outbound, protecting that data wherever it is, is a paradigm shift we\u2019d do well to execute on.\u201d<!-- \/react-text --><\/p>\n<p data-reactid=\"406\"><!-- react-text: 407 -->Otherwise, absent more details about how the Mr. Smith hack happened in the first place, the best steps to take are also the simplest.<!-- \/react-text --><\/p>\n<p data-reactid=\"408\"><!-- react-text: 409 -->\u201cThe majority of the time, the lessons that are learned from these sort of events is that basic security principles and basic security hygiene are often not followed,\u201d says Pollard. Even a step as using two-factor authentication, for instance, could forestall potential Twitter takeovers.<!-- \/react-text --><\/p>\n<p data-reactid=\"410\"><!-- react-text: 411 -->Ultimately, the HBO hacks have proven less severe than what Sony suffered three years ago. Personal emails have not been publicly aired, and the leaks of shows so far don\u2019t seem to have put a dent in viewership. A very bad month has not turned as catastrophic as it first seemed it might have.<!-- \/react-text --><\/p>\n<p data-reactid=\"412\"><!-- react-text: 413 -->Then again, we\u2019re only two weeks in.<!-- \/react-text --><\/p>\n<p class=\"related-cne-video-component__dek\" data-reactid=\"423\">It\u2019s 2017! It\u2019s time to start using an encrypted messaging app. Why? Using end-to-end encryption means that no one can see what you\u2019re sharing back and forth. <\/p>\n<p><a href=\"https:\/\/www.wired.com\/story\/hbo-hacks-game-of-thrones\" target=\"bwo\" >https:\/\/www.wired.com\/category\/security\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p><img decoding=\"async\" src=\"https:\/\/media.wired.com\/photos\/59961adcd5c2fb3991a1a05f\/master\/pass\/HBO-breach-03-FeatureArt.jpg\"\/><\/p>\n<p><strong>Credit to Author: Brian Barrett| Date: Fri, 18 Aug 2017 15:46:32 +0000<\/strong><\/p>\n<p>Four separate security incidents, including _Game of Thrones_ leaks, have turned HBO&#8217;s August into a case study of hack attacks.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10378,10607],"tags":[714],"class_list":["post-8811","post","type-post","status-publish","format-standard","hentry","category-security","category-wired","tag-security"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/8811","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=8811"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/8811\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=8811"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=8811"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=8811"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}