My TeamSpeak Login got hacked

Hello everyone,

yes it happened and I don’t really know how, that’s why I’m here bc I need help to protect it better.

This is the message that I got from team speak support:

Hello again :),

Thanks for doing that. Just have to be careful with compliance.

So what I can see here is this (and this is how I know it links up to "a profile").

Using "EMAIL" I can now see your profile that was originally created when you purchased the license. Now since then, your https://sales.teamspeak.com/ account details have switched. (So to explain, when a customer purchases a license, we have an internal means in which to see your original details when you placed the order. This changed beyond ordering).

The change removed the address details & switched the email address to something that looks very generic. Has anyone gained access to your license? Or have you come across any issues recently in relation to your server? (Thinking odd error messages like "Too many slots hosted" or something similar).

Ultimately, I think we need to change your details to secure the account. (If you didn't do this, someone else has).

What details would you prefer for this? (Don't give me a password, I mean email address).

Thanks -

The thing is I don’t really know how, he didn’t hacked into my email or into my team speak server or my Linux machine, but I found in the team speak logs that some had tried to brute force my username. The IP is blocked now I hope so. One IP is from Russia and the other from Germany which gives me the information that he used an VPN.

I used sudo iptables -I INPUT -s IP -j DROP to block the IPs but don’t know if that is enough. Team Speak support have changed my email to another one and I have recovered my account. I would appreciate any help how to protect it in future and if someone can explain me how he get into my Team speak account where my license.dat file is. Hope you guys don’t get mad with my terrible English.

submitted by /u/Jam0L33T
[link] [comments]

July 3, 2023
Read More >>