The Onion staff put their laughing-making on hold last week when the Syrian Electronic Army hacked its Twitter account \u2014 the latest in a growing list of publications invaded by the group. “In summary, they phished Onion employees’ Google Apps accounts via 3 separate methods,” the site’s tech team explained in a blog post. The slow, calculated attack began early this month, when the Syrian Electronic Army (SEA) sent emails to some of the site’s employees. The messages (example below) implored The Onion’s reporters to “Please read the following article for its importance,” with a link to what appeared to be a Washington Post story. [Interesting, the attackers modified their social engineered email attack to be a password reset email, after the Onion IT department told everyone to change their passwords.]<\/p>\n","protected":false},"excerpt":{"rendered":"
At least one employee entered their credentials, allowing the attackers entrance to their account, from which the SEA sent the same email to more Onion staff. The last attack compromised at least two more accounts, one of which was used to control the Twitter account.<\/p>\n
One in particular \u2014Syrian Electronic Army Has A Little Fun Before Inevitable Upcoming Deaths At Hands Of Rebels \u2014 angered the attacker, who began posting edtorial email addresses on the SEA account.<\/p>\n
At the end of the day, at least five Onion accounts were compromised; the company forced a password reset on every staff member’s Google Apps account.<\/p>\n
Link: http:\/\/www.itproportal.com\/2013\/05\/13\/the-onion-reveals-how-syrian-electronic-army-hacked-its-twitter\/<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-242","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=242"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/242\/revisions"}],"predecessor-version":[{"id":2729,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/242\/revisions\/2729"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}