Old Bitly links are being hijacked
Old Bitly URLs from deactivated accounts are being re-registered and redirected to prank or malicious destinations, highlighting long-predicted risks of third-party link shorteners. Commenters argue that outsourcing shortened URLs and QR redirects creates a fragile layer of indirection that can rot, be hijacked, or turned into paywalled scams, especially when embedded in tweets, books, SMS, or physical media. Many advocate self-hosted shorteners on a company’s own domain—or avoiding shorteners entirely—in favor of more stable URLs and first-party analytics.
How the Bitly hijack works
- Old Bitly links tied to deleted/inactive accounts were freed and reissued; new owners can point them anywhere.
- Some see disabling affected links as sufficient; others argue Bitly should restore original targets, but critics say that’s on the original brands for “renting” URLs from a third party.
- Commenters note this outcome was predicted years ago: any recycled identifier (URLs, usernames, subdomains) will eventually be abused.
Security, abuse, and related attack patterns
- Link shorteners are described as “waiting to get abused,” especially when hiding destinations in contexts like
curl | bash. - Similar risk: “dangling DNS” where CNAMEs point to domains that later lapse and are bought by spammers/malware operators. CT logs and subdomain search tools are cited as discovery mechanisms.
- Shorteners and high‑reputation domains are attractive to scammers because they can bypass filters and user suspicion.
Debate on value of link shorteners
- Pro‑shortener points:
- Short links help in SMS, early Twitter limits, podcasts, printed material, and QR codes (less dense codes scan more reliably).
- Provide per‑campaign analytics, affiliate tracking, A/B tests, and easier link generation for non‑technical marketers.
- Anti‑shortener points:
- They hide the real destination and facilitate phishing.
- They create systemic link rot; when a shortener dies or repurposes links, large swaths of the web break with no way to infer the original URL.
- In an era of search, QR codes, and browser history, many argue the practical need has mostly disappeared.
Self‑hosting vs third‑party services
- Broad agreement that if shorteners must exist, they should be run on your own domain (e.g.,
example.com/r/slug) for better control and permanence. - Marketing teams often bypass internal tech and sign up for third‑party tools, leading to exactly these long‑term failures.
- Some suggest whitelisting only top domains in new shorteners, but others warn this doesn’t prevent abuse on user‑generated‑content platforms and requires careful use of the Public Suffix List.
Business models, Trust & Safety, and scams
- Shorteners make money from marketing analytics, click‑through data, and sometimes ads; at least one major provider reportedly has substantial revenue and staff, including Trust & Safety.
- Commenters describe QR/short‑URL services that offer “free” codes but later ransom them behind subscriptions, likened to earlier image‑hosting bait‑and‑switches.
- Consensus: any public URL shortener attracts large volumes of scams and malware, effectively requiring a Trust & Safety function to survive.
Cultural and meta reactions
- Many find the specific corporate tweet hijacks darkly funny; others are “tired of people ruining it for the rest of us.”
- Several readers criticize the linked article as slow, shallow, and likely AI‑generated, saying the thread explains the incident more clearly than the piece itself.