exploiting-broken-link-hijacking

Detect and exploit broken link hijacking by claiming expired domains and decommissioned cloud resources.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill exploiting-broken-link-hijacking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploiting-broken-link-hijacking
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/web-application-security/exploiting-broken-link-hijacking
Command: npx skills add https://github.com/xalgord/xalgorix --skill exploiting-broken-link-hijacking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often reference external resources such as scripts, S3 buckets, GitHub Pages sites, and social handles that later expire or get decommissioned, leaving a gap attackers can claim to inject content or steal data. This Skill provides a structured workflow to find those dead references, verify they are genuinely claimable, and prove impact with a benign canary.

Core Features & Use Cases

  • Dead Reference Discovery: Crawl targets with broken-link-checker, extract external scripts, CSS, and historical links from the Wayback Machine, and flag 404/000 responses.
  • Takeover Verification: Match service-specific fingerprints (NoSuchBucket, GitHub Pages, Heroku, Azure, Shopify) and use subjack or nuclei takeover templates to confirm a resource is actually registrable, avoiding false positives.
  • Proof-of-Concept Exploitation: Claim the expired domain, S3 bucket, or GitHub Pages repo, serve a benign canary, and assess impact such as full XSS via hijacked JavaScript.
  • Use Case: During a bug bounty engagement, you find the target loads analytics JS from an expired domain; you register the domain, serve a benign marker, and report a confirmed supply-chain XSS finding.

Quick Start

Ask the AI to crawl the authorized target site for dead external links and check whether any referenced domains or cloud resources are claimable for a broken link hijacking proof of concept.

Frequently Asked Questions about exploiting-broken-link-hijacking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find broken link hijacking vulnerabilities on a website?

Crawl the target with broken-link-checker to list dead external links, then extract script, CSS, and historical references from page source and the Wayback Machine. Check each dead reference with whois or HTTP status to see if the underlying domain or cloud resource is claimable.

How to check if a subdomain takeover is possible?

Resolve the subdomain's CNAME and check whether the target service responds with a takeover fingerprint such as NoSuchBucket, GitHub Pages 404, or Heroku 'No such app'. Tools like subjack and nuclei takeover templates automate this fingerprint matching.

What tools detect subdomain takeover and dead links?

broken-link-checker finds dead links via crawling, subjack and nuclei detect takeoverable services using fingerprint databases, and the can-i-take-over-xyz list documents which services are vulnerable. The Wayback Machine helps surface historical external references.

Does a 404 on an external link confirm broken link hijacking?

No, a 404 or failed DNS response is only a candidate. You must confirm the domain is actually registrable via whois or that the cloud resource is recreatable, then ideally claim it and serve a benign canary to prove the target loads your content.

What is the impact of a hijacked external JavaScript reference?

A hijacked script source gives the attacker full JavaScript execution on every page that loads it, equivalent to stored XSS for all visitors. Lower-impact cases include dead images or CSS, which enable defacement, phishing, or tracking rather than code execution.

Is broken link hijacking testing legal?

It is only legal on systems you own or have written authorization to test, such as within a bug bounty scope. The Skill includes a legal notice stating unauthorized use may violate computer fraud laws.