Skip to content

Commit 531f23f

Browse files
committed
fix(secu-spoofing): Workshop formatting
1 parent 7000f13 commit 531f23f

File tree

1 file changed

+41
-14
lines changed

1 file changed

+41
-14
lines changed

security/spoofing/README.md

Lines changed: 41 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
# PoC Security | Spoofing Workshop
1+
# Workshop Spoofing
22

3+
✔️ Learn how to create an SMTP server
34

4-
### In this workshop you will learn:
5-
- How to create SMTP server
6-
- How to spoof an email
7-
- How to create evil proxy
5+
✔️ Discover how to spoof an email
6+
7+
✔️ Create an evil proxy
88

99
## Setup
1010
!!!! CHECK YOUR EMAIL !!!
@@ -19,21 +19,24 @@ Once you have the private key, you can connect to the server using the following
1919
`ssh -i id_rsa root@<IP>`</br>
2020

2121
The next step is to install prerequisites for the workshop:
22-
> sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
22+
```
23+
sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
2324
24-
> sudo apt install mailutils && sudo apt install sendemail
25+
sudo apt install mailutils && sudo apt install sendemail
2526
26-
> sudo dpkg-reconfigure postfix
27+
sudo dpkg-reconfigure postfix
28+
```
2729

2830

2931
## Step 1: SMTP server
32+
3033
- Setup relay restrictions
3134
- Configure hostname and network
3235
- Specify send-only parameters
3336
- Set spoofed masquerade
3437

3538
To get the flag, send your postfix configuration in `/etc/postfix/main.cf` to a PoC Security administrator.</br>
36-
You can send it in `workshop-spoofing@proton.me` with your Epitech email addres with the following subject: `SMTP server`.</br>
39+
You can send it in `workshop-spoofing@proton.me` with your Epitech email address with the following subject: `SMTP server`.</br>
3740

3841
If you have not received the flag after 5 minutes, please contact a PoC Security member.
3942

@@ -56,28 +59,52 @@ The subject is the same that the previous step but the content must be original
5659
It must contain the PoC logo and the text must be colored.</br>
5760
You're free to put whatever you want in the email.</br>
5861

59-
> Hint: think how to embeded html code in the email.
62+
> 💡 Hint: think how to embed html code in the email.
6063
6164
## Step 4: Evil Proxy
6265
The evil proxy will be able to intercept all the traffic and redirect it to a server of your choice.</br>
63-
In our case, the proxy will redirect all the traffic to the PoC Innovation github url: `https://github.com/PoCInnovation` </br>
66+
In our case, the proxy will redirect all the traffic to the PoC Innovation github url: [https://github.com/PoCInnovation](https://github.com/PoCInnovation) </br>
6467
Before redirect, it must implement a login page to get the admin password.</br>
6568
The login page must be a real phishing page.</br>
6669

6770
Here is a sample scheme of the evil proxy:
6871

6972
![](https://tse2.mm.bing.net/th?id=OIP.mdfWRGSKWIDDqEqd7_BV6gHaDC)
7073

71-
I recommand to use [EvilGinx2](https://github.com/kgretzky/evilginx2) to create the evil proxy and [Freenom](https://www.freenom.com/en/index.html?lang=en) to get a free domain name.</br>
74+
We recommend to use [EvilGinx2](https://github.com/kgretzky/evilginx2) to create the evil proxy and [Freenom](https://www.freenom.com/en/index.html?lang=en) to get a free domain name.</br>
7275
To get the flag, you will have to send the same spoofing email that the previous step with the evil proxy url.</br>
7376

7477
## Step 5: Go Further
78+
7579
You must have seen that spoofing does not work on all mailboxes because of bad certificates used. </br>
7680
Indeed, some providers check if the certificates match the dns record of the email used. </br>
7781
If you want to go further, you can try to spoof an email with a good certificate to bypass restrictions.</br>
7882

7983
All bonus in this workshop will be rewarded in the PoC Security platform.</br>
8084
Don't hesitate to contact a staff member if you have any questions :) </br>
8185

82-
---
83-
This workshop has made with ❤️ by PoC Security
86+
<h2 align=center>
87+
Organization
88+
</h2>
89+
<br/>
90+
<p align='center'>
91+
<a href="https://www.linkedin.com/company/pocinnovation/mycompany/">
92+
<img src="https://img.shields.io/badge/LinkedIn-0077B5?style=for-the-badge&logo=linkedin&logoColor=white">
93+
</a>
94+
<a href="https://www.instagram.com/pocinnovation/">
95+
<img src="https://img.shields.io/badge/Instagram-E4405F?style=for-the-badge&logo=instagram&logoColor=white">
96+
</a>
97+
<a href="https://twitter.com/PoCInnovation">
98+
<img src="https://img.shields.io/badge/Twitter-1DA1F2?style=for-the-badge&logo=twitter&logoColor=white">
99+
</a>
100+
<a href="https://discord.com/invite/Yqq2ADGDS7">
101+
<img src="https://img.shields.io/badge/Discord-7289DA?style=for-the-badge&logo=discord&logoColor=white">
102+
</a>
103+
</p>
104+
<p align=center>
105+
<a href="https://www.poc-innovation.fr/">
106+
<img src="https://img.shields.io/badge/WebSite-1a2b6d?style=for-the-badge&logo=GitHub Sponsors&logoColor=white">
107+
</a>
108+
</p>
109+
110+
> 🚀 Don't hesitate to follow us on our different networks, and put a star 🌟 on `PoC's` repositories.

0 commit comments

Comments
 (0)