Timeline for A deeper dive into the May 2019 security incident: blog post feedback
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2021 at 5:15 | comment | added | Félix Gagnon-Grenier | I was secretly hoping for a "plot twist: it was actually a trained AI model poking at the security holes gone bad" | |
| Jan 27, 2021 at 3:48 | comment | added | Martheen | @hat if that's the case the attacker's fresh account would've gained 10k reps during the intrusion from answering questions. | |
| Jan 26, 2021 at 4:43 | comment | added | hat | Okay, not Jon Skeet gone bad then :p | |
| Jan 25, 2021 at 17:17 | comment | added | Dean Ward StaffMod | Oh, I gotcha - yes, there was definitely indications of the attacker actually sleeping etc. which correlated with the time zone associated with their traffic. | |
| Jan 25, 2021 at 17:13 | history | edited | bad_coder | CC BY-SA 4.0 |
added 296 characters in body
|
| Jan 25, 2021 at 17:09 | comment | added | Dean Ward StaffMod | Are you asking whether the attacker went idle after they discovered we were on to them? If so: after escalation was discovered on SO the attacker continued pulling source code, but once we started to take build and source servers off the Internet they quickly backed off and their traffic was limited to (very) few site visits across the network | |
| Jan 25, 2021 at 17:01 | history | answered | bad_coder | CC BY-SA 4.0 |