Ask HN: Buffer got hacked - does anyone know details?
116 points| andreasklinger | 12 years ago | reply
https://twitter.com/search?q=%40buffer&src=typd&f=realtime
The guys seem to be on it.
Last information: They confirmed they got hacked turned of publishing and they are investigating the issue.
[+] [-] leowidrich|12 years ago|reply
- All FB posts via Buffer are temporarily deleted. They will reappear again once we've enabled the FB app again (which we'll do once we're sure we're not compromised anymore).
- All Tweets are also stopped from sending.
We'll keep you updated from the @Buffer twitter and FB account.
- Leo
[+] [-] FredericJ|12 years ago|reply
How do you store the Buffer passwords? SHA1(password+salt)?
[+] [-] 300bps|12 years ago|reply
How'd they get into your system? Was it a Buffer Overflow?
[+] [-] shortformblog|12 years ago|reply
[+] [-] emhart|12 years ago|reply
[+] [-] chmars|12 years ago|reply
[+] [-] iriche|12 years ago|reply
Hi there,
I wanted to get in touch to apologize for the awful experience we've caused many of you on your weekend. Buffer was hacked around 1 hour ago, and many of you may have experienced spam posts sent from you via Buffer. I can only understand how angry and disappointed you must be right now.
Not everyone who has signed up for Buffer has been affected, but you may want to check on your accounts. We're working hard to fix this problem right now and we're expecting to have everything back to normal shortly.
We're posting continual updates on the Buffer Facebook page and the Buffer Twitter page to keep you in the loop on everything.
The best steps for you to take right now and important information for you:
Remove any postings from your Facebook page or Twitter page that look like spam Keep an eye on Buffer's Twitter page and Facebook page Your Buffer passwords are not affected No billing or payment information was affected or exposed All Facebook posts sent via Buffer have been temporarily hidden and will reappear once we've resolved this situation I am incredibly sorry this has happened and affected you and your company. We're working around the clock right now to get this resolved and we'll continue to post updates on Facebook and Twitter.
If you have any questions at all, please respond to this email. Understandably, a lot of people have emailed us, so we might take a short while to get back to everyone, but we will respond to every single email.
- Joel and the Buffer team
[+] [-] jlees|12 years ago|reply
[+] [-] abracar|12 years ago|reply
[+] [-] ericabiz|12 years ago|reply
Brutal. Once you revoke it, there's little to no chance that you're going to re-invoke it.
I've seen stuff like this get ugly in the past [1] -- I really like and respect the Buffer founders and hope they can recover from this.
[1]: http://en.wikipedia.org/wiki/Gnolia
[+] [-] mpeg|12 years ago|reply
Personally feeling slightly smug now, I actually applied for a job there not too long ago and got a half hearted rejection without any feedback (or the courage to actually reject me). I have direct experience in doing security for a Facebook SPMD - we never got successfully hacked, and yet we ran scenarios like this in our mind all the time.
[+] [-] dylanhassinger|12 years ago|reply
we'll re-invoke it
[+] [-] joelgascoigne|12 years ago|reply
We're working pretty hard to get to the bottom of everything.
Let me know if you have questions, I'll try and answer them all.
[+] [-] boy88|12 years ago|reply
[+] [-] chime|12 years ago|reply
When I see a local credit union site written in VBScript get hacked, I don't worry too much because it was probably riddled with SQL-injection bugs that any script kiddie can exploit. However, I know that you guys take data security seriously (you and I Skyped a while ago) and yet this happened. That's what worries devs like me the most.
I think it would be very helpful to us all (including many of your tech-savvy users) if you would write a detailed blog entry describing what actually happened and how. I believe you're encrypting tokens now but how did they get exposed in the first place? Was it a framework issue? Unhandled exceptions? Wrong chmod on a log file? New employee hooking up trojan'ed PC to your internal network? Here's hoping you feel comfortable in sharing.
[+] [-] borski|12 years ago|reply
[+] [-] antr|12 years ago|reply
[+] [-] morgante|12 years ago|reply
Though I don't want to be crass, I can't help but mention that I'm working on a project to help minimize the damage from these sorts of things. Would be interested in any feedback. (http://socialsecurity.io)
[+] [-] nwh|12 years ago|reply
[+] [-] deweerdt|12 years ago|reply
http://www.davidreiley.com/papers/SpamEconomics.pdf
[+] [-] lost-theory|12 years ago|reply
[+] [-] edcrfv|12 years ago|reply
[+] [-] iriche|12 years ago|reply
[+] [-] iriche|12 years ago|reply
[+] [-] dylanhassinger|12 years ago|reply
buffer rocks and is handling this in an A+ way
[+] [-] tokanizar|12 years ago|reply
[+] [-] tomphoolery|12 years ago|reply
[+] [-] pearjuice|12 years ago|reply
[+] [-] nathas|12 years ago|reply
[+] [-] denzil_correa|12 years ago|reply
[+] [-] OoTheNigerian|12 years ago|reply
All updates have been paused.
Passwords and payment information have NOT been compromised. --
It would be sorted out in a bit.
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] langer|12 years ago|reply
[+] [-] zaidf|12 years ago|reply
[+] [-] homakov|12 years ago|reply
[+] [-] tehwalrus|12 years ago|reply
(I will be re-enabling ASAP - I use this app a lot!)
[+] [-] brackin|12 years ago|reply
[+] [-] nav|12 years ago|reply
[+] [-] gregimba|12 years ago|reply