Anyone been hacked / chrome blocked / blacklisted lately?

[shimmy2]

heyhey, Q: so paysite just suddenly became invisible to google sandboxed or whatever you call it few days ago, was wondering what was up. just the red page in chrome tripped like theres malware on my page and i havent updated tour in few weeks. checking through my logs has this happened to anyone else lately

[lock]

I have had a whole site deleted this week.

[RyuLion]

Is that what's happening? I get 403 Forbidden on xbiz.net but when I try incognito it shows the site, or are you talking about something else?

[shimmy2]

most likely just some haters causing trouble, fake snitching and whatnot, goes with the territory of dominating microniches. im onto their game like white on rice. anyhow for reference if this happens to any of you, here is how to go about fixing the red page haters:

Cleaning up your site
To remove Google's warnings, you'll need to find and remove the badware Google detected on your site and request a malware review. The articles and videos in Google's help for hacked sites section can help you learn how to assess site damage, how to clean it up, and how to request a malware review.

In addition to the information and tools Google provides to site owners who register for Webmaster Tools, you can read StopBadware's information on common hacks and how to fix them. If you need help finding the badware on your site, you can ask for help from Google's hacked site forum. One of the volunteers who answer questions here may be able to provide specific advice about your site.

Requesting a malware review from Google
When you are sure your site is free of badware, you can request a malware review. Requesting a malware review from Webmaster Tools is the fastest way to remove Google's warnings.

Google provides step-by-step instructions for Webmaster Tools users on how to request a malware review of a blacklisted site. *Note: Do not request a "reconsideration." A reconsideration is not a malware review and will not suffice to clear the warnings. If you are signing up for Webmaster Tools for the first time, you will need to add and verify your site before requesting a review.

Typically, a malware review from Google Webmaster Tools takes less than a day. If Google re-scans your site and does not find any badware, the warnings can be removed quickly. Webmaster Tools users will be able to see the results of their malware review request on their Webmaster Tools dashboard.

[Klen]

Posting URL of offending site would help.

[shimmy2]

problem fixed, it was a wordpress hack. even though i dont use wordpress. if its installed on your box then youre vulnerable. basically a low level hack some fuck embedded some <script> calling from a https:// secure connect in the index.html to some file. traced it back to country code "GA" somewhere near congo, west africa. likely a proxy server user. the offending script code i found in the source linked back to: (do not click or go to it)

'http s : / / l etsmakeparty3 . ga / l.js?n=1'

its a common wordpress hack to sandbox/redpage your site and take it off google. who is behind it, not sure at the moment but im combing through logs. problem solved.

[_Richard_]

Originally Posted by RyuLion

Is that what's happening? I get 403 Forbidden on xbiz.net but when I try incognito it shows the site, or are you talking about something else?

you need to clear the cookies for the site via the application on your browser

Originally Posted by shimmy2

problem fixed, it was a wordpress hack. even though i dont use wordpress. if its installed on your box then youre vulnerable. basically a low level hack some fuck embedded some <script> calling from a https:// secure connect in the index.html to some file. traced it back to country code "GA" somewhere near congo, west africa. likely a proxy server user. the offending script code i found in the source linked back to: (do not click or go to it)

'http s : / / l etsmakeparty3 . ga / l.js?n=1'

its a common wordpress hack to sandbox/redpage your site and take it off google. who is behind it, not sure at the moment but im combing through logs. problem solved.

thanks for the heads up