martinibuster - 3:34 am on Apr 3, 2013 (gmt 0)
Imo, it's best if you FIRST do as I recommended, diagnose the problem then take steps to mitigate them. So as I posted previously, first identify the rogue code, and from the position of the code within the page, you can very likely identify the part of the template that is being altered/hacked. I gave you instructions on how to do it. You're not going to solve problems by removing VBSEO if you haven't first diagnosed it as the source of the problem. Is the version of VBSEO the very latest version? As Roger_D already suggested, check to see if the VBulletin version installed is the latest version. Do you have many mods installed? If so, any one of those can be the source. You really should diagnose this first. Then act.