Incident sheet · /security

Filed
Read
4 min · 812 words
Severity
Routine

Bitly Link Hijack Hit Trump, Burger King, FBI X Accounts

Bitly links in old posts by Trump, Burger King, McDonald's, Trudeau and the FBI were redirected to unrelated Wikipedia pages on November 15, 2026, exposing dead-link hijacking risks.

Old Bitly links in Trump, Burger King and other prominent X accounts redirected to unrelated websites
FeedOld Bitly links in Trump, Burger King and other prominent X accounts redirected to unrelated websites — FunkyFocus / pixabay

Event log

  1. On November 15, 2026, at least 12 Trump posts had hijacked Bitly redirects; Burger King, McDonald's, Gates, Trudeau and FBI accounts were also affected.
  2. Most affected links appeared in posts published between 2009 and 2014.
  3. A recreated Burger King link carried a Bitly creation timestamp of November 15, 2026, 5:32 a.m. UTC — the day of discovery.
  4. Bitly said it suspended accounts and disabled links but has not explained how identifiers were reclaimed despite its no-reuse policy.
  5. A prior incident used the same technique for a crypto pump-and-dump scheme, proving fraud applicability.

At least 12 posts on Donald Trump's X account had their Bitly links redirected to unrelated destinations, security researchers confirmed on November 15, 2026. The same failure affected old posts from Burger King, McDonald's, Bill Gates, former Canadian Prime Minister Justin Trudeau and the FBI. Most of the hijacked links sat in posts published between 2009 and 2014.

This is not a minor cosmetic glitch. It is a structural weakness in URL shortening that every enterprise still using decade-old short links in emails, PDFs, QR codes and help pages needs to audit today.

What did the redirects point to?

The new destinations were inflammatory, not commercial. Specific confirmed cases include:

  • Burger King: A link in a July 24, 2011 post promoting a restaurant-search service redirected to Wikipedia's list of Nazi concentration camps. A second Burger King link pointed to Wikipedia's article on Adolf Hitler.
  • McDonald's: A link in a June 7, 2011 post redirected to Wikipedia's article on the September 11 attacks.
  • Trump: A 2013 post criticising wind turbines led to a page with a photograph of an infant. A post about a Scottish golf course redirected to an article on Jeffrey Epstein documents.

One forensic detail matters. Bitly's information page for the Burger King link showed a creation date of November 15, 2026, 5:32 a.m. UTC — the day of discovery. Someone recreated that link hours before it was found. That timestamp is the strongest evidence this was deliberate repurposing, not a database error.

Burger King told CNN it had no role in the changes and was correcting or deleting affected posts. McDonald's had not responded to CNN's request for comment at publication time.

What did Bitly say?

Bitly confirmed the incident on X on November 15. Its statement read: "We identified an issue that allowed bad actors to repurpose certain old, inactive links to redirect people to content unrelated to the original posts. We have suspended the accounts involved and are disabling the affected links."

The company said its Trust and Safety team is working on stronger safeguards. Note what that statement does not say. It does not explain how the identifiers were reclaimed. It does not say how many links were affected. It does not confirm all redirects have been invalidated.

How does 'dead link hijacking' work?

Researchers call the technique dead link hijacking. When a shortened link's original account or destination is removed, the link goes inactive. If another party claims the link's identifier, every post, document or printed page carrying that link now routes to an attacker-chosen destination.

Here is the contradiction at the center of this story. Bitly's own help documentation states the identifier at the end of a short link cannot be reused once the original account is deleted. Reports from February 2025 indicated a bug allowing such reuse had been fixed. The November 2026 incident suggests that fix was incomplete or a similar flaw persisted. Bitly has not publicly clarified the mechanism, and that silence should worry any organization with a decade of archived short links in circulation.

Is this the first time?

No. An earlier incident, reported by Gizmodo and Forbes, exploited a Bitly bug to replace links in Trump's older posts. Those redirects pushed a memecoin website and a fake explicit image. Bitly said it fixed that bug and disabled the affected links.

The motives differ between the two events. The earlier attack was commercial — a crypto pump-and-dup scheme. The November 2026 redirects led mainly to Wikipedia articles, game-streaming pages and videos, which researchers read as trolling rather than fraud. The trolling variant is the benign one.

What is the enterprise exposure?

Ari Lightman, a digital media professor at Carnegie Mellon University, warned that clicking altered links could expose user information, and that artificial intelligence could automate such tampering at scale.

The attack surface extends far beyond social media. Short links live in marketing emails, PDFs, slide decks, printed QR codes and help pages — all of them redirectable through the same identifier-reclaim technique. The prior incident involved crypto promotion, which proves the method works for fraud. Researchers warn the next iteration could be phishing, delivered through links embedded in trusted official accounts — exactly the accounts compromised here.

What is still unknown?

Bitly's statement resolved little. Open questions include:

  • Who executed the redirects, and whether one actor or several were involved.
  • The total number of affected links — reports identified examples but gave no overall count.
  • How identifiers were reclaimed despite Bitly's stated no-reuse policy.
  • Whether Bitly has fully invalidated every affected link.

Until Bitly answers the reuse question publicly, treat every legacy short link your organization published before 2015 as unverified infrastructure. The timestamps prove recreation is possible. Nothing in the company's response proves it cannot happen again.

via medianama.com (Source)

Filed under

  • bitly
  • link-hijacking
  • url-shorteners
  • phishing
  • enterprise-security
Share this article:

More from Daniel Okafor

Daniel Okafor

Show full bio

Staff writer covering technology and product news in enterprise information technology and the leaders who run at CIO Monitor.

203 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›