Skip to main content
Blog
Back to Blog

Old Bitly links hijacked: how to check the short links in your old posts

On November 14 and 15, 2026, bit.ly links in years-old posts from Burger King, McDonald's and Donald Trump started sending people to unrelated, and in some cases offensive, pages. Nobody had logged into those accounts: someone had re-created the old short links and pointed them somewhere new. If you have been posting about your product for a few years, your launch posts, README, newsletter archive, pitch deck or printed QR codes may contain bit.ly links too. This guide is for a founder or small team that wants to know which of those links are still theirs: a 30-second check for one link, a script that lists every bit.ly link in your X archive, what to do with each result and how to stop it happening again. It is useful without a Soloop account and is not a statement from Bitly.

The short answer

Add a plus sign to the end of a bit.ly link, for example bit.ly/abc123+, and open it. Bitly shows the destination and the date the link was created, without sending you there. If the creation date is later than the date of your post, the link is no longer the one you shared: someone else created it and decides where it goes.

Delete or replace posts whose links were re-created, report those links to Bitly, and update the places you can still edit. For anything you publish from now on, use links on a domain you own, so nobody else can claim them.

What happened on November 14 and 15, 2026

A bit.ly link has two parts: the domain and the back-half, the short code after the slash. According to reporting by Ransomnews, old links in posts from 2011 by Burger King and McDonald's were re-created during the night of November 14 to 15 (UTC) and pointed at unrelated Wikipedia pages. The posts were not edited and the accounts were not accessed, so the brands had no sign of a compromise until people noticed.

Later on November 15, Bitly said on X that it had found an issue that let bad actors repurpose certain old, inactive links, that it had suspended the accounts involved and was disabling the affected links. Bitly has not said how many links were affected, how the back-halves were claimed or which links were at risk. Its help center says a deleted link's back-half cannot be reused; this incident shows that, at least for some old links, someone else was able to create them again.

Bitly

"Earlier today, 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."

Bitly on X, November 15, 2026
Timeline

Burger King's 2011 link was re-created at 05:32 UTC and McDonald's at 05:14 UTC on November 15; neither account posted anything. Both links returned HTTP 410 (gone) when we checked on November 16.

Ransomnews: Old Bitly links hijacked

Where your old short links are

Start with the places strangers still find years later, and the ones you cannot edit.

  • Posts on X and LinkedIn, including pinned posts and launch threads.
  • Your GitHub README, documentation, changelog and old release notes.
  • Launch pages on Product Hunt, Hacker News, Indie Hackers and app store listings.
  • Newsletter archives on Substack, Mailchimp or Beehiiv, and old email sequences that still send.
  • Pitch decks, PDFs, slides and conference talks people still download.
  • Printed QR codes on packaging, flyers or business cards: a Bitly QR code opens a short link, so it has the same problem.
  • Email signatures, link-in-bio pages and your own website's old blog posts.

Fix posts you cannot edit

X lets some accounts edit a post only for a short time after publishing, so for an old post you can delete it, or reply to it with the correct link and a short note, then pin the reply or the updated post if it matters. LinkedIn lets you edit the text of your own posts. On launch sites, check whether you can edit the listing; if not, ask the site's support to update the link.

For printed QR codes you cannot recall, keep the original Bitly account active and check those links regularly. If a code's link was re-created, report it to Bitly and stop handing out that print run.

Worked example: three years of launch posts

This example is invented to show the workflow. A founder has posted about a scheduling tool on X since 2023. They download their X archive, run the script and get 23 unique bit.ly links.

  1. They open all 23 "+" pages over two evenings and fill in the creation date and status.
  2. 18 links were created on the day of the post: original. 2 were created in 2025, long after the posts, and still point to the product's old pricing page. 3 are disabled. 18 + 2 + 3 = 23.
  3. The 2 re-created links are in a pinned launch thread. The founder deletes the thread, posts a new one with yourproduct.com/launch and pins it, and reports both links to Bitly.
  4. The 3 disabled links are in old replies nobody reads; the founder deletes those replies.
  5. They replace the 18 original links in the README and docs with links on their own domain, and add a quarterly reminder to check the links left in old posts.

What Bitly has not said

  • How the old back-halves were claimed, and whether the cause is fixed.
  • How many links were affected, and in which years.
  • Whether links from free, deleted or inactive accounts were more exposed.
  • Whether re-created links that point somewhere plausible will also be disabled.
  • Whether original owners can get re-created links back.

Where Soloop fits

Soloop does not shorten links, scan your old posts or edit or delete posts on any platform. Use the steps above and each platform's own tools for the audit.

Soloop helps with what you publish next: according to the Soloop manual, it can research a market with sources, write and publish X posts and replies through a connected account, send outreach through a connected Gmail account and prepare Google Ads search campaigns after setup and payment, with actions waiting for your approval by default. Check the links in a draft before you approve it.

Sources, limitations and refresh

Bitly's statement, the Ransomnews report, the DEV Community audit and Malwarebytes' report were read on November 16, 2026. Bitly's help center blocks automated reading, so its no-reuse and no-expiry statements are taken from its published articles as shown in search results. We checked the "+" page and the status of the Burger King, McDonald's and one re-created link ourselves on November 16. The script was tested on a sample archive in the format X uses; the decision table, prevention list and worked example are editorial guidance, and the example is invented.

This guide will be reviewed by February 16, 2027, or sooner if Bitly explains the cause, restores original links or changes how back-halves can be claimed.

Product capability

The Soloop manual describes research with sources, X posting through a connected account, Gmail outreach and Google Ads search campaigns after setup and payment; approval comes first by default. It does not shorten or audit links.

Soloop product manual