TeamViewer immediately responded to fix the issue to bring all services back up. The outage was caused by a denial-of-service attack (DoS) aimed at the TeamViewer DNS-Server infrastructure. "TeamViewer experienced a service outage on Wednesday, June 1, 2016. This is the company line, echoed through multiple PR statements released throughout the past few days (broken link removed):
"There is no security breach at TeamViewer" The TeamViewer response has been resolute and constant: Instead of discussing how I almost got hacked, I'd be talking about the serious implications of my personal data leak." Had I not been there to thwart the attack, who knows what would have been accomplished. Also lucky for me is the fact that I was there when it occurred.
Lucky for me, those were the only two machines that were still powered on with TeamViewer installed. I immediately go to the TeamViewer website and change my password while also enabling two-factor authentication. As soon as I reach the machine, I revoke control and close the app. Before I am able to kill it, the attacker opens a browser window and attempts to go to a new web page. Low and behold, the TeamViewer window shows up.
I run downstairs where another computer is still up and running. Then it dawns on me: I have other machines running TeamViewer! As soon as I realize what is happening, I kill the application. "In the middle of my gaming session, I lose control of my mouse and the TeamViewer window pops up in the bottom right corner of my screen. Nick Bradley, a practice leader inside IBM's Threat Research Group detailed his discovery:
0 kommentar(er)
