PayingPost Gone Bad?

Last week, Google Chrome wouldn’t load two of my blogs, this one and Kabalyero.com. Google Chrome would display a malware warning saying that the blogs “contains elements of img309.imagehack.ws which appears to host malware”. At first, I thought it was just a false positive and that Google Chrome is just mistaking imageshack.us with imagehack.ws since both blogs still load with no problems in Firefox. After searching both blogs source HTML codes for any instance of img309.imagehack.ws which turned out negative, I simply brushed it off as an error within Google Chrome’s security and used Firefox instead.

Today, these two blogs suddenly stopped loading in Firefox as well. Alarmed, I immediately started searching Google for possible answers. The search term I used in Google was “chrome reports imagehack.ws on my site” and the result lead me to Google’s Support Forum where the same issue is being discussed.

Skimming through the long thread, I learned that the problem could be from a third party code that went rouge and later down the thread I learned that those who were having the same problem were able to fix it by simply removing their PayingPost code from their blogs.

Well, it looked like I found the answer to my problem. I did sign-up with PayingPost many months ago and installed their code in both blogs without any thoughts of them using it to spread malware.

I immediately removed the codes from PayingPost on both blogs, deleted and cleared all cache files and a few minutes later both blogs are once again loading in both Google Chrome and Firefox.

By the way, PayingPost is now known as BlogAdvertisingStore. If you are looking for a way to make money from your blog or blogs then I would suggest that you stay away from them. I trusted them once and look what they did to my blogs (and to other bloggers as well). They used my blog with their code on it to spread malware.