On November 15, 2026, old Bitly links in tweets from Burger King, McDonald's, Donald Trump and others began pointing to unrelated pages. Nobody hacked the accounts. According to Ransomnews' investigation, the short codes in those old links were re-created on Bitly's side, so every existing copy of each link followed the new owner's destination. If your company has used bit.ly or another public shortener in tweets, docs, emails, PDFs or QR codes, you should audit those links now and move new links to a domain you control.
What happened on November 15
The timeline below comes from Ransomnews, which reconstructed it from Bitly's link-info pages and from posts on X. All times are UTC.
| Time (UTC) | Event |
|---|---|
| Nov 14, 23:52 | Earliest re-creation found: a link in a 2013 Trump tweet now points to a Steam page |
| Nov 15, 05:14 | McDonald's 2011 link re-created and pointed at Wikipedia's 9/11 article |
| Nov 15, 05:32 | Burger King's 2011 link (originally a restaurant locator) re-created and pointed at Wikipedia's list of Nazi concentration camps |
| Nov 15, 06:51 | An X user quotes the Burger King tweet; the post reaches roughly 2 million views |
| Nov 15, 19:13 | Bitly confirms on X that bad actors were able to "repurpose certain old, inactive links" |
| Nov 15, 19:22 | The Burger King and McDonald's links show Bitly's "Link Deactivated" page |
Bitly's statement, as quoted by MediaNama, said: "We have suspended the accounts involved and are disabling the affected links." Bitly also said it was strengthening its safeguards. Burger King told CNN it had no role in the changes and was correcting or deleting the affected posts. MediaNama, summarising CNN, says similar redirects appeared in old posts from Bill Gates, Justin Trudeau, the FBI and others, with most of the affected posts published between 2009 and 2014. Ransomnews notes that it has not independently verified the CNN cases.
The scale is still unknown. In the one account Ransomnews studied in depth, Trump's, 57 of 97 Bitly links from 2009 to 2013 (59%) no longer point to their original destination. Forty-eight of those were re-created within a 17-minute window on May 26, 2023, so for some links the takeover is years old, not days. Most of those 48 still point to plausible destinations, which is why nobody noticed. Ransomnews' own figures are slightly inconsistent in places, and Bitly has not said how many links were affected or how the codes became available.
How short-link hijacking works
A Bitly link has two parts: the domain (bit.ly) and the "back-half," the code after the slash. The back-half is the only thing that ties the link to a destination. If someone else gets control of a back-half, every copy of that link changes with it: in tweets, newsletters, slide decks, PDFs and printed QR codes. No password is stolen and the brand's account is never touched.
Security researchers call this broken-link or dead-link hijacking. It is the same pattern as an expired domain being re-registered, or a deleted S3 bucket name being claimed by someone else. The link outlives the thing it originally pointed to, and whoever controls it next inherits all the trust built up by the original publisher.
Bitly's policy vs. what happened
Bitly's help center says deleting a link does not free up its back-half for reuse. Ransomnews found the opposite in practice: tweets from 2009 to 2012 now contain back-halves whose creation dates fall between 2023 and 2026. Bitly has not explained the gap.
It has happened before. In February 2025, Gizmodo reported that crypto promoters had used a Bitly bug to swap the destinations of links in Trump's and Melania Trump's old tweets to a memecoin site. That bug was reported as fixed and the links were deactivated. The November 2026 re-creations show the same kind of reuse is possible again, or never fully stopped.
Why the November destinations matter less than the method
Most of the November redirects went to Wikipedia pages, game profiles and videos, which looks like trolling. But the method is ideal for fraud. Ransomnews found two re-created Trump links pointing to domains that imitate crypto services, and one aimed at a domain copying World Liberty Financial's name. A link posted by a verified brand account, or printed on a product label, is exactly the kind of link people click without checking.
For a startup, the worst case is not an embarrassing Wikipedia page. It is an old "claim your credits" or "log in here" link in your docs or onboarding emails that now leads to a credential-phishing page carrying your brand.
How to audit your own short links
You can't fix links you don't know about, so start with an inventory. This takes an afternoon for most early-stage companies.
- Collect every short link you've published. Search your website, docs, help center, blog, email templates, README files, app store listings, pitch decks and PDFs for
bit.ly,bitly.com,j.mp,bit.do,tinyurl.com,ow.lyand any other shortener you've used. For a codebase or content repo, a simplegrep -rEo "https?://(bit\.ly|j\.mp|tinyurl\.com|ow\.ly)/[A-Za-z0-9_-]+" .gets most of them. - Pull links out of social posts. X wraps links in
t.co, which hides the Bitly code in the visible post. Ransomnews flags this as a reason the true scope is hard to measure. Download your account archive and search its tweet data for shortener domains rather than scrolling your timeline. - Check each link's creation date. Append a
+to any bit.ly link (for examplebit.ly/abc123+) to open Bitly's info page. Ransomnews used this to show the destination and creation date. If the creation date is later than the post or document containing the link, the code has been re-created by someone else. - Check where each link actually resolves. To see the redirect target without opening it in a browser, run
curl -sI https://bit.ly/abc123 | grep -i "^location". Compare the target with what you meant to link to. - Check links in your own Bitly account too. If you're on a paid plan, the redirect history in Bitly shows every destination a link has had, how many clicks each got and how long each was active. An unexpected entry there points to an internal problem, such as a compromised account or an over-permissioned teammate, rather than a re-created code.
- Fix what you find. Edit or delete posts and pages that contain hijacked links. Report the link to Bitly so it is deactivated for everyone, including copies you can't edit. Replace the link with a direct URL or a link on a domain you own.
- Record what you checked. Keep a simple sheet of each link, where it appears, its intended target and its creation date. That sheet is the starting point for the registry described below.
Printed QR codes need special attention. You can't edit a printed code, so if one encodes a public-shortener link that turns out to be hijacked, the only fixes are getting the link deactivated and replacing the printed material.
Choosing a safer short-link setup
The underlying problem is that on a shared public domain like bit.ly, you don't control the namespace. Somebody else's account, bug or policy change decides who owns a code. The fix is to put your links on a domain only you can write to.
| Setup | Who controls the codes | Can you change destinations later? | Main risk |
|---|---|---|---|
| Free links on a public shortener domain (bit.ly, etc.) | The shortener | Depends on plan; Bitly says redirects are a paid feature | Code reuse, policy changes, account lapses |
Paid shortener with your own short domain (e.g. go.yourco.com) |
You (on your domain) and the vendor's platform | Yes, on plans that include redirects | Vendor lock-in; letting the domain or plan lapse |
| Self-hosted shortener (e.g. Shlink, MIT-licensed) on your domain | You | Yes | You operate and patch it |
Plain redirects on your main site (yourco.com/go/launch) |
You | Yes, via config or code | No click analytics unless you add them |
For most startups, either of the middle two options is the right default. A branded short domain means nobody else can claim go.yourco.com/pricing, and you keep the ability to repoint links when pages move. Self-hosting with a tool like Shlink, which offers REST and CLI interfaces and an official Docker image, avoids per-link pricing but adds one more service to maintain.
Two rules apply to whichever you choose:
- Never let a short domain expire. If you stop renewing
go.yourco.com's parent domain, every link on it becomes available to whoever registers it next, which is the same hijack at a bigger scale. Put short domains on auto-renew and include them in your domain inventory. - Retire links, don't abandon them. When a campaign ends, point the link to a relevant live page instead of deleting it. A link that resolves somewhere sensible is harder to misuse than one that 404s.
If you're building UTM-tagged campaign links for a launch, generate them on your own domain from the start. Our free UTM Builder produces clean links that you can then wrap in your own short domain rather than a public one.
What this means if you build link or QR products
If you run a shortener, a link-in-bio tool, a QR code generator or any product that issues public identifiers, this incident is a design lesson:
- Make identifiers permanent. Once a code has resolved publicly, it should never be issuable again, even after deletion, account closure or plan downgrade. Enforce this in the database, for example with a tombstone table, and not only in a help-center article.
- Expose creation dates and destination history publicly. Bitly's
+page is what let outsiders spot the re-created links. Users can only check what you show them. - Rate-limit and flag bulk creation of short or "vintage-looking" codes. Forty-eight of the re-created Trump links were made in 17 minutes, per Ransomnews. Bulk creation of codes that match historical links should trigger a review.
- Let customers verify links. An export of every link a workspace has created, with creation dates and current targets, makes audits like the one above much faster.
QR menu and QR marketing tools face the same risk, with higher stakes, because their codes are printed. If you're comparing vendors, ask them directly what happens to a code when an account is cancelled.
What to watch and what to do now
Bitly has not yet said how the back-halves became available, how many links were affected or whether all re-created links have been disabled. MediaNama lists all of these as open questions. Watch for a technical post-mortem from Bitly and for whether other public shorteners turn out to have the same weakness.
In the meantime:
- Today: Search your website, docs and email templates for public shortener links and check the creation date of each one with the
+trick. - This week: Go through your social archive, especially old posts from accounts with large followings, and report any re-created links to Bitly.
- This month: Move new links to a short domain you own, set it to auto-renew, and keep a registry of every link and QR code you publish.
Short links are cheap to create and easy to forget. This incident shows that a forgotten link can still be used against your brand years after you posted it.
Frequently asked questions
Were Burger King's and McDonald's accounts hacked in the Bitly incident?
No. Ransomnews found that the X accounts were not compromised. The old Bitly short codes in their 2011 tweets were re-created on Bitly on November 15, 2026 and pointed to new destinations, so the tweets never changed but the links did.
How can I tell if a Bitly link has been hijacked?
Add a plus sign to the end of the link (for example bit.ly/abc123+) to open Bitly's info page, which shows the destination and creation date. If the creation date is later than the post, email or document the link appears in, the short code has been re-created and someone else controls it.
Can a deleted Bitly back-half be reused by someone else?
Bitly's help pages say deleted back-halves cannot be reused. However, Ransomnews found tweets from 2009 to 2012 whose Bitly codes now show creation dates between 2023 and 2026, and Bitly confirmed that bad actors were able to repurpose certain old, inactive links. Bitly has not explained how that happened, so don't rely on the policy alone.
What is the safest way for a startup to use short links?
Use a short domain you own, either connected to a paid shortener plan or running a self-hosted shortener such as Shlink, and keep a registry of every link you create. That way nobody else can claim a code on your domain, and you can still change or retire destinations later. Keep renewing the domain, because a lapsed short domain hands every link on it to whoever registers it next.
Should I delete old tweets that contain hijacked links?
For tweets that matter, deleting or replacing them is the quickest fix, which is what Burger King said it was doing. Also report the link to Bitly so it gets deactivated, because copies of the link may live on in emails, PDFs, screenshots and printed QR codes you can't edit.
Sources
- Ransomnews: Old Bitly links hijacked in Burger King, McDonald's and Trump tweets— ransomnews.com
- MediaNama: Old Bitly links in Trump, Burger King X posts hijacked— medianama.com
- Gizmodo: Crypto hackers edit Trump's old tweets via Bitly bug (February 2025)— gizmodo.com
- Bitly blog: How to redirect a Bitly link— bitly.com
- Bitly Support: Can I hide, delete or archive a link in Bitly?— support.bitly.com
- Shlink: self-hosted URL shortener (GitHub)— github.com
