{"id":386,"date":"2013-08-22T15:14:26","date_gmt":"2013-08-22T20:14:26","guid":{"rendered":"http:\/\/www.spacerogue.net\/wordpress\/?p=386"},"modified":"2023-02-27T13:46:42","modified_gmt":"2023-02-27T18:46:42","slug":"anatomy-of-hype-take-2","status":"publish","type":"post","link":"https:\/\/www.spacerogue.net\/?p=386","title":{"rendered":"Anatomy of Hype, Take 2"},"content":{"rendered":"

I almost wasn\u2019t going to write about the supposed cyber attack at the New York Times last week as reported by Fox Business because I just haven\u2019t had the time but after the NASDAQ went down today and everyone and their brother started to speculate as to the nature of the \u2018technical glitch\u2019 I figured I should throw something together.<\/p>\n

In my talk ‘Hackers and Media Hype or Big Hacks That Never Really Happened’<\/a> I mention that I see this sort of thing every day. That it is rampant throughout the tech press and often leaches over into traditional media outlets as well. I\u2019ve detailed this sort of thing before as in this blog post ‘Anatomy of Hype’<\/a> however this time reporters Matt Egan<\/a> and Jennifer Booton<\/a> published their unconfirmed \u2018cyber attack\u2019 on the FOX Business website and while FOX takes a lot of shit for their style of nearly tabloid journalism they have a much greater reach than tech news outlets like ZDNet.<\/p>\n

So lets see if we can piece together what happened here. At approximately 11:30 on August 14th 2013 the New York Times website went down. And by down I mean down hard, nytimes.com and nytco.com were both throwing up 503 site unavailable errors. Hey, shit happens, sites go down, they get fixed they come back up. As anyone who has ever worked on-call for an IT department will tell you despite backups, failovers and triple redundancies this happens ALL THE TIME.<\/p>\n

\"tweet\"<\/p>\n

By 11:53am, about half hour into the outage the official verified New York Times twitter account cited technical difficulties as the reason for the outage.<\/p>\n

At 11:55am Matt Egan<\/a> Matt Egan (@MattEgan5) and Jennifer Booton<\/a> (@jbooton) pushed the first version (screenshot)<\/a> of their story “Source: New York Times Website Hit by Cyber Attack”<\/a>. Their entire basis for the story was ‘a source close to the matter’. A source they fail to identify. A source as it turns out wasn\u2019t all that close to the matter after all.<\/p>\n

By 12:31am, internal New York Times employees start referencing an internal email that cites a malfunctioning system patch as the cause for the outage. While Microsoft\u2019s Patch Tuesday was the day before, which may or may not have been the cause of the outage, it made much more sense than a cyber attack.<\/p>\n

At 12:47pm, a little over an hour into the outage the New York Times Official twitter account finally offers up an explanation citing a \u2018server issue\u2019.<\/p>\n

<\/p>\n

In the face of all this new evidence did FOX Business pull the erroneous story about a cyber attack? Did Matt Egan<\/a> and Jennifer Booton<\/a> update their story to reflect the new information?<\/p>\n

Well, they did update their story (screenshot)<\/a>, put they updated it with quotes that make it sound like there was still some sort of cyber attack, quotes that are obviously of a hypothetical nature. Quotes that appear to be taken completely out of context but which support the original erroneous hypothesis of a cyber attack.<\/p>\n

One of the people who was quoted in the article said afterwards that the reporters came to him saying that they had already confirmed the cyber attack which was the only reason he agreed to speak with them. I have to ask, where was the confirmation? I have never been to journalism school but I suspect that Matt Egan<\/a> and Jennifer Booton<\/a> must have slept through the class on confirmation. I always thought you needed two independent sources to confirm a story. A lone \u2018source close to the matter\u2019 does not count as confirmation. Where were the FOX Business editors that reviewed this tripe before it was posted to the FOX Business website?<\/p>\n

As I did with ZDNet<\/a> I call on FOX Business to either completely rewrite the story on their site to reflect the currently known facts or to remove it altogether. Leaving a story such as this to fester on their website reflects poorly not just on FOX Business Matt Egan<\/a> and Jennifer Booton<\/a> but on the InfoSec industry as a whole, not to mention the damage that it is doing to the New York Times.<\/p>\n

The excuse that it fast breaking new story does not fly; a news website has a responsibility to the public to publish accurate and timely information. There is no excuse in this modern age not to update stories with new information as it becomes available. FOX Business has updated this story, several times, but the information is entirely skewed to support the original erroneous hypothesis.<\/p>\n

So how about FOX, Matt, and Jennifer, can you take the high road and report the facts or do you prefer to wallow in the muck of fear, uncertainty, and doubt?<\/p>\n

Update: Dave Lewis at CSO Magazine has also blogged about this story.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

I almost wasn\u2019t going to write about the supposed cyber attack at the New York Times last week as reported by Fox Business because I just haven\u2019t had the time but after the NASDAQ went down today and everyone and … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,11],"tags":[],"class_list":["post-386","post","type-post","status-publish","format-standard","hentry","category-current-events","category-media-hype"],"_links":{"self":[{"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=\/wp\/v2\/posts\/386","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=386"}],"version-history":[{"count":24,"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=\/wp\/v2\/posts\/386\/revisions"}],"predecessor-version":[{"id":969,"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=\/wp\/v2\/posts\/386\/revisions\/969"}],"wp:attachment":[{"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=386"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=386"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.spacerogue.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=386"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}