TacanRadio

[TacanRadio @hackeng444]

My 15yo account was hijacked & renamed to
@hackeng444
. But X didn't kill my session tokens—I'm tweeting from inside the hacked account right now! Fix Case: ACCESS-14406743. Live proof: [https://t.co/ADYHjI6DeC]
@Support
@Safety
@elonmusk
@BleepinComputer
@TechCrunch
@lindayaX

[TacanRadio @hackeng444]

My 15yo account was hijacked & renamed to @hackeng444. But X didn't kill my session tokens—I'm tweeting from inside the hacked account right now! Fix Case: ACCESS-14406743. Live proof: [https://t.co/ADYHjI6DeC] @Support @Safety @elonmusk @BleepinComputer @TechCrunch @lindayaX

[TacanRadio @hackeng444]

Is this safe? Hacker changed my handle to @hackeng444 but my device is still logged in & tweeting. Support bot ignores live proof of token theft. Escalate Case: ACCESS-14406743 Proof: [https://t.co/ADYHjI6DeC] @lindayaX @BleepinComputer @TechCrunch @Support @Safety

[TacanRadio @hackeng444]

Major security bug on X: My account was hacked & renamed to @hackeng444, but X failed to invalidate my session. Tweeting live from the breached account right now! Case: ACCESS-14406743 Proof: [https://t.co/ADYHjI6DeC] @CaseyNewton @briankrebs @Verge

[TacanRadio @hackeng444]

I am the original owner of this 15-year-old account. My credentials were changed via session hijacking. This is live proof that my local session is still active while my handle was forcedly changed to
@hackeng444 Case ID: ACCESS-14406743. Help!
@Support
@Safety