From b0774925d6947a575903e4770c8b5c0e340257e6 Mon Sep 17 00:00:00 2001
From: kymb0 <55473161+kymb0@users.noreply.github.com>
Date: Sun, 22 Jan 2023 00:04:23 +1030
Subject: [PATCH] Update ####2023-01-21-IAM-attacking-AWS.md

---
 _posts/####2023-01-21-IAM-attacking-AWS.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_posts/####2023-01-21-IAM-attacking-AWS.md b/_posts/####2023-01-21-IAM-attacking-AWS.md
index 1b55b3a24ab5..c2088b623bf3 100644
--- a/_posts/####2023-01-21-IAM-attacking-AWS.md
+++ b/_posts/####2023-01-21-IAM-attacking-AWS.md
@@ -60,7 +60,7 @@ We store these secrets in our envrinment variables for our terminal session and
 
 ![stolen_key_auth_success](/assets/images/AWS_1/stolen_key_auth_success.jpg)  
 
-Unfortunately from here however, we discover the account does not have IAM list privileges after trying to list policies. I even tried to enumerate with an AWS exploit tool called ![PACU](https://github.com/RhinoSecurityLabs/pacu) to see if I was missing anything, it was however a dead on the IAM front. When this happened I said "IAM dissapointed"  
+Unfortunately from here however, we discover the account does not have IAM list privileges after trying to list policies. I even tried to enumerate with an AWS exploit tool called [PACU](https://github.com/RhinoSecurityLabs/pacu) to see if I was missing anything, it was however a dead-end on the IAM front. When this happened I said "IAM dissapointed"  
 
 ![dissapointed](/assets/images/AWS_1/dissapointed.gif)  
 ![list_policy_fail](/assets/images/AWS_1/list_policy_fail.jpg)