Someone re-registered old Bitly links, and 2011 tweets from Burger King and McDonald's now point elsewhere
Bitly says bad actors repurposed old, inactive bit.ly links. Links in 2011 Burger King and McDonald's tweets now open Wikipedia pages about Nazi camps and 9/11.

At 05:32 UTC on November 15, a short link in a Burger King tweet from July 24, 2011 — the one promoting its restaurant locator — was re-created, and its destination changed to Wikipedia’s list of Nazi concentration camps. Eighteen minutes earlier, a link in a June 7, 2011 McDonald’s tweet, bit.ly/mLWJO0, was re-created the same way and pointed at Wikipedia’s article on the September 11 attacks. Both tweets were posted from their original accounts and were taken down or hidden later on November 15. Nobody broke into those accounts. What changed was the destination, on Bitly’s side.
Key points
- Two 2011 links, one night: the McDonald’s link was claimed at 05:14 UTC on November 15 and the Burger King link at 05:32 UTC, both landing on Wikipedia pages unrelated to the original posts.
- It is not just those two: Ransomnews checked 97 bit.ly links in Trump tweets from 2009 to 2013. Fifty-six were created after the tweet that contained them, seven led somewhere unrelated, and one was blocked by Bitly as malicious.
- Bitly confirmed it at 19:13 UTC: the company said an issue “allowed bad actors to repurpose certain old, inactive links,” suspended the accounts involved and began disabling affected links. Its status page still listed redirect services as operational on November 16.
What happened
The sequence started before dawn UTC and hit two tweets more than a decade old within 18 minutes of each other.
| Account | Original tweet | Short link | Re-created (UTC) | New destination |
|---|---|---|---|---|
| Burger King | 2011-07-24, restaurant locator promo | bit.ly/19BFiM | 2026-11-15 05:32 | Wikipedia, list of Nazi concentration camps |
| McDonald’s | 2011-06-07 | bit.ly/mLWJO0 | 2026-11-15 05:14 | Wikipedia, September 11 attacks |
| Trump (sample) | 2009–2013, 97 links | 7 pointed elsewhere | 4 registered 07:49–09:57 | A Roblox profile, YouTube videos, Wikipedia on Trump and Epstein |
Ransomnews logged the rest in order. At 06:51 UTC an X user quote-tweeted the Burger King post; by the afternoon that quote had passed 2.2 million views. By 13:45 UTC the Burger King post itself was unavailable, and at 14:20 UTC the McDonald’s tweet returned not-found — yet both links still redirected at 15:05 UTC. Bitly posted its statement at 19:13 UTC, and at 19:22 UTC both links showed “Link Deactivated.” A third check at 23:35 UTC found the seven anomalous links dead, but 49 re-created links that still matched their original content were working as before.
Those 49 deserve a closer look. Forty-eight of them were created in a roughly 17-minute window on May 26, 2023, and most point to Trump’s YouTube channel or news pages. Re-registering dead links was already happening at batch scale three years ago; nobody noticed then.
How a short link changes hands
The part of a bit.ly address after the slash is the back-half. Bitly generates it at random by default, and users can pick their own. Once a link stops existing — the account is closed, the link is deleted, the account goes inactive — that back-half can become claimable again, and whoever claims it decides where it points. Every old tweet, email, PDF, menu, package and QR code that spelled out those characters follows the new destination.
Bitly’s own help center is blunt about the intent: “Previous back-halves cannot be reused with the same domain.” A separate help page says accounts inactive for three years are deleted. Ransomnews cites a February 2025 Disruptionist report that a bug let people claim a back-half after the original link or account was deleted or deactivated, and that Bitly fixed it and disabled the hijacked links at the time. The November creation dates sit awkwardly beside the “cannot be reused” wording.
Nothing in this involves a stolen password, and no one logged into the Burger King or McDonald’s accounts. The original poster sees nothing change: click counts, post appearance and account status all look normal, while the destination moves on Bitly’s side. The motive is not mysterious either. A link quoted for fifteen years carries distribution, search authority and print credibility, and claiming a back-half costs nothing. If the new destination’s own domain later lapses, the same link can be reassigned once more.
What others say
Bitly’s statement is the only first-party response so far. In its post on X, the company said it had identified an issue that “allowed bad actors to repurpose certain old, inactive links to redirect people to content unrelated to the original posts,” said it had suspended the accounts involved and was disabling affected links, and said its Trust and Safety team was working on protections against similar misuse.
CNN’s reporting that evening widened the scope. It found redirected links in old posts from Trudeau, Mike Pence, the FBI and the US Department of Defense, plus at least a dozen in Trump’s own account, and another Burger King post that opened Wikipedia’s article on Adolf Hitler; the wave appeared confined to posts from 2009 to 2014. Burger King told CNN it had “no involvement” in the redirects and was “working quickly to correct and delete” the altered posts. McDonald’s did not immediately respond, and neither Bitly nor X answered CNN’s request for comment.
Ransomnews states plainly that it did not independently verify the links CNN listed. Its own checks found no public statement from Bitly, Burger King or McDonald’s as of 14:30 UTC — nearly five hours before Bitly acknowledged the issue on X. One more inconsistency: on November 16, Bitly’s status page listed both link shortening and redirects as operational, with no incident recorded.
Our take
The lesson is not that someone did something bad. It is that a short link is borrowed infrastructure. The characters live in your post; control of the destination lives with the vendor. Once the vendor permits back-half recycling, every asset you distributed years ago becomes somebody else’s doorway. For brands and public accounts, any short link pushed at scale before 2014 should now be treated as an untrusted asset, ranked alongside weak passwords in an audit.
What remains unanswered matters too. Nobody has said who re-created 48 Trump links in 17 minutes in May 2023 — an archive project and a marketing team are both plausible. Bitly has not published a root cause, the total number of affected links is unknown, and it is unclear whether the recycling is intended behavior or another bug. The gap between the status page and the incident says the existing monitoring covers availability, not destination integrity, and destination integrity is where this failure actually lives.
For developers, the practical reading is that a short link should be a disposable hop, not a permanent address. Unlike the fake invitations in AI event invite phishing, this attack reuses links that genuinely existed and were genuinely trusted, so “suspicious domain” gives defenders nothing to work with.
What to check
- Inventory the links you still depend on. Export your Bitly links (dashboard CSV or API) and pull out every short link that appears in tweets, emails, PDFs, packaging or QR codes, with its intended destination noted.
- Monitor the destination, not the uptime. Resolve those links on a schedule and diff the result against the recorded target; alert on any change. This incident surfaced because someone happened to click a link in their timeline.
- Move to a domain you own. Serve 301s from your own brand domain so a vendor switch does not mean new links, and the destination stays under your control. Keep third-party shorteners as a hop only.
- Fix what is already published. A post with a deactivated link stays up, and “Link Deactivated” is a dead end for readers; edit the post or add a correction. The same ownership gap shows up in Yandex’s cloud data loss: what you store with someone else is not automatically under your control.