Recent searches
Search options
TeamViewer got owned (again) by Russia. https://infosec.exchange/@jtig/112689362692682679
Update confirming Russia: https://www.teamviewer.com/en/resources/trust-center/statement/
TeamViewer update, they believe it is restricted to their corporate environment only.
TeamViewer incident looks pretty small and contained: https://therecord.media/teamviewer-cyberattack-employee-directory-encrypted-passwords
I do wonder how this one got out into the public - rumours were abound in IR and CTI circles about TeamViewer being compromised before this was made public by TeamViewer.
@GossiTheDog This is a bold claim based on practically no evidence.
Anyway, I switched away from it some time ago. Not because of Russia but because it has turned to shit.
Using RustDesk now and it's mostly OK. If only I could make it resize the displayed remote desktop, so that it fits in the window of the client...
@bontchev @GossiTheDog exact same thing here. My only downside of RustDesk - can't autostart before Windows login. Managed somehow to make it work long time ago on Win10, but can't on Win11
@GossiTheDog sure, but what’s the likelihood that’ll result into compromises elsewhere? I’m not holding my breath.
@GossiTheDog "I believe I can fly..." 
@GossiTheDog
I really would like to know what is the case with development systems? Source code and the build infrastructure?
I'm not sure if this really counts as "production" and I have my doubts about a total separation of development and IT infrastructure
@GossiTheDog if the hackers found the "commercial usage detected" killswitch and sabotaged it, they get my applause
@GossiTheDog
TeamViewer: “restricted to corporate network”
File name customer-passwords.xlsx:
@GossiTheDog Sooo, was the account's MFA MITM'd, or did it not exist ?