Bitly's Link Hijacking Flaw Exposes a 15-Year Supply Chain Risk

Bitly's Link Hijacking Flaw Exposes a 15-Year Supply Chain Risk

On November 15, someone systematically reclaimed expired Bitly short links from tweets posted over a decade ago. Burger King’s 2011 restaurant locator link now points to a Wikipedia article on Nazi concentration camps. McDonald’s 2011 link redirects to September 11 attack content. Trump’s old links point to crypto scams. The common thread: all these links were created years after the original tweets, suggesting Bitly’s back-halves (the slug after the slash) can be re-registered despite claims otherwise.

This isn’t just embarrassing for brands. It’s a warning about how we build systems that trust external services with traffic routing.

The Mechanics of the Exploit

Bitly’s public information pages show when each link was created. A link from a 2011 tweet shouldn’t have a 2026 creation date. Yet 56 of 97 Trump links examined show exactly this. The attack is straightforward: when an old link expires or its account deactivates, someone registers the same back-half again and points it wherever they want. No password theft. No account breach. The original poster sees nothing unusual.

Bitly’s own documentation claims back-halves “cannot be re-used,” but the evidence contradicts this. The company acknowledged the vulnerability and started disabling affected links, but only after public pressure and a viral post reaching 2.2 million views.

What bothers me most is that this happened before. In February 2025, memecoin promoters hijacked Bitly links from 2013 Trump tweets. Bitly claimed to fix it then. Clearly they didn’t.

Why This Breaks Architecture Decisions

Link shorteners are convenient. They’re trackable, memorable, and make URLs manageable in tweets and print media. But they’re also a single point of failure you don’t control. When you delegate traffic routing to a third party and that third party’s security model depends on the assumption that “expired links stay expired,” you’re accepting risk you might not realize.

For developers choosing infrastructure, this is a case study in delegation trade-offs. Yes, you could use your own URL shortener. Many organizations do, and for good reason. You maintain control of the back-half lifecycle. But that requires hosting, monitoring, and operational overhead. Most companies choose convenience and accept the risk.

The problem scales quietly. A brand’s 2011 tweet is dormant. Nobody’s monitoring it. By 2024 or 2025, when the hijack happens, the tweet’s still floating in search results and old articles. The redirected link gets clicked. Some people see concentrated camps next to a Burger King logo. Trust erodes. Misinformation spreads. A 15-year-old link becomes a vector for harm that nobody anticipated when it was created.

The Systemic Issue

This isn’t really about Bitly’s code quality. It’s about how services handle the lifecycle of old data. When you create a short link, you’re making a promise: this link will work and point where we said it points. If you later delete the account or let the link expire, you’re breaking that promise. But if you then allow someone else to make the same promise with the same link, you’re worse than broken. You’re untrustworthy.

Bitly had options. They could have permanently retired back-halves tied to old accounts. They could have required explicit confirmation before re-issuing. They could have been transparent about the risk. Instead, they let it happen twice and only acted when caught.

I’ve seen similar patterns in other infrastructure. APIs get deprecated but old clients still exist. Domains get abandoned but old links persist in documentation. Cloud resources get deleted but monitoring still references them. The technical debt compounds silently until the day someone weaponizes the forgotten link.

What This Means for Your Systems

If you use external link shorteners, audit them. Check what happens to old links. Understand the service’s account lifecycle policies. Consider whether you need the convenience or if control matters more.

If you run your own shortener, think deeply about back-half recycling. A link is a contract. Breaking it, even years later, has consequences you can’t predict. The safest approach is to never retire a back-half once issued. The cost is modest compared to the cost of hijacked traffic and broken trust.

For content creators and brands: your old links are still out there. They’re still in tweets, PDFs, printed materials, archived pages. Bitly removing hijacked links after the fact doesn’t remove them from URLs that people already clicked. The damage propagates beyond what any company can measure.

The deeper question is whether we can trust infrastructure that treats link lifecycle as a fire-and-forget problem, only caring when the fire becomes visible.

Read Next