Instead of discussing how I almost got hacked, I’d be talking about the serious implications of my personal data leak.īradley's account came a few hours after Germany-based TeamViewer reaffirmed what it has steadfastly maintained for the past two weeks-that the account takeovers are the result of end users' careless passwords practices. 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. Lo 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," wrote Nick Bradley, a practice leader inside IBM's Threat Research Group. Late on Friday afternoon, an IBM security researcher became the latest to report a TeamViewer account takeover. Over the past three days, both Reddit and Twitter have exploded with such reports, often with the unsupported claim that the intrusions are the result of a hack on TeamViewer's network. No one outside of TeamViewer knows precisely how many accounts have been hacked, but there's no denying the breaches are widespread. In many of the cases, the online burglars reportedly drained PayPal or bank accounts. For more than a month, users of the remote login service TeamViewer have taken to Internet forums to report their computers have been ransacked by attackers who somehow gained access to their accounts.
0 kommentar(er)
