Old Bitly Links Hijacked: Why Third-Party URL Shorteners Are a Ticking Time BombBrief · digest for November 19
Brief≈ 1 min

Old Bitly Links Hijacked: Why Third-Party URL Shorteners Are a Ticking Time Bomb

No accounts were hacked, 2FA stayed intact, and yet an old tweet suddenly started sending people to offensive pages. That happened to Burger King and McDonald's on November 15, 2026: within 18 minutes, attackers took over their 2011 links (bit.ly/19BFiM and bit.ly/mLWJO0) and redirected traffic to Wikipedia articles on concentration camps and 9/11. Reposts of Burger King's tweet quickly passed 2 million views.

This was link hijacking. A URL shortener hides a long address behind a back-half slug after the slash and serves an HTTP redirect. Bitly deletes accounts after three years of inactivity and promises never to reissue old back-halves, yet a bug reopened that exact loophole—even though it had already been patched in February 2025. A Ransomnews investigation checked 97 old bit.ly links from Donald Trump's tweets: 40 remained original, while 49 had been re-created later, some pointing to fake crypto sites. Bitly disabled the hijacked links later on November 15.

The takeaway for developers is simple: don't hardcode bit.ly into READMEs, emails, PDFs, or QR codes. Use full URLs or your own short redirect domain like go.example.com. And before clicking any Bitly link, append + to the end of the URL to see the destination and creation date—if the link is newer than the post, someone already took it over.

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 2