#Panic mode hacked full

I know one of the programmers was able to solve the first one without much trouble. I didn’t mention the first attack because I barely remember it. Our business and some of its main client functions run through our site, so this was beginning to take a toll on our performance and bottom line, not to mention that we were running out of ideas/solutions. Apart from the time investment, there were considerable pecuniary expenses made throughout the ordeal. The other solutions were similarly difficult to implement, including having e-mail hosted with them but the domain hosted with another company that offered other secure Internet protocols. The solutions they offered included buying a new domain, which in part meant we had to change our company name, which is a registered trademark.

Of course they knew it wasn’t us, but their policies and protocols allowed for them to bar us. We went back to our hosting company to find out what was happening and it turned out that our domain was “ blacklisted” because we had “violated their terms”. However, when we tried to upload them back, it wasn’t possible. Fortunately, they were able to clean them up. It took about 3 days for them to find out that most of our web files were corrupt.

#Panic mode hacked full

Notified our programming team and asked them to find out which files had been corrupted and run a full audit of the hack. I then called our hosting company and asked them to disable our site entirely.

I went into panic mode for about 10 minutes. Needless to say, it was striking (see image). Some ill-intended hacker had filtered his way into our webpage and posted an image of a religious fanatic holding a machine gun and wearing a face veil similar to a Niqab most typically worn by women, covering all but his eyes.

On a typical Wednesday morning I get to work and check my e-mail, only to find a client telling me “What’s up with your website?” I didn’t think much of it, but I did open it up to a horrific site.