UrbaanAlmelo

Looks like my problem was caused by another domain on the same server, that got hacked. Simply chmodding my root folder did the trick…

It’s always the hardest when a simple solution is right in front of you…

Don’t wanna spoil the fun, but there’s no _cache.php on my server.

I’m pretty sure by now that it’s not an issue that I myself can resolve. In my FTP client I saw this popping up:

[22:45:36] 211-Status of .htaccess:
[22:45:36]  -r--r--r--   1 henkleurinknl psacln       3519 Jan 17 21:34 .htaccess

henkleurinknl and psacln being websites of two other people – unfamiliar to me – who, not surprisingly, have also been compromised.

The problem seems to be lying somewhere else. Which does nót comfort me.

@impackt Can I borrow your guardian angel, just for a night?

@jamieedwards Yeah, I looked for it, but it’s not on my server.

@jamieewards Hope it works out for you. “Unfortunately” I don’t have timthumb issues, so no solution in sight for me as yet.

@impackt I’m not having issues with 404’s, but I added the piece of code you suggested. I don’t really see how that could be a solution, but it seems to have worked for you, so let’s wait and see.

Thanks for the help btw.

Right now my .htaccess looks like this

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

@impackt I did that over and over again. And the contents are exactly as they should be. Untill the file gets replaced again an hour later.

And I’ve changed all my passwords again and again today, so that’s not it.

@impackt I can overwrite the .htaccess on my server. But it really makes no difference at all.

@djab

Can you tell me how to implement the cron code? Not familiar with that.

@pkwooster

Thanks for the plugin. It showed that only the .htaccess is being modified. I’m also starting to think that the problem is related to hosting.

Yep, that’s kind of what I did…

I get that, but I manually deleted every single file that is related to WP (and more than that). I cleaned up my whole server. Still, after the reinstall, .htaccess was again targeted.

I did everything that’s been said in this thread, but the issue has still not been resolved. I even made a clean reinstall – deleting every single wp-file on my server – including a new database. Didn’t work. I’m really lost on this one. And getting just a little desperate.

Blank replies are the best ^^