Well, lookie there. We got the same browser string, and one of these IPs is, surprise surprise, Thomas himself dating back to olden times. We can clearly see our h4x0r wannabe trying, and failing, at using proxycondoms, probably because noob how-tos don't cover how to configure Furryfox, and as a result, BUSTED.

Well, lookie there. We got the same browser string, and one of these IPs is, surprise surprise, Thomas himself dating back to olden times. We can clearly see our h4x0r wannabe trying, and failing, at using proxycondoms, probably because noob how-tos don't cover how to configure Furryfox, and as a result, BUSTED.

Hmmm... Nouk, are you saying that maybe TSR did all this in order to blame Coconut? 

If so, that's pretty freakin' clever of them. And risky as hell too.  They hack Simsecrets, then use Buggy's complaint as an excuse to hack her site.  They leave a lot of calling cards to draw attention to the fact that it's TSR, and everyone goes, "Those bastards!" But some of us wonder, how stupid do you have to be?

So, TSR comes forward and says, "We wuz haxed!" 

And who is the logical person to blame?  Coconut.  Because Coconut has the motive.  And, from the screen shots, it's known that Coconut has access to TSR, higher access than other people. 

EDIT to add:  Also, I think all of us would agree that Coconut is pretty intelligent.  He/She has to be clever to get away with everything they have.  So, I think even Coconut would know not to leave too much evidence that it was Thomas, if Coconut was doing all this damage.  But, if you were Thomas, and wanted to make sure that TSR would get the blame until they could claim they were hacked, he'd make sure the evidence was as crystal clear as possible, so there would be no doubt that the hacker wants to frame TSR. 

I'm pretty sure that it was before my surgery, which was beginning of february.

Hi All,

I've spoken with TSR regarding this matter, and they informed me that they had a security breach about 3 months ago that may have left subscriber accounts vulnerable. If this information is indeed correct, it's possible that a third party could have logged into both buggybooz and Thomas accounts.

It's also entirely possible that other accounts have been compromised, which is why it's strongly advised to change your passwords anywhere where they are the same as at TSR. While the initial evidence indeed pointed to a TSR-owned account on MTS2 being used to initiate this attack, no actual hacking was done on MTS2 itself. The information supplied by TSR is worth thinking about, and indeed, I will be the first to admit that - at the time - I was annoyed about the whole thing and thought that this was a new low.

When this attack happened, my first concern was for how it happened, and then for restoring any damage done to buggys account. I worked with her for hours today in chat, as I mentioned in my first post, and we went through and restored everything. It was only after this was done that I decided to post up up this thread.

At the time, we believed that, given the evidence at hand, this was either a (very stupid) TSR sanctioned move, or one by a TSR staff member with access to the accounts. Given the lack of evidence to point elsewhere, I felt that, as this was a seemingly direct attack on a creator on *my* website, to get as much information out publically as possible. It is, however, with this new information about a possible security exploit, not 100% clear that, indeed, this was TSRs doing. Obviously neither I nor anybody else here knew about the alleged vulnerability, and the information to hand strongly pointed to a direct link.

I am willing to consider the possibily that this was not TSR sanctioned, but this raises other questions, particularly about the timing of the attacks and access to information that I simply don't have answers for right now. The evidence itself, however, remains unchanged. The IP addresses and screenshots are only edited to blur out any other users details and contain the real information as gotten from the MTS2 backend - and the validity of which is not disputed in any way by TSR. Regardless of the evidence at hand, there any many more questions that need addressing, and precious few answers right now.

The issue of the stolen content is still one that I, personally, would like to get cleared up and from comparing the downloads, there is some issue about the source textures, UV mapping and mesh for the Featured Artist to answer. I hope that TSR investigate this as an urgent matter.

For now, though, lets assume that this may not have been, indeed, a TSR sanctioned move - and I think we all agree that this would be a particularly stupid thing to do. I have to wonder as to the motivations and reasoning behind this apparent attack. What would somebody have to gain by deleting only a specific creators uploads, especially since any and all details would eventually come out publically? This entire thing has left a bad taste in my mouth, and while I don't like the idea of paysites, I also don't like the possibility of my being used and looking stupid.

Regards,
Delphy