. i think someone else was testing/creating the dark test one.
I took a look at the process, but it was above my level/time consuming. So, I tabled it.
If I get time, I'll make that a bit more of a priority. The problem is, I'm not sure how much time to set aside. I'm also limited to using the ACP (which isn't a bad thing, I suppose) instead of using CSS.
There...
That was a lot of stuff to reply to in one thread. I didn't even say 'you're welcome' to those who said thanks. So, collectively, you're welcome. I did what I could to diagnose the problem and to find the source of the problem, but
@Rob did the heavy lifting.
It was obviously a script injection. You could verify this by blocking scripts on the site. (You could also still access the forum by doing so, but I had no way to let regular users know that.) The only question was what script it was and how they managed to do it.
Our fearless leader did not take any chances. Instead of trying to remove the scripts (and the widgets), he reverted to a time before the defacing. Which is a perfectly cromulent way of doing things. It was also a good idea just in case there were things we missed,
If you opened the page's source and searched for 'script', you'd eventually have come across a script that included 'hahaha' in the text. Well, two of them... And that's what the problem was.
My last post was long. So, I'll say it again, because it should be said.
There is no evidence (especially when looking at the XenForo bug) that user data was compromised. They didn't make off with your username, email, or password. Well, the passwords would be salted and hashed before being stored in the database. That'd make things more difficult for them.
Anyhow, you should be good to go.