From 00b63b4bc3db8c15f55ca06cdf755f893352669a Mon Sep 17 00:00:00 2001
From: Hadi <112569860+anotherhadi@users.noreply.github.com>
Date: Sat, 23 Aug 2025 14:08:01 +0200
Subject: [PATCH] Add email spoofing section

Signed-off-by: Hadi <112569860+anotherhadi@users.noreply.github.com>
---
 README.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.md b/README.md
index e6bfcda..3c801e0 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,7 @@
 - [🧪 Usage](#-usage)
   - [Flags](#flags)
   - [Token](#token)
+  - [How does the email spoofing work?](#how-does-the-email-spoofing-work)
 - [💡 Examples](#-examples)
 - [🕵️‍♂️ Cover your tracks](#-cover-your-tracks)
 - [🤝 Contributing](#-contributing)
@@ -153,6 +154,18 @@ You can set the token in multiple ways:
 > **separate GitHub account** rather than your main account. This way, if
 > anything goes wrong, your primary account remains safe.
 
+### How does the email spoofing work?
+
+Here’s the process:
+
+1. Create a new repository.
+2. Make a commit using the **target's email** as the author.
+3. Push the commit to GitHub.
+4. Observe which GitHub account gets associated with that commit.
+
+All of these steps are handled **automatically by the tool**, so you just need
+to provide the target email.
+
 ## 💡 Examples
 
 ```bash