Individual skill
exploiting-broken-link-hijacking
Discover and exploit broken link hijacking vulnerabilities by identifying references to expired domains, decommissioned cloud resources, and dead external services that can be claimed by an attacker.
internal/tools/skills/data/web-application-security/exploiting-broken-link-hijacking/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,325
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- broken-link-hijacking Declared skill tag
- blh Declared skill tag
- subdomain-takeover Declared skill tag
- dead-link Declared skill tag
- expired-domain Declared skill tag
- supply-chain Declared skill tag
- external-resource Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Exploiting Broken Link Hijacking
## When to Use
- When auditing web applications for references to expired or unclaimed external resources
- During supply chain security assessments of third-party script and resource dependencies
- When testing for subdomain takeover opportunities via dangling CNAME records
- During bug bounty hunting for broken link hijacking vulnerabilities
- When assessing the security of external resource dependencies in production applications
### How to CONFIRM a Hit (avoid false negatives)
- **Positive signal**: the broken/dead reference points to a resource you can **actually claim** (expired domain registrable, deleted S3 bucket recreatable, unclaimed GitHub Pages/social handle) AND, once claimed, your content is served where the target loads it — confirm with a **benign canary**.
- A `404`/`000` on a linked resource is a candidate, not a confirmed hijack — the domain or namespace must be genuinely **available to register/claim**.
- Do NOT conclude "vulnerable" until you have: