---
id: "CMP-202611-taqwyk"
page: "https://infrastack.ai/live/CMP-202611-taqwyk"
kind: "campaign"
aliases: []
title: "Old Bitly short links hijacked: a Bitly flaw let attackers re-point expired bit.ly links in brands' old posts (McDonald's, Burger King, Trump) to new destinations"
severity: "medium"
cvss: null
epss: null
exploited: true
status: "open"
category: "vendor"
products: [{"name": "Bitly", "fixed": [], "vendor": "Bitly"}]
ecosystems: []
tags: ["campaign", "early-warning"]
not_affected_if: []
published_at: null
first_seen_at: "2026-11-16T20:38:32+00:00"
updated_at: "2026-11-16T20:39:12+00:00"
sources: [{"source": "analyst", "url": null, "first_seen_at": "2026-11-16T20:38:32+00:00"}]
exploit_sources: []
---

# Old Bitly short links hijacked: a Bitly flaw let attackers re-point expired bit.ly links in brands' old posts (McDonald's, Burger King, Trump) to new destinations

Link for people: https://infrastack.ai/live/CMP-202611-taqwyk (this .md is for agents)

Since about 15 Nov 2026, attackers have abused a flaw Bitly confirms in how it handles expired or inactive links. It let them make old bit.ly short links point somewhere new. Links in genuine old posts from McDonald's, Burger King, KFC, Donald Trump and others (some from 2009-2011) were redirected to unrelated or offensive pages, so far mostly Wikipedia pages and memes. The posts and the accounts themselves were not touched. Bitly says it suspended the accounts involved and is disabling the affected links. It has not said what the root cause is or how many links were affected. No phishing or malware destinations have been reported yet, but any old bit.ly link in your docs, READMEs, emails, QR codes or social posts could have been re-pointed.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- :Bitly affected range not listed fixed no fixed version listed

## Cause

How the attacker got in: not disclosed yet (unknown). Bitly confirms a flaw in how it handles expired links that let attackers re-point bit.ly links, but it has not said what the root cause is, so how the attacker got in is unknown.

How it reached others: customers' data or keys went with it (third-party-breach).

Last month's incidents with the same cause, and the full checklist: https://infrastack.ai/live/breaches.md#third-party-breach

## How to check

Find bit.ly links your organization has published (docs, READMEs, install instructions, marketing posts, printed QR codes), especially old or expired ones. Check where each one leads now, for example by adding '+' to the end of the bit.ly URL to see its preview, or by running it through a link checker without opening it. Any link that no longer reaches your own site, or now shows Bitly's 'You've got the wrong address' error page, was affected. For forwarded messages: a bit.ly link in an old, genuine brand post that now opens an unrelated page.

## Fix

Replace bit.ly links in your docs and posts with direct URLs or links on a domain you control. Check the destinations of any Bitly links you still own in your Bitly account. Until Bitly publishes a root cause, don't trust a short link just because the post it sits in is genuine.

## Timeline

- 2026-11-16T20:38:32+00:00 analyst

## Documents

- [describes] Hijacked Bitly links turn old brand posts into offensive redirects (Malwarebytes) https://www.malwarebytes.com/blog/news/2026/11/hijacked-bitly-links-turn-old-brand-posts-into-offensive-redirects
- [discussion] @SocketSecurity: Bitly link jackers have it their way 🍔 https://t.co/JN4YAk9jU9 https://x.com/SocketSecurity/status/2122422869762142512

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
