How to get URL link on X (Twitter) App
2/ AI automation largely favors Attackers, as their tasks align with AI’s strengths. Defender tasks require AI’s weaknesses. This isn't a temporary gap—it's structural. Here's why, and what defenders can do about it.
https://twitter.com/TalBeerySec/status/19035799835928043642/ Short answer: @whatsapp is indeed using @signalapp E2EE protocol, but "cheating" and leaking some metadata from the client side.
https://twitter.com/DAlperovitch/status/19292646127231020042/ In this case the "local" FPV drones attack was made possible with trucks that bridged the thousands of KMs separating Ukraine and the attacked Russian airbases (and relaying the control protocol over 4G/LTE).
https://x.com/TalBeerySec/status/1747556980540006446?s=20
2/ Eth_sign (legacy): in the beginning, client could sign anything, which of course could allow attackers to serve valid on-chain transactions as data for the victims to sign
https://twitter.com/ZenGo/status/1353704727255642112
2/ Advanced attackers (#APT) steal long term secrets ("the stamp") that allow them to issue access tokens and thus access all services in victims' environment, bypassing all security, including multi-factor auth (#MFA,#2FA)
https://twitter.com/jaredhaight/status/13222083096722022422/ Per the "Kerberoasting" example mentioned by @jaredhaight, the naive solution would be to just ask service account owners to upgrade password strength.
https://twitter.com/TalBeerySec/status/11993244655172239372/ The gist of it: Facebook breached their TOS as it allows blocking only in cases the blocked user actually violated the TOS and requires informing the blocked user