file2store issue is back?

I'm not disagreeing. I was, however, disagreeing with the statement that this exploit has nothing to do with "vb or vbseo at all."

So can anyone actually give me some suggestions instead of just arguing whose fault this is? I have been asking for the last 3 posts.

As stated before, if this keeps happening, you still have a folder or file that is writable, or never deleted the file that was originally uploaded and they keep executing it. You will need to find it.

Hi Err0r, I am curious...did you find a way to fix it? I have the same problem and checked everything. I even had no writable dirs and installed vbulletin and vbseo software again. Redirect still keeps coming back.

Did you change all your passwords as well? everything from admin accounts to ftp accounts to your actual hosting account to the DB password and db user.

once in, they could have gotten any of that.

i also got this problem..
what i do, just upload again (& replace) vbseo_sitemap file on
manage product under "plugin & product tab"..
then, it will fix..

see: Google redirecting to filestore123.info - vBulletin SEO Forums

I never managed to fix this, and yesterday, I was finally fed up with the hack and decided to delete the previous 3.8.7 install, and install a fresh copy of the latest vB4. After uploading all new files, I connected to the old database proceeded to run the upgrade script. Then I installed vBSEO.

This morning, the file2store.info redirection is back. Disabling and then re-enabling vBSEO 3.6.0 fixes the problem temporarily, still.

Does this mean that the database is hacked? Really confused and sad. Feels like I've been battling this problem for years.

Hello Carl ,

Did you read the suggestions posted in other thread where this issue has been discussed ?

This thread? Security issue

Yeah, read through it many times and applied the various fixes.

These are the steps I took previously: file2store issue is back?

check
Google redirecting to filestore123.info - vBulletin SEO Forums

Just posting in an old thread...

But SURE you change your password to your sql database once your hacked. That's what finally stopped the reoccuring hack for me, along with the rest of the fixes.