Raw LLM Responses

At present I am running with the assumption that this is *NOT* a hacked server on the part of teamviewer (there's no evidence to support that assertion, yet), but is instead an exploitation of device discovery and "allow remote control". Allow remote control makes it so your computer is able to be remote controlled by a "support" technician, which is all well and good. Older versions of TeamViewer used 4 digit numbers (newer versions of Team viewer use a 6-character alphanumeric (a-z+0-9) randomly generated password. With ~200,000,000 accounts and a 60 second cooldown after 4 guesses the attackers could easily just be brute forcing machines that allow for remote control, and sending a success message back to the program controlling it when they gain access. With a pool that large and discoverability / password guessing being easily brute forced (discovery comes via different messages if a computer doesn't exist or incorrect credentials), it seems that is a more likely scenario than a central server breach. That said if this is the case TV is braindead for not catching the amount of incoming requests trying to brute force much sooner. Note: This kind of access can be disabled -- http://i.imgur.com/ITX4ToC.png If this proves to be a server breach I'll have to put in some serious hours this weekend to remove it. Ick. Edit: I stated in another comment: >It's also possible that this coincides with a larger hacking. The un/pw's were released from the linkedin hacking from years ago, and apparently just started to circulate (HaveIBeenPwned alerted me to it a few weeks ago). Thus password reuse could actually be the root cause here, despite my earlier claim. Email / Password combos could be automated and sent as well. Which seems to coincide with the timing off these attacks as well. You can check to see if your credentials were leaked in this (or any other) attack at https://haveibeenpwned.com/ . If you reuse your passwords and did so for TeamViewe