> For the complete documentation index, see [llms.txt](https://www.webhackingtips.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.webhackingtips.com/week-39-broken-link-hijacking.md).

# Week 39 - Broken Link Hijacking

This week’s web hacking tip is on Broken Link Hijacking!\
\
This attack occurs when a threat actor can take over an obsolete or outdated link to an external resource or URL on your website. It is especially dangerous when the external link is to a JavaScript file that no longer exists. An attacker can register the resource domain/subdomain, upload their own malicious JavaScript file, and instantly have Stored XSS!\
\
You can manually check for broken links by opening the Developer Tool’s web console, or use the following tool to automate the process: <https://github.com/stevenvachon/broken-link-checker>\
\
Surprisingly, this type of vulnerability doesn’t get too much attention when it comes to Bug Bounties or Penetration Tests. It’s quick and easy to check for and can be incredibly dangerous when discovered.

![](/files/5UfJFRLFbKRxRWq4q8BK)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.webhackingtips.com/week-39-broken-link-hijacking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.