This news item is covered in The Conversation.
On 11 June 2014, there was a major hack on TweetDeck which caused many messages to be send from TweetDeck. The message from Twitter at 5:59pm outlined:
We've temporarily taken TweetDeck
services down to assess today's earlier security issue. We'll update
when services are back up.
The university team have now analysed the back and have outlined it here.
Some text is:
Almost every day we see new threats with the security of
applications. At one time our problem was with viruses and worms, where
malicious code hide themselves on systems and aimed to trick the user
into installing themselves on the host system, and then do damage.
The world is changing though, were we are moving into the Cloud, and where code is run on Web servers, and where are data is stored within Cloud-based systems. In the past, software development teams would spend a great deal of time testing their programs for a range of activities, and often test them to destruction.
It’s a well-known problem in testing, as testers who test their own programs often do not exercise them in a way that we make them break. This article outlines the key elements of designing computer software, and highlights the specific example of the Tweet Deck hack.
The rest is at: