From dfe83d95edb230a21b44cc53e06550c349615a04 Mon Sep 17 00:00:00 2001
From: MaxToffy <91328785+MaxToffy@users.noreply.github.com>
Date: Mon, 29 Jul 2024 10:24:49 +0200
Subject: [PATCH] Replacing dead link

---
 windows-hardening/ntlm/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows-hardening/ntlm/README.md b/windows-hardening/ntlm/README.md
index 4317b842c..127d536d7 100644
--- a/windows-hardening/ntlm/README.md
+++ b/windows-hardening/ntlm/README.md
@@ -194,7 +194,7 @@ The **challenge length is 8 bytes** and **2 responses are sent**: One is **24 by
 
 The **second response** is created using **several values** (a new client challenge, a **timestamp** to avoid **replay attacks**...)
 
-If you have a **pcap that has captured a successful authentication process**, you can follow this guide to get the domain, username , challenge and response and try to creak the password: [https://research.801labs.org/cracking-an-ntlmv2-hash/](https://research.801labs.org/cracking-an-ntlmv2-hash/)
+If you have a **pcap that has captured a successful authentication process**, you can follow this guide to get the domain, username , challenge and response and try to creak the password: [https://research.801labs.org/cracking-an-ntlmv2-hash/](https://www.801labs.org/research-portal/post/cracking-an-ntlmv2-hash/)
 
 ## Pass-the-Hash