I was told by a friend of mine who reads my blog that the last two posts have not been showing up in Google Reader. Usually when I put up a post, there is a (1) that shows up right after my name (or just a few minutes later) but it is not working for some reason now. I am so clueless with technology and all of this programming stuff :( it's pretty sad actually!
Can anyone help me resolve this? I have a Feedburner and that seems to be working right.. I think at least?
Here is my blog URL, I'm not sure if you need it though
http://amazingasset.com
Posts Not Showing Up On Google Reader (9 posts)
-
tessa8m
Posted 1 year ago #
-
Rev. Voodoo
Posted 1 year ago #
YOur most recent post is missing from feedburner
Also, your missing images cause me concern
`
http ://amazingasset.com/”data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAVkAAAE8CAYAAABqy8IyAAADJWlDQ1BJQ0MgUHJvZmlsZQAAeAGFlE1IFGEYx/+zjQSxBtGXCMXQwSRUJgtSAtP1K1O2ZdVMCWKdfXedHGenmd0tRSKE6Jh1jC5WRIeITuGhQ6c6RASZdYmgo0UQBV4itv87k7tjVL4wM795nv/7fL3DAFWPUo5jRTRgys67yd6Ydnp0TNv8GlWoRhRcKcNzOhKJAZ+plc/1a/UtFGlZapSx1vs2fKt2mRBQNCp3ZAM+LHk84OOSL+SdPDVnJBsTqTTZITe4Q8lO8i3y1myIx0OcFp4BVLVWhen I investigate yourmissing images, the link is the above (that's not a good sign, indicitave of a hcked site)
I'm looking through your source now for any more stuff
-
Posted 1 year ago #
oh my... what do I do about a hacked site?!
-
Posted 1 year ago #
Yup, it do look hacked.
That link will show you your source code. You can see all those lines of gibberesh in there, thats encoded garbage. It's dangerous, and it's what is causing all of your issues
Unhacking a site is a royal PITA
First thing. Change all of your passwords regarding WP and your host
THen, here's some stuff to look into:
http://codex.wordpress.org/FAQ_My_site_was_hacked
http://wordpress.org/support/topic/268083#post-1065779
http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
http://ottopress.com/2009/hacked-wordpress-backdoors/
http://sitecheck.sucuri.net/scanner/Maybe a talk with your host will help, they might be able to help (Most don't, but worth a shot)
Do you (or your host) keep backups at all?
-
Posted 1 year ago #
I have backed up before... but not in a few weeks. I am not sure if Bluehost has backups. I have absolutely no idea how to unhack a site... so it's a hard thing to do? Thank you for providing those links, I will look into them.
Do you know why this happened? -
Posted 1 year ago #
It can be a bit hard. Unfortunately, every hack, site, and server configuration is different. So there isn't really a step by step how to.
Forum / Google searches may help. Talking to Bluehost may help. Telling them you've been hit with some sort of base 64 eval hack
IT happened due to some bad configuration. WordPRess itself has no known vulnerabilities at this time. However, themes can have vulnerabilities.
For instance, I see you run thesis. Is it up to date? If not, you may have fallen victim to the timthumb exploit.
Bad plugins can also be vulnerable, as can bad server setup. BUt the more I look at your code, and situation, I'm nearly certain its the timthumb thing.
That gives you some info to help narrow down your search for help, looking for timthumb thesis hacks, cleanup, etc
-
Posted 1 year ago #
Thank you for your suggestions! I am pretty certain I am going to have to have someone do this for me... I literally have no idea about most of this stuff :(
-
Just a heads up, her site was not hacked. Those encodings were from her trying to copy and paste images into the posts. The actual encodings themselves, prefaced with "data:image/png;base64,", is a valid way to declare a src for an img tag. The problem was that doing it that way for some reason caused the editor to go into rich text mode for the html, inserting html entities for curly quotes where she needed plain single or double quotes. That in turn broke a few other things, but I think she has it straightened out now.
-
Posted 1 year ago #
Excellent! Thanks for clarifying that!
I just saw thesis, then base64, and jumped to a conclusion, very happy it wasn't a hack, those are a giant pain!
Topic Closed
This topic has been closed to new replies.
