FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
1–10 of 76 posts
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#2Is this from the 2016 hack or a new one?
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#3Site is currently unresponsive. Cached version:
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#4Is this from the 2016 hack or a new one?
Website lists October 14th, 2019 as the article date and quotes a tweet from four days earlier. So I'd assume it's new.
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#5Is this from the 2016 hack or a new one?
The Chief Security Architect of FireEye posted this Tweet last week clarifying that there isn't a new compromise of TeamViewer, and the social media posts suggesting there is are misinterpreting a slide from a conference presentation.
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#6The article doesn’t give me any confidence in their reporting and is a site I’ve not heard of, so I’m feeling it’s a bit suspect. Anyone have a better source?
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#7The article should've linked to this tweet[0] by the same researcher instead:
> "APT41 compromised company behind TeamViewer - which enabled them to access any system with TeamViewer installed"
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#8[deleted]
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#9There is an ongoing trend the last several weeks of highly sensationalized cybersecurity incidents being mis-reported and ending up being nothing.
Not sure if it’s just a cluster of fuckups or if something is contributing to the uptick in false reports. But add this one to the list.
Re: FireEye confirms APT41 hacked TeamViewer, may have accessed billions of devices
#10Site is currently unresponsive. Cached version: http://archive.is/bklNU
Has anyone noticed that archive.is has pretty apalling dns-based tracking?