News for hackers. Stuff that matters.
Re:How we discovered a database leak in one of the biggest S... by raducu on Tuesday March 06, 2018 @06:01AM (#16528099)
The moral of the story should have been -- change your hosting provider the minute they commit such a blunder.
Re:How we discovered a database leak in one of the biggest S... by aepiepaey on Tuesday March 06, 2018 @07:52AM (#16528488)
The first time might have been forgivable, but with the second incident it was definitely time to change provider.

The conclusion for what happened is obvious: the host "patched" what the attacker had done, but not the vulnerability that gave them access. Thus, the attackers re-used the same attack later to re-gain access.

Re:How we discovered a database leak in one of the biggest S... by bringtheaction on Tuesday March 06, 2018 @07:33AM (#16528392)
Indeed. Like they say, fool me once, shame on you; fool me twice, shame on me.

However how do you go about picking a new provider? How do you know that anyone else is any better?

Re:How we discovered a database leak in one of the biggest S... by twhiston on Tuesday March 06, 2018 @08:23AM (#16528648)
nine.ch is better (disclaimer - I work for them ;) )