News 4 min read

Old Bitly links hijacked in Trump, Burger King and McDonald's posts


Bitly short links in old X posts by Donald Trump, Burger King, McDonald’s, Bill Gates, Justin Trudeau and others were taken over this weekend and pointed at unrelated pages, from Wikipedia articles to YouTube videos and games. On Sunday, November 15, Bitly confirmed on X that it had “identified an issue that allowed bad actors to repurpose certain old, inactive links”, suspended the accounts involved and started disabling the affected links. No brand account was hacked: the tweets are unchanged, but the short links inside them were registered again by someone else, so every old post, email, PDF or QR code that carries them now leads wherever the new owner chooses.

What happened

  • The brand links. A Bitly link in a Burger King tweet from July 24, 2011, meant for a restaurant locator, was created again at 05:32 UTC on November 15 and pointed at a Wikipedia list of Nazi concentration camps, Ransomnews found from Bitly’s public link info pages. A link in a McDonald’s tweet from June 7, 2011 had been re-created 18 minutes earlier and opened Wikipedia’s article on the September 11 attacks. A quote post of the Burger King tweet passed 2 million views within hours.
  • Trump’s old posts were hit hardest. CNN counted at least a dozen of Trump’s posts that now direct to unrelated sites, including a game, a Google site and a Wikipedia page about the Epstein files. Ransomnews checked 97 Bitly links in Trump tweets from 2009 to 2013: 40 were still the original, 49 had been re-created later but still led where the tweets suggested, seven led somewhere new and one was blocked by Bitly as malicious or spam.
  • Others too. CNN also found redirected links in old posts by Bill Gates, Justin Trudeau, Mike Pence and McDonald’s Indonesia account, and says the affected posts seem to date from 2009 to 2014. A Burger King spokesperson told CNN the company had no part in the redirects.
  • Bitly’s response. Bitly posted its statement on Sunday afternoon (19:13 UTC by Ransomnews’ timeline) and said its Trust and Safety team is working to “strengthen protections against similar misuse in the future.” By 19:22 UTC the Burger King and McDonald’s links showed Bitly’s “Link Deactivated” page. Bitly has not said how many links were taken or how.

The part of a Bitly URL after the slash (Bitly calls it the back-half) is either random or a custom word the user picks. If that back-half becomes free again, for example after the original link or the account that made it is deleted, whoever claims it controls the redirect. No password is stolen and nothing changes on the brand’s side, so nobody watching the account notices.

Bitly’s help pages say back-halves of deleted accounts can’t be reused, according to Ransomnews, which notes Bitly also deletes accounts that have been inactive for three years. The creation dates on the hijacked links (2026 for links tweeted in 2011) show that reuse did happen. It isn’t the first time: in February 2025, memecoin promoters took over Bitly links in 2013 posts by Donald and Melania Trump, and Bitly was reported to have fixed the bug then.

Two of the Trump links Ransomnews found, re-created in 2024 and 2025, point at domains that copy the names of crypto services (one at a path called “eligibility/check”), which shows how the same trick works for phishing: a link inside an old post from a verified brand or government account borrows that account’s trust.

What it means for developers

Any short link you have published is a redirect you don’t control. If the shortener loses track of it, your old docs, READMEs, release notes, emails and printed QR codes become an open door. Things worth doing this week:

  • Audit your short links. Grep your repos, docs and email templates for bit.ly/ and other shorteners. Adding + to the end of a Bitly link (bit.ly/abc123+) opens its public info page, which shows where it points and when it was created; a creation date after the post that uses it means the link was re-created.
  • Keep the accounts alive. Bitly deletes long-inactive accounts. If your company’s links live in an account nobody logs into, someone should own it.
  • Prefer redirects on your own domain. A short path like example.com/go/docs that your server redirects stays under your control as long as you keep the domain. It is a few lines in most web servers or frameworks; our older post on redirecting pages in PHP shows the basics.
  • Expand links before following them in code. If your app or bot follows user-supplied short links (link previews, crawlers), resolve the final URL and check it against your allow and block lists before fetching or showing it.
  • Watch the domains behind your links. Ransomnews found a replaced link whose target domain was registered again on the day of the wave. A lapsed domain is the same problem one step further down.

We covered a different kind of trust problem on November 14 in the Cursor security incident, where a leaked key led to a fake extension.

Sources