From b996699820668cf5e21c59f2fdeef1dab730f5e3 Mon Sep 17 00:00:00 2001 From: mcoder Date: Fri, 17 Apr 2026 20:52:15 +0330 Subject: [PATCH] Add --- resources/views/hacker/webrtc.blade.php | 166 +++++++++++++++++++ resources/views/user/lab-directory.blade.php | 23 ++- routes/web.php | 5 + 3 files changed, 187 insertions(+), 7 deletions(-) create mode 100644 resources/views/hacker/webrtc.blade.php diff --git a/resources/views/hacker/webrtc.blade.php b/resources/views/hacker/webrtc.blade.php new file mode 100644 index 0000000..b596d22 --- /dev/null +++ b/resources/views/hacker/webrtc.blade.php @@ -0,0 +1,166 @@ + + + + + + WebRTC IP Leak Lab + + + + + +
+
+
+
+

WebRTC IP Leak Test

+

Zero-Click Information Disclosure

+
+
+ Scanning +
+
+
+ +
+

+ This page automatically executes a WebRTC connection request upon loading. WebRTC relies on STUN/TURN servers to establish peer-to-peer connections. During this process, the browser gathers all available network interfaces (ICE candidates) and exposes them to Javascript, often leaking the user's real public and local IP addresses—even behind proxies or split-tunnel VPNs. +

+ +

Discovered IP Addresses:

+ +
+
    + +
+ +
+
+
+ + +
+

+ + Developer & Security Note +

+
+

+ Local IP Obfuscation: Modern browsers (Chrome, Safari, Firefox) have implemented security measures to obfuscate local IP addresses using mDNS (Multicast DNS) by default (e.g., xxx.local). This prevents trivial local network scanning. +

+

+ Public IP Leaks: However, public IP addresses often still leak, especially when users rely on proxy extensions or split-tunnel VPNs, because WebRTC operates outside the standard HTTP flow and communicates directly via UDP. +

+

+ 🛡️ Zero Trust & Remote Browser Isolation (RBI): +

+

+ In an enterprise environment using a Zero Trust (RBI) browser, the WebRTC execution happens completely within an isolated cloud container. The STUN server only sees the cloud container's IP address, ensuring the real user's device IP is never exposed to the malicious website. +

+
+
+
+ + + + + + + 🏠 Back to Lab Directory + + + + \ No newline at end of file diff --git a/resources/views/user/lab-directory.blade.php b/resources/views/user/lab-directory.blade.php index fc35afd..fc74cc2 100644 --- a/resources/views/user/lab-directory.blade.php +++ b/resources/views/user/lab-directory.blade.php @@ -33,7 +33,7 @@

CSRF Attack

Demonstrate a classic Cross-Site Request Forgery attack using a hidden form.

- Launch Lab + Launch Lab
@@ -42,7 +42,7 @@

Session Stealer Logs

View the C2 server logs to see if any cookies or data have been exfiltrated.

- Launch Lab + Launch Lab
@@ -51,7 +51,7 @@

MitB Simulation

Simulate a Man-in-the-Browser attack by injecting JS into the login page via DevTools.

- Launch Lab + Launch Lab
@@ -60,7 +60,7 @@

Clickjacking

Bypass SameSite=Lax cookie protection using a compromised but same-site subdomain.

- Launch Lab + Launch Lab
@@ -69,7 +69,7 @@

Drive-by Download

Test how browsers handle automatic downloads initiated from a cross-origin iframe.

- Launch Lab + Launch Lab
@@ -78,7 +78,7 @@

Clipboard Data Leak

Explore browser permissions and user gestures required for clipboard access.

- Launch Lab + Launch Lab
@@ -96,7 +96,16 @@

CORS & Opaque Responses

Test how browsers block cross-origin data reads and handle 'no-cors' requests.

- Launch Lab + Launch Lab +
+ + + +
+
+

WebRTC IP Leak

+

Discover real IP addresses bypassing standard proxies via WebRTC STUN negotiation.

+ Launch Lab
diff --git a/routes/web.php b/routes/web.php index 2df0b9a..dcee013 100644 --- a/routes/web.php +++ b/routes/web.php @@ -64,6 +64,11 @@ return view('hacker.cors'); })->name('hacker.cors'); + // WebRTC IP Leak Exploit Page + Route::get('/webrtc-leak', function () { + return view('hacker.webrtc'); + })->name('hacker.webrtc'); + }); /*