briankrebsVerified account

@briankrebs

Independent investigative journalist. Writes about cybercrime. Author of 'Spam Nation', a NYT bestseller. Wrote for The Washington Post '95-'09

The Underweb
Joined March 2009

@briankrebs is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @briankrebs.

  1. In an unwelcome development, the source code for the 'Mirai' IoT botnet family has been released

  2. Money mule gangs turn to Bitcoin ATMs to launder stolen cash

  3. if you're trying to access my site right now and getting an error, please just try the https:// version thanks.

  4. We're glad to see back online thanks to Project Shield.

  5. both candidates are equally clueless when it comes to "cyber".

  6. Got the SSL issues fixed. Preparing to roll out a new, responsive theme in the very near future. Should be much more streamlined, simple

  7. It may take another 24h for my site to come up everywhere. meantime, you could try flushing your DNS cache

  8. first post with the site back under Google's Project Shield - The Democratization of Censorship

  9. should be coming back up gradually now and over the next 48 hours.

  10. RT : Why the record-breaking DDoS on KrebsOnSecurity opens a troubling chapter for the Net <best yet

  11. re-learning all of the security hoops we set up to block the site from being jacked over the years. fun times.

  12. Working on getting the site back up today, hopefully. Thanks to all who've expressed support, concern and solidarity.

  13. ...almost annoyingly irrelevant for me right now.

  14. Can't recall a time when I've received more invites from the MSM to come talk about the Yahoo hack. That's important to be sure, but..

  15. there's no place like 127.0.0.1

  16. site may be offline, but all his blogs are still available

  17. Before everyone beats up on Akamai/Prolexic too much, they were providing me service pro bono. So, as I said, I don't fault them at all.

  18. This is what I was talking about earlier. zero sense of urgency to the ddos problem.

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·