LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

Security

Old Bitly links changed where Burger King and McDonald’s posts sent readers

A familiar account can leave a trusted-looking post behind while a separate redirect changes years later.

Chris on a desert road grips an old signpost arrow that someone has twisted to point down a shady side lot.
Illustration: LockerGnome

An old post can keep its original words and still send somebody to a new destination. Ransomnews found that shortened links in years-old Burger King and McDonald’s posts had been re-created long after the posts were written. The company account provided the familiar wrapper. A separate redirect decided where the click went.

The investigation matters because those are different things to secure. A reader looking at an established account might reasonably trust that the post belongs to it. That observation cannot establish who currently controls a destination behind a shortened URL. The envelope can be genuine while somebody else supplies the forwarding address.

Ransomnews reports checking the redirects and their creation information. Its evidence concerns old links being repurposed; it does not require the corporate accounts themselves to have been compromised. Treating every such click as an account takeover would put the investigation at the wrong door.

Bitly later acknowledged an issue involving “old, inactive links.” Its statement said accounts involved had been suspended and affected links were being disabled. Ransomnews updated its article as the Burger King and McDonald’s examples stopped redirecting and began returning a deactivation page.

That timeline limits what a reader should expect to reproduce. A link that has been disabled after reporting is no longer a live demonstration of the earlier destination. The original post, the investigator’s recorded checks and the provider’s response each establish a different part of the sequence. None should be quietly substituted for another.

For somebody responsible for a company’s old posts, this changes the audit question. Checking who can sign in to the account remains useful. Checking where its published links resolve is another job. A post does not lose its ability to send traffic merely because it has slipped out of the social team’s current spreadsheet.

There is a practical inventory hiding inside that distinction. Keep track of public short links you control, the destinations they should reach, and the accounts responsible for managing them. If a provider identifies an affected link, review the published places that still refer to it. A repaired redirect and an edited post are separate possible actions, depending on what control remains available.

For readers, the familiar account name is evidence about the post’s apparent author, not a guarantee about every later redirect. When a destination is unexpected, stop there rather than assuming the brand must have intended it. You can visit the organization’s own site separately without following the surprising route further.

The report documents particular examples and Bitly’s response. It does not establish that every old shortened link is reclaimable, or that other shortening services use the same lifecycle. The provider’s specific failure and the broader dependency are worth keeping distinct.

Old posts still have working doors.

More Security

Every Security story →