Bitly Says Bad Actors Repurposed Old Links in Burger King, McDonald's and Trump X Posts
Security / news
Bitly Says Bad Actors Repurposed Old Links in Burger King, McDonald's and Trump X Posts
Short links in posts from 2009 to 2014 now open unrelated pages. Bitly has not said how the identifiers were reclaimed, and nobody has published a count.

Old Bitly short links embedded in X posts from Burger King, McDonald's, Donald Trump and others began redirecting to unrelated pages on November 15, 2026. Bitly said it "identified an issue that allowed bad actors to repurpose certain old, inactive links" and that it suspended the accounts involved. No X account was compromised, because the posts themselves are unchanged. Only the destination behind each link moved.
Bitly's statement, posted on X on Sunday afternoon, is quoted in reporting that KSL attributes to CNN and that MediaNama also summarised. The company said its Trust and Safety team is working to strengthen protections against similar misuse. It did not say how the links were reclaimed.
Which links moved
The affected links date from roughly 2009 to 2014. The reporting lists these examples.
| Account | Post | Now opens |
|---|---|---|
| Burger King | July 24, 2011 | Wikipedia's list of Nazi concentration camps |
| McDonald's | June 7, 2011 | Wikipedia's article on the September 11 attacks |
| Donald Trump | 2013 wind turbines post | A page with a baby photo |
| FBI | 2012 "Ghost Clicks" post | A page with a seal photo |
KSL, citing CNN, says at least a dozen Trump posts were affected. Bill Gates, Justin Trudeau, Mike Pence, McDonald's Indonesia, the FBI and the Department of Defense also appear in the list. Neither outlet gives a total count of links.

How a link gets hijacked
MediaNama describes the technique as dead link hijacking. If the account behind a short link is deleted or the destination disappears, another party may be able to claim the identifier and redirect every existing use of it. MediaNama says Bitly's help documentation states that identifiers cannot be reused after an account is deleted. That documentation returned an access error when The Terminal tried to fetch it, so the claim rests on MediaNama's account.
Bitly does delete inactive accounts. Alex Chan, who writes at alexwlchan.net, recorded that Bitly emailed Chan on February 6, 2025 saying an account with no logins in three years would be deleted in 30 days. Chan wrote that links on bit.ly keep working after deletion, and the note does not say whether deleted link names could be reassigned. MediaNama also cites a February 2025 report of a reuse bug that had been fixed.
The attack does not need a vulnerability in X. It needs a gap between what Bitly's policy says and what its systems did. Bitly has not said which side of that gap it found.
What the redirects did
The destinations seen so far are vulgar or random, not malicious. MediaNama contrasts this with an earlier Bitly incident in which links in older Trump posts pointed to a memecoin site. The commercial motive was clear there. Here it appears to be trolling.
Harmless destinations understate the risk. A redirect to Wikipedia harms no one's device. A redirect to a credential form would, and the same mechanism would deliver it, from an account people trust.
Ari Lightman, a digital media professor at Carnegie Mellon University's Heinz College, told CNN that unmonitored social accounts are problematic and that the links could be exploited at scale. Short links also sit in emails, PDFs, slide decks and QR codes, per MediaNama, where nobody is watching them.
What is still unknown
Bitly has not named the number of links, the number of accounts suspended, or the mechanism. Burger King told CNN it had no role in the changes and was correcting or deleting the posts. McDonald's had not responded when MediaNama published. Bitly and X did not respond to CNN's request for comment.
Organisations that posted Bitly links before 2015 should search their archives for them and test each one. Related reading: the GPUStack authentication bypass shows what exploitation in the wild looks like when a source confirms it, and the Coway Airmega report covers another case of trust placed in something nobody was watching.
Sources
More in Security
- 01Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a PatchA one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
- 02NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits ThemThe reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
- 03CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 04CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.