![]() ![]() We immediately informed Twitter of the information we had in our possession (and forwarded it to them), and at the same time reached out to the attacker. Various bloggers speculated about the cause of the attack – with some placing the blame on Google while others blaming the rising trend of hosting documents in the cloud. When the story first broke the true scope of what had taken place and how it occurred was not understood. The second is what was happening behind he scenes with Twitter as the story unfolded. The first, this post, is exactly how the hacks took place, based on information gathered from hours of conversations with Hacker Croll. We’ve already said a lot about all of this and the related “ server password = password” story that was discovered by another individual last week. It included things like financial projections and executive meeting notes that contained highly confidential information. It wasn’t until later that he realized just how much and what kind of information was taken. It’s clear that Twitter was completely unaware of how deeply they were affected as a company – when Williams said that most of the information wasn’t company related he believed it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |