Its a proxy server. The following code will block it:
.htaccess
Code:
deny from 219.129.21.137
If you have an ErrorDocument 403, it will rewrite those through it's system.
However, since it is a proxy, and it is serving dupe content, I would think it would be worse to allow the proxy to continue since google could deem it as duplicate content.
This will at least break it for javascript compliant people. Meta-refresh's, location redirects, etc are all rewritten.
.htaccess
Code:
RewriteEngine on
RewriteCond %{REMOTE_ADDR} ^219\.129\.21\.137$
RewriteRule .* http://domain.com/br.html [R,L]
br.html
Code:
<script language="javascript" type="text/javascript">
var sMyDom = 'dom'+'ain'+'.com';
if (top.document.domain != sMyDom) {
top.location.replace(document.URL.replace(document.domain, sMyDom));
}
</script>
I'm not quite sure it was originally done with malicious intent -- it is a caching proxy server running on IIS it seems. I think someone just had a link that was followed, and google did its thing.