plug
1.6K posts

plug
@plugxor
Your atypical security enthusiast | DFIR | Threat Hunting | Detection Eng | Insider Threat | Making content at The Blue Team Village | Opinions are my own.















Some of the people who are looking include @Salbei_ & @Micheal_merrill I’m also happy to forward leads to the team




Join the shared User Day of @owasp #DSOMM and #JuiceShop on Sep 25th, the day before @appsecusa San Francisco 2024! The agenda includes intros, demos, workshops and even a live CTF: #div-userday2024" target="_blank" rel="nofollow noopener">owasp.org/www-project-ju…
Register now on eventbrite.com/e/owasp-global… because seats are very limited!
For anyone worrying about this, I’d like to hear how you were already handling a near identical attack that didn’t require this vuln: - steal Yubikey - login - returns key WITHOUT cloning it, because 1 session is enough for most objectives Same attack flow. If that wasn’t already part of your threat model, why is this? If it was part of your threat model, how do your existing defenses not already handle the vuln? (I can think of a few, but none that apply to most of the people who are concerned) This should change very little for most people.




We have finished our investigation into last week's Mandiant X account takeover and determined it was likely a brute force password attack, limited to this single account.








