News for hackers. Stuff that matters.
Re:Security incident update by ig1 on Tuesday April 16, 2013 @06:44AM (#5557337)
I've canceled the card I used with Linode, the hacker may or may not have got access to the card number, but given the level of uncertainty I'd just rather cancel my card and get a new one reissued. I imagine my bank feels the same way.

Remember that depending on where you're based / your agreement with your bank that you might lose any standard "protection" for any fraudulent transactions that occur after you learn your cards been compromised.

Re:Security incident update by qompiler on Tuesday April 16, 2013 @07:18AM (#5557422)
This should be the top comment and the reason why companies should disclose this information on time and more often. Just like you would block your card if you get robbed, you should block your card if someone steals your cc data.
Re:Security incident update by kaiserama on Tuesday April 16, 2013 @11:41AM (#5558771)
I did the same thing. I had to read HN to even have a clue about this as their email correspondence/site gave no indication that this was even a possibility.

I would assume a large majority of their clients don't read HN and would have no line of sight to do the same.

It's unfortunate that this happened, but I'll be looking for another host in the near future.

Re:Security incident update by hvs on Tuesday April 16, 2013 @11:32AM (#5558707)
Agreed. As soon as I heard about this, I called my bank and canceled the card (no suspicious activity on it) and then regenerated 32 character passwords for all of my logins associated with Linode. An ounce of prevention and all that.
Re:Security incident update by trebor on Tuesday April 16, 2013 @09:36AM (#5557929)
And for exactly that reason I've had my credit card reissued as well, even though no fraudulent charges have been made. The risk is just too great for me to feel safe with the old credit card number.

Edit: Fixed spelling mistake.