<?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 Sahil Shah on Medium]]></title>
        <description><![CDATA[Stories by Sahil Shah on Medium]]></description>
        <link>https://medium.com/@sahil3276?source=rss-1b56fa38db4d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tKaQXXcdVXulJw9nKWBJAw.jpeg</url>
            <title>Stories by Sahil Shah on Medium</title>
            <link>https://medium.com/@sahil3276?source=rss-1b56fa38db4d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:24:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sahil3276/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[How I Passed the HTB CWES with 100/100 (2026)]]></title>
            <link>https://sahil3276.medium.com/how-i-passed-the-htb-cwes-with-100-100-2026-bcac57518558?source=rss-1b56fa38db4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/bcac57518558</guid>
            <category><![CDATA[how-to-pass-htb-cwes]]></category>
            <category><![CDATA[cwe]]></category>
            <category><![CDATA[htb-cwes-medium-blog]]></category>
            <category><![CDATA[htb-cwes]]></category>
            <category><![CDATA[htb-cwes-2026-methodology]]></category>
            <dc:creator><![CDATA[Sahil Shah]]></dc:creator>
            <pubDate>Tue, 22 Sep 2026 20:14:27 GMT</pubDate>
            <atom:updated>2026-09-22T20:14:27.755Z</atom:updated>
            <content:encoded><![CDATA[<h4>CWES preparation, Exam experience, Machines &amp; Report Tips</h4><p>On March 27, I received the email I had been waiting for: I had passed the Hack The Box Certified Web Exploitation Specialist exam with a score of 100/100.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*db48ADuyTGvLj6LzYEA-7Q.png" /><figcaption><a href="https://www.credly.com/badges/c8132629-db41-4ff5-beba-c31699a96d3c/public_url">https://www.credly.com/badges/c8132629-db41-4ff5-beba-c31699a96d3c/public_url</a></figcaption></figure><p>I completed the Practical part of Exam in 2 Days and spent another 2 full days working on the report. Those four days included a lot of enumeration, a few frustrating rabbit holes, very little sleep, and more tea🍵 than I can count .</p><p>This was my first certification from Hack The Box. If I had to describe the entire experience in one sentence, I would say: <strong><em>it was freaking amazing!!</em></strong></p><p>This is not an exam walkthrough or a step-by-step guide. I am only sharing what the certification is, how I prepared, what my exam experience looked like, and what worked for me. I will not disclose any exam targets, payloads, vulnerabilities, or solutions.</p><h3>About the HTB CWES</h3><p>The Hack The Box Certified Web Exploitation Specialist, or HTB CWES, is an intermediate-level practical certification focused on web application penetration testing and bug bounty-style vulnerability discovery.</p><p>CWES was previously known as the Certified Bug Bounty Hunter (CBBH) certification. Hack The Box later renamed it and updated the associated learning path to better match roles such as Web Application Penetration Tester and Application Security Engineer. Learn more: <a href="https://academy.hackthebox.com/preview/certifications/htb-certified-web-exploitation-specialist">Here</a></p><p>The exam gives you <strong>7 continuous days </strong>(<em>including report writing :) </em>). Multiple web applications are hosted within the provided environment, and the connection can be made through HTB’s browser-based Pwnbox.</p><p>At the time of writing (2026), <strong>80/100 points were required to pass</strong>. Each application generally had two objectives: an <strong>initial flag </strong>after breaking the first major application barrier, and a <strong>server-level Final flag </strong>after achieving remote command execution or equivalent access. The second objective is often called the “root flag,” but <strong>operating-system privilege escalation is not required</strong>; the escalation happens at the web application level.</p><blockquote>Capturing enough flags is only one part of the exam. A professional and reproducible penetration testing report must also be submitted within the same seven-day window.</blockquote><p>For anyone familiar with OffSec certifications, CWES can loosely be placed in the same web-security space as OSWA, but CWES uses a seven-day exam format.</p><h3>A Little About Me</h3><p>CWES was my first HTB certification. Before starting it, I already had bug bounty experience and had completed my master’s degree in cybersecurity. That background definitely helped me recognize vulnerability patterns and move faster during the exam.</p><p>During my preparation, I collected publicly available information from YouTube, Reddit, blogs, and other candidates’ reviews. I used those sources to understand what the overall experience might look like, but the HTB Academy material remained my main resource.</p><p><strong>My honest view is simple:</strong> read and complete the <strong>HTB content</strong> properly. It <strong>contains everything required to understand the concepts covered by the certification.</strong></p><h3><strong>The Web Penetration Tester Path</strong></h3><p>Before the CWES exam can be attempted, the Web Penetration Tester Job Role Path must be completed. At the time of writing, it contains 20 modules and 279 sections.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dshT1fq1lTTgSO6dNr-yXA.png" /></figure><p>The modules are:</p><p>1. Web Requests<br>2. Introduction to Web Applications<br>3. Using Web Proxies<br>4. Information Gathering — Web Edition<br>5. Web Fuzzing<br>6. JavaScript Deobfuscation<br>7. Cross-Site Scripting (XSS)<br>8. SQL Injection Fundamentals<br>9. SQLMap Essentials<br>10. Command Injections<br>11. File Upload Attacks<br>12. Server-side Attacks<br>13. Login Brute Forcing<br>14. Broken Authentication<br>15. Web Attacks<br>16. File Inclusion<br>17. Attacking GraphQL<br>18. API Attacks<br>19. Attacking Common Applications<br>20. Bug Bounty Hunting Process</p><p>Official path:<br><a href="https://academy.hackthebox.com/path/preview/web-penetration-tester">https://academy.hackthebox.com/path/preview/web-penetration-tester</a></p><blockquote>The path is reading-heavy. Anyone who does not enjoy reading technical content will feel that very quickly. The material includes explanations, commands, examples, practical exercises, and a skills assessment at the end of each module.</blockquote><p>Still, the<strong> quality of the content is excellent</strong>. It explains not only how a vulnerability can be exploited, but also why it exists, how the application behaves, and how different techniques can be chained together to increase the impact.</p><blockquote>One module I particularly liked was <strong>Attacking Common Applications</strong>. It covers the process of testing technologies and platforms commonly seen during real assessments, including CMS platforms and applications such as Wordpress and Joomla (Tomcat, Jenkins &amp; more). The path does a good job of moving from basic web concepts to deeper exploitation and attack chaining.</blockquote><p><strong>Attacking Web Applications with Ffuf</strong> and <strong>Hacking WordPress — i Found </strong>found them useful, especially for reinforcing enumeration and CMS testing. Must to DO!</p><h3>How I Prepared</h3><p>My preparation started with completing the entire Academy path and its practical assessments. A few additional modules helped me personally:</p><blockquote><em>Web Fuzzing<br>Login Brute Forcing<br>Attacking Web Applications with Ffuf<br>SQL Injection Fundamentals<br>Hacking WordPress<br>File Inclusion</em></blockquote><p><strong>For note-taking, I used GitHub</strong> because I am comfortable with Markdown. I kept detailed notes containing useful commands, payloads, short explanations, and concepts that I found difficult to remember. I also noted which techniques could help with initial application access and which ones could lead to greater web-level impact or remote code execution.</p><p>I did not follow a complicated note-taking framework. The goal was simply to make the important material searchable during the exam. Notion, OneNote, Obsidian, CherryTree, or any similar tool can serve the same purpose.</p><p>I also collected a <strong>small practice list from community discussions</strong> and other researchers’ blogs. The HTB machines that appeared most often were:</p><blockquote>Union<br>Soccer<br>Delivery<br>Shoppy<br>BountyHunter<br>Cronos</blockquote><p><strong>HTB also has a CWES Preparation track.</strong> I did not complete that track personally, but it is another available source of web-focused practice.</p><p><strong>I also used the following VulNyx machines [Recommended!]</strong>:</p><blockquote>Swamp<br>Express<br>BOLA<br>JarJar<br>Gattaca<br>Future<br>Jerry<br>Lost</blockquote><blockquote>VulNyx machines:<br><a href="https://vulnyx.com/machines/">https://vulnyx.com/machines/</a></blockquote><p>These lists are simply the resources I used or collected during my preparation. They are not a mandatory checklist, and they do not reveal what appears in the exam.</p><h3>Exam Day</h3><p>I started the exam at around 5:00 a.m. on <strong>March 19</strong>.</p><p>The beginning was slower than I expected. The first two flags were the hardest for me, and for a while I was not sure whether I was approaching the applications correctly. Once I found the right direction, the pace changed completely.</p><p>By the end of the first day, I had captured <strong>five flags</strong> ;)</p><p>Tea🍵 deserves some credit here. I took several tea breaks throughout the day, and stepping away from the screen often helped me rethink what I had already seen. More than once, I returned to Burp Suite with a new idea after spending a few minutes away from the laptop.</p><p>On <strong>March 20</strong>, I continued with the remaining applications. Flag number nine was another difficult one for me. Looking back, the issue was not the vulnerability itself; it was finding the correct entry point and looking at the application differently.</p><p>At approximately 11:00 p.m. on March 20, I captured the final flag. The dashboard showed <strong>100/100!</strong></p><p>I just sat there for a moment looking at the score. Two days of almost continuous testing, and the technical part was finished.</p><p>For me, the <strong>exam difficulty was moderate.</strong> Not every vulnerability from the Academy path appeared, which would be impossible in one exam, but the main web exploitation concepts were well represented. My bug bounty experience and cybersecurity background clearly helped, so my completion time should be viewed only as my personal experience.</p><p>I slept for roughly four hours during those two days. That was not a clever strategy🥹; I was simply too focused on reaching the next flag. The tea kept me awake, but it could not replace sleep. :)</p><p>One thing became very clear during the exam: correct enumeration and attack chaining mattered more than trying random payloads. When I remained stuck on one idea for too long, changing the input point or reviewing the traffic usually gave me a better direction.</p><p><strong>I sent all relevant application traffic through Burp Suite and added the IP addresses and domains to the project scope</strong>. Having a complete HTTP history was extremely helpful whenever I needed to revisit an old request, compare responses, or look for something I had initially missed.</p><h3>The Report</h3><p>After achieving the Score, I spent March 21 and March 22 entirely on reporting.</p><p>I had read several blogs and Reddit discussions saying that <strong>HTB takes reporting seriously</strong>. I did not want to risk the result by submitting something incomplete or difficult to reproduce.</p><p>I used SysReptor and followed its ready-made CWES report template:<br><a href="https://docs.sysreptor.com/assets/reports/HTB-CWES-Report.pdf">https://docs.sysreptor.com/assets/reports/HTB-CWES-Report.pdf</a></p><p>(Simply Register there and start making your exam report there)</p><p>The template already contains the main sections required for the assessment, so it was easy to understand where to place the executive summary, scope, findings, technical details, remediation, and captured flags. That saved me a lot of time and kept the final report consistent.</p><p>For every finding, I included all the steps required to reproduce it. I added screenshots with clear borders around important details, figure captions, short explanations, and captions for command or shell output. I did not rely only on screenshots from Burp Suite; the relevant raw HTTP requests were included in code blocks, and I added cURL commands wherever they made the reproduction clearer.</p><p>I also included a clean proof-of-concept script in the report ZIP and referenced it from the appendix. The exact flags submitted during the exam were added as well, because resetting an application can generate new flag values.</p><p>My main focus was simple: <strong>a technical reviewer should be able to follow the report from beginning to end and reproduce every result without guessing what happened between two steps.</strong></p><p>I submitted the report on March 22.</p><p><strong>Five days later, on March 27, I received the result: passed with 100/100.</strong></p><h4><strong>What Worked for Me</strong></h4><p>Looking back, four things made the biggest difference in my attempt:</p><p>- Reading the HTB material properly instead of only collecting payloads!<br>- Keeping detailed, searchable notes with commands and key concepts<br>- Enumerating every application carefully and revisiting old traffic in Burp Suite<br>- Thinking about how vulnerabilities could be chained instead of treating each finding separately</p><p><strong>Seven days felt more than enough for my attempt</strong>. I completed the technical portion in two days and used another two days for reporting, so the rush and lack of sleep were completely unnecessary. That was simply how I approached the challenge at the time.</p><h3>Final Thoughts</h3><p>For me, the HTB CWES was absolutely worth it.</p><p>The Academy path is long, text-heavy, and sometimes exhausting, but the content is genuinely valuable. It covers web penetration testing in depth and constantly connects technical exploitation with methodology and reporting.</p><p>The perfect score was a great result, but the best part was seeing how the preparation came together during the exam. Small concepts from the modules, practice machines, notes, Burp history, and previous bug bounty experience all played a role.</p><p>This certification pushed my limits and made me more confident in approaching unknown web applications. That is what made the entire journey worth it.</p><p>I wish everyone taking this path success in their journey.</p><p>And yes — keep your Tea/Coffee ready :)</p><h4>Disclaimer</h4><p>This article reflects my personal experience and does not contain exam solutions or confidential target information. Certification formats and requirements may change, so the current instructions provided by Hack The Box remain the official source of truth!</p><blockquote>Get in touch with me here:</blockquote><p><a href="https://www.linkedin.com/in/sahilshah3276/"><strong>Linkedin</strong></a><strong> | </strong><a href="https://x.com/sahil3276"><strong>Twitter</strong></a><strong> | </strong><a href="https://github.com/sahil3276"><strong>Github</strong></a></p><p>#HTB #CWES #2026 #HTB-CWES #Methodology #Guide #Sahil3276</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bcac57518558" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS S3 Bucket Hacking 101: From Enumeration to Exploitation]]></title>
            <link>https://sahil3276.medium.com/aws-s3-bucket-hacking-101-from-enumeration-to-exploitation-e3e2a2948eba?source=rss-1b56fa38db4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3e2a2948eba</guid>
            <category><![CDATA[aws-hacking]]></category>
            <category><![CDATA[cloud-hacking]]></category>
            <category><![CDATA[s3-bucket]]></category>
            <category><![CDATA[reconnaissance]]></category>
            <category><![CDATA[aws-s3-bucket]]></category>
            <dc:creator><![CDATA[Sahil Shah]]></dc:creator>
            <pubDate>Sun, 20 Apr 2025 08:49:03 GMT</pubDate>
            <atom:updated>2025-04-20T08:56:11.675Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BJ16Gs9wHkzcEUjujTBjNA.jpeg" /></figure><h3><strong>Introduction:</strong></h3><p>Amazon S3 (Simple Storage Service) is a widely used cloud storage service offered by AWS. It allows users to store and retrieve any amount of data at any time. These storage units are called <strong>buckets</strong>, and they can hold files, folders, images, backups, and more.</p><p>However, if misconfigured, these buckets can become publicly accessible, exposing sensitive data to anyone on the internet. This makes <strong>S3 bucket enumeration and exploitation</strong> a valuable skill for ethical hackers, bug bounty hunters, and cloud security professionals.</p><p>In this blog, we’ll explore how to find exposed S3 buckets, tools used for enumeration, and both manual and automated ways to assess and exploit them.</p><h3>Example of S3 Bucket URLs</h3><ul><li>http://&lt;org-bucket&gt;.s3.amazonaws.com/</li><li>https://s3.amazonaws.com/&lt;org-bucket&gt;/files/</li></ul><p>Another way to identify an S3 bucket is by checking the response headers. A typical sign is:</p><pre>Server: AmazonS3<br>X-Amz-Id-*:<br>X-Amz-Bucket-Region:<br>X-Amz-Request-Id: </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l5KJxq5JOGlQlEk9PWeFPw.png" /></figure><h3><strong>How to Find Open S3 Buckets?</strong></h3><p>There are several techniques you can use during the reconnaissance phase to discover exposed or misconfigured S3 buckets. Below are some of the methods and tools I personally use during bucket enumeration:</p><ol><li><strong>S3 Enumeration Tools</strong></li></ol><p>Here is a list of Tools I Personally Use for S3 Bucket Enumeration</p><ul><li><a href="https://github.com/sa7mon/S3Scanner">S3Scanner</a></li><li><a href="https://github.com/koenrh/s3enum">s3enum</a></li><li><a href="https://github.com/gwen001/s3-buckets-finder">s3-buckets-finder</a></li><li><a href="https://github.com/nahamsec/lazys3">lazyS3</a></li><li><a href="https://github.com/jordanpotti/AWSBucketDump">AWSBucketDump</a> [Old]</li><li><a href="https://github.com/0xSearches/sandcastle">sandcastle</a> [ld]</li><li><a href="https://github.com/smiegles/mass3">mass3</a> [old]</li></ul><p><strong>2. Nuclei Templates</strong></p><ul><li><a href="https://github.com/projectdiscovery/nuclei-templates/blob/master/technologies/aws/amazon-ec2-detect.yaml">amazon-ec2-detect.yaml</a></li><li><a href="https://github.com/projectdiscovery/nuclei-templates/blob/master/technologies/aws/aws-bucket-service.yaml">aws-bucket-service.yaml</a></li></ul><p><strong>3. Burp Suite Extension</strong> — <em>Asset Discovery</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljDmdTvIkvb1f3xM5BEiIA.png" /></figure><p><strong>4. Recon Automation Tools</strong></p><p>The most effective ways to identify potential S3 buckets is through <strong>automated recon using subdomain enumeration tools</strong>. These tools help uncover subdomains of a target domain, which can then be probed to detect if any of them point to Amazon S3 services. some commonly used tools:</p><ul><li>assetfinder</li><li>subfinder</li><li>amass</li><li>chaos</li><li>hacktrails<br> ...and many more!</li></ul><p>Once you have the list of subdomains, you can pipe them into httpx or httpx-toolkit to detect S3 servers. For example:</p><pre>cat subdomains.txt | httpx -silent -webserver -threads 100 | grep -i AmazonS3</pre><p>Or a complete one-liner example:</p><pre>subfinder -d google.com -all -silent | httpx -silent -webserver -threads 100 | grep -i AmazonS3</pre><p><strong>5. Google Dorking</strong></p><ul><li>site:amazonaws.com inurl:”.s3.amazonaws.com/”</li><li>site:s3.amazonaws.com intitle:index.of.bucket</li><li>Inurl: s3.amazonaws.com/uploads/</li><li>Inurl: s3.amazonaws.com/backup/</li><li>Inurl: s3.amazonaws.com/mp3/</li><li>Inurl: s3.amazonaws.com/movie/</li><li>Inurl: s3.amazonaws.com/video/</li></ul><p>6. <strong>Using Online Services to Discover Open S3 Buckets</strong></p><p>One of the easiest ways to find open S3 buckets is by using online search platforms like <a href="https://buckets.grayhatwarfare.com/">GrayHatWarfare</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n3A9uPq6b48VcyhMNKfX2g.png" /></figure><p><strong>[1]How Secure Bucket look like:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/0*7f7MmuzSIKKjkTGe.png" /></figure><p><strong>[2] How open Bucket looks like:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1001/1*TaCpz_U_seaId5pEgwwvZg.png" /></figure><p><strong>[3] S3 Bucket Vulnerable to Takeover:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/830/0*C8WBXtJPlK9WXSyZ.png" /></figure><h3>Exploitation: Interacting with Open S3 Buckets</h3><p>Once you’ve discovered an open S3 bucket, you can attempt to <strong>read, upload, or download files</strong> using the AWS CLI. Here’s how to get started:</p><p><strong>Step 1: Create an AWS Account</strong></p><p>If you don’t already have one, sign up for a free AWS account here:<br> 🔗 <a href="https://aws.amazon.com/">https://aws.amazon.com</a></p><p><strong>Step 2: Install AWS CLI</strong></p><p>Download and install the AWS Command Line Interface from:<br> 🔗 <a href="https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html">https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html</a></p><p>Step 3: Configure AWS CLI</p><p>Open your terminal or command prompt and run:</p><pre>aws configure</pre><p>You’ll be prompted to enter:</p><ul><li>AWS Access Key ID</li><li>AWS Secret Access Key</li></ul><p>These credentials can be created in the <strong>AWS Management Console</strong> under <strong>IAM &gt; Users &gt; Security Credentials</strong>.</p><p><strong>Step 4: Interact with the S3 Bucket</strong></p><p>Once configured, you can now run the following AWS CLI commands:</p><p><strong>List contents of a bucket:</strong></p><ul><li>aws s3 ls s3://bucket-name</li></ul><p><strong>List contents without configuring credentials (fails if private):</strong></p><ul><li>aws s3 ls s3://bucket-name --no-sign-request</li></ul><p><strong>Download a file from the bucket:</strong></p><ul><li>aws s3 cp s3://bucket-name/file.png ./</li></ul><p><strong>Upload a file to the bucket:</strong></p><ul><li>aws s3 cp ./localfile.txt s3://bucket-name/poc.txt</li></ul><h3>S3 Bucket Takeover</h3><p>If you come across a bucket that returns an error like <strong>“The specified bucket does not exist”</strong>, it might be a candidate for <strong>S3 bucket takeover</strong> especially if it’s tied to an unclaimed subdomain.</p><p>You can refer to this video for a step-by-step explanation on how the takeover/Registration process works:<br> 🎥 <strong>YouTube</strong>: <a href="https://www.youtube.com/watch?v=-l83oqcaTHg">How to create S3 Bucket</a></p><p>For technical references and a full list of services vulnerable to subdomain takeovers, check out:<br> 📚 <strong>GitHub (EdOverflow)</strong>: <a href="https://github.com/EdOverflow/can-i-take-over-xyz">can-i-take-over-xyz</a></p><blockquote><em>📝 Note: As of the date of writing, S3 bucket takeover is still a valid attack vector in some scenarios involving misconfigured DNS.</em></blockquote><p>If you encounter any difficulties or problems, let me know in the comments.</p><p><em>Thanks for your patience. [ Hit some likes ;) ]</em></p><p>Get in touch with me here:</p><p><a href="https://www.linkedin.com/in/sahilshah3276/"><strong>Linkedin</strong></a><strong> | </strong><a href="https://x.com/sahil3276"><strong>Twitter</strong></a><strong> | </strong><a href="https://github.com/sahil3276"><strong>Github</strong></a></p><p>#BugBounty #EthicalHacking #S3BucketFinding #CyberSecurity #InfoSec #PenetrationTesting #HackerCommunity #BugHunting #AWS #CloudSecurity #AWSHacking #CloudPentesting #S3Enumeration<br> #OpenBuckets #CloudMisconfig #HackTheCloud #SecurityResearch<br> #BugBountyTips #RedTeamOps #CloudRecon #InfosecCommunity<br> #HackerLife #AWSRecon #PentestTips #DataExposure #CyberAwareness<br> #OSINT #CloudEnumeration #CloudHackers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3e2a2948eba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Intercepting HTTP Traffic for Thick-Client Penetration Testing]]></title>
            <link>https://sahil3276.medium.com/intercepting-http-traffic-for-thick-client-penetration-testing-25e06a96070e?source=rss-1b56fa38db4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/25e06a96070e</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[thick-client]]></category>
            <category><![CDATA[thick-client-security]]></category>
            <category><![CDATA[sahil3276]]></category>
            <category><![CDATA[traffic-intercept]]></category>
            <dc:creator><![CDATA[Sahil Shah]]></dc:creator>
            <pubDate>Thu, 20 Feb 2025 10:23:38 GMT</pubDate>
            <atom:updated>2025-02-20T17:31:38.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JULmbkVofPmbWdIgk6QRTg.jpeg" /></figure><p>Hello folks,<strong> </strong>I’m Sahil Shah, A Security Researcher passionate about <strong>Web, Mobile, and Thick client penetration testing</strong>.</p><p>In today’s blog, I’ll walk you through <strong>intercepting thick client HTTP traffic</strong> using <strong>Fiddler and Burp Suite with a dual proxy setup</strong>. I’ll keep it <strong>simple and beginner-friendly</strong>, so stay with me</p><p>let’s dive in! 🚀</p><p>First, you need to install the required tools for this setup.</p><p><strong>Install Fiddler : </strong>Click the link below and follow the installation instructions to complete the setup.</p><p><a href="https://www.telerik.com/download/fiddler">Download Fiddler Web Debugging Tool for Free by Telerik</a></p><p>After completing the installation, the initial interface will look like this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PLIEaxDKiSDn-nUMajvv-Q.png" /></figure><h3>Enable HTTPS Decryption in Fiddler</h3><p>Fiddler allows you to intercept and decrypt HTTPS traffic by installing its root certificate.</p><ul><li>Go to <strong>Tools → Options → HTTPS</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*qo-gTRkhHGO240rXvabvZQ.png" /></figure><ul><li>Check the following options:<br>✅ <strong>Capture HTTPS CONNECTs</strong><br>✅ <strong>Decrypt HTTPS Traffic</strong><br>✅ <strong>Ignore server certificate errors</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*iaYeeydm-rcgr3KMAQWEAA.png" /></figure><p>This will allow Fiddler to inspect encrypted traffic effectively.</p><h3>Trust the Fiddler Root Certificate</h3><ul><li>Click on <strong>“Actions”</strong> → <strong>“Trust Root Certificate”</strong>.</li><li>Follow the on-screen prompts to add Fiddler’s certificate to the trusted certificate store.</li></ul><p>This step ensures Fiddler can intercept and decrypt HTTPS traffic without security warnings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*YeRoOWqUUcR0B3JiXW0pSw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*qmYBD_7XmZzitVrQX06Vbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/511/1*w7aKREa-JulgYPiPjZLbkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/1*YeMJ-UaNrklMV2YMdtQeWA.png" /><figcaption>Root Certificate Installation Done.</figcaption></figure><h3>Configure Manual Proxy to Redirect Traffic to Burp Suite</h3><p>Fiddler allows you to <strong>redirect traffic to Burp Suite</strong> by setting up a manual proxy.</p><ul><li>Go to <strong>Tools → Options → Gateway</strong></li><li>Select <strong>“Manual Proxy Configuration”</strong></li><li>Set the <strong>Burp Suite listener proxy (default: 127.0.0.1:8080)</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/0*lTFeudwEZU50812g.png" /></figure><p>This setup routes traffic through Fiddler first, then forwards it to Burp Suite for deeper analysis.</p><blockquote>If you haven’t installed Burp Suite yet, you can download it from <a href="https://portswigger.net/burp/communitydownload">Here</a></blockquote><h3>Configure Burp Suite Proxy</h3><ul><li>Open <strong>Burp Suite</strong> and navigate to <strong>Proxy → Proxy Settings</strong></li><li>Ensure the <strong>proxy listener</strong> is <strong>active</strong> and set to 127.0.0.1:8080.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4cXdoWZRxRwjkD9ilPTAg.png" /></figure><h3>Configure Fiddler to Exempt System Traffic</h3><ul><li>Go back to <strong>Fiddler</strong> and click on <strong>“WinConfig”</strong>.</li><li>Select <strong>“Exempt None”</strong> to ensure only the intended application traffic is intercepted, avoiding unnecessary system traffic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*vAW2QIAyF1Ty63l8miUTbA.png" /></figure><p>Make sure <strong>“Exempt None”</strong> is selected. If not, select it and save the changes. Once done, you’re all set!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqHgCMM6UkUs6D7e-XwPyg.png" /></figure><p>Now, launch any thick client application and perform actions like <strong>login, signup, or any operation that generates HTTP traffic</strong>. If everything is set up correctly, you’re good to go!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jTdVwgxgjWks9hftT45vgg.png" /></figure><p>If you encounter any difficulties or problems, let me know in the comments.</p><blockquote>Thanks for your patience. [ Hit some likes :) ]</blockquote><p>Sahil Shah.</p><p>Get in touch with me here:</p><p><strong>Linkedin:</strong> <a href="https://www.linkedin.com/in/sahilshah3276/">https://www.linkedin.com/in/sahilshah3276/</a></p><p><strong>Twitter: </strong><a href="https://x.com/sahil3276">https://x.com/sahil3276</a></p><p><strong>Github:</strong> <a href="https://github.com/sahil3276">https://github.com/sahil3276</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25e06a96070e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CyberDefenders - PoisonedCredentials Blue Team Lab]]></title>
            <link>https://sahil3276.medium.com/cyberdefenders-poisonedcredentials-blue-team-lab-40a6dee29fcd?source=rss-1b56fa38db4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/40a6dee29fcd</guid>
            <category><![CDATA[cyberdefender]]></category>
            <category><![CDATA[investigation]]></category>
            <category><![CDATA[poisonedcredentials]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Sahil Shah]]></dc:creator>
            <pubDate>Thu, 19 Sep 2024 19:56:10 GMT</pubDate>
            <atom:updated>2024-09-19T19:56:10.164Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi, I’m Sahil Shah, In this walkthrough, I’ll be covering the <a href="https://cyberdefenders.org/blueteam-ctf-challenges/poisonedcredentials/"><strong>PoisonedCredentials Lab</strong></a>, a challenge designed to test your incident response and forensic investigation skills in a simulated network security incident.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*2ACnDQ776-tdiwDdDs87hw.png" /></figure><p>Let’s dive into the details of the investigation:</p><p><strong>Question 1:</strong></p><blockquote>In the context of the incident described in the scenario, the attacker initiated their actions by taking advantage of benign network traffic from legitimate machines. Can you identify the specific mistyped query made by the machine with the IP address 192.168.232.162?</blockquote><p>Answer: <strong>fileshaare</strong></p><figure><img alt="Wireshark" src="https://cdn-images-1.medium.com/max/1024/1*3jAjj2Q5ZnWGddzm2DGCTg.png" /><figcaption>Wireshark</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hN3Z-Q-P0pd25AZEf35TA.png" /><figcaption>NetworkMiner</figcaption></figure><p><strong>Question 2:</strong></p><blockquote>We are investigating a network security incident. For a thorough investigation, we need to determine the IP address of the rogue machine. What is the IP address of the machine acting as the rogue entity?</blockquote><p>Answer: <strong>192.168.232.215</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eYvCrPfc1kP3JLvxp565Xg.png" /><figcaption><em>As you can see there is an ip on the right acting as the rogue entity</em></figcaption></figure><p><strong>Question 3:</strong></p><blockquote>During our investigation, it’s crucial to identify all affected machines. What is the IP address of the second machine that received poisoned responses from the rogue machine?</blockquote><p>Answer: <strong>192.168.232.176</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YDpR6-xoTjK69LoOs80yDg.png" /><figcaption>Wireshark -&gt; Statistics -&gt; Connections -&gt; IPv411</figcaption></figure><p><strong>Question 4:</strong></p><blockquote>We suspect that user accounts may have been compromised. To assess this, we must determine the username associated with the compromised account. What is the username of the account that the attacker compromised?</blockquote><p>Answer: <strong>janesmith</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5U4CrgM3gMmusA84U6nNdA.png" /><figcaption>You can use this filter also: <strong>smb2</strong></figcaption></figure><p><strong>Question 5:</strong></p><blockquote>As part of our investigation, we aim to understand the extent of the attacker’s activities. What is the hostname of the machine that the attacker accessed via SMB?</blockquote><p>Answer: <strong>AccountingPC</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9RQWxbXVNCc-ZuI23wAy-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iILHj6oEu3dGCpvicQgJtQ.png" /></figure><p>Thanks for your patience.</p><p>Sahil Shah.</p><p>Get in touch with me here: <a href="https://www.linkedin.com/in/sahilshah3276/"><strong>LinkedIn </strong></a><strong>| </strong><a href="https://github.com/sahil3276"><strong>Github</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40a6dee29fcd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Full Potential of Amass [Part-2]]]></title>
            <link>https://sahil3276.medium.com/unlocking-the-full-potential-of-amass-part-2-292b7fab6618?source=rss-1b56fa38db4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/292b7fab6618</guid>
            <category><![CDATA[configuration]]></category>
            <category><![CDATA[massa]]></category>
            <category><![CDATA[recon]]></category>
            <category><![CDATA[subdomains-enumeration]]></category>
            <category><![CDATA[reconnaissance]]></category>
            <dc:creator><![CDATA[Sahil Shah]]></dc:creator>
            <pubDate>Mon, 27 May 2024 20:10:27 GMT</pubDate>
            <atom:updated>2024-05-27T20:10:27.041Z</atom:updated>
            <content:encoded><![CDATA[<p>This is the second article in the series about Amass Configuration.</p><p>If you haven’t checked out <a href="https://sahil3276.medium.com/unlocking-the-full-potential-of-amass-part-1-0521ddbee8cc">Part-1</a> yet, please do so and follow the steps outlined.</p><p>As I have mentioned, I will provide a list of domains that offer free API keys. You will need to implement these in your datasources.yaml file.</p><p><strong>First let us Discuss Why are these API keys important, and what are these domains?</strong></p><p>Let’s consider a scenario: Suppose you have a target domain, for example, target.com, and you need to gather as many subdomains as possible. You might have tools like Subfinder and Assetfinder, which have limited functionalities. However, There are other websites like VirusTotal, URLScan, and SecurityTrails that also provide subdomain information for particular domains.</p><p>In this case, if the user wants to find more valuable subdomains, they would typically need to manually visit these websites and collect the data. This is where Amass comes into play. Amass offers a functionality where it uses API keys from authenticated users to gather as much information as possible from multiple domains. This means the user doesn’t need to manually check all the domains and gather subdomains; Amass will handle all the work automatically. I hope this clarifies the process.</p><blockquote><em>Below, I have provided a list of domains along with their web addresses. Simply go to the respective websites, sign up with your account, and obtain your API key. Add the key to the file, and you will be good to go.</em></blockquote><pre>asnlookup          https://asnlookup.com/<br>virustotal         https://virustotal.com/<br>urlscan.io         https://urlscan.io/<br>bevigil            https://bevigil.com/<br>bigdatacloud       https://www.bigdatacloud.com<br>BinaryEdge         https://app.binaryedge.io             <br>BuiltWith          https://api.builtwith.com                                  <br>CENSYS             https://censys.com/<br>Chaos              https://cloud.projectdiscovery.io/ <br>CertCentral        https://www.digicert.com/        <br>FullHunt           https://fullhunt.io/     <br>github             https://github.com/             <br>intelx             https://intelx.io/              <br>IPdata             https://dashboard.ipdata.co/                 <br>ipinfo             https://ipinfo.io/                            <br>LeakIX             https://leakix.net/                      <br>Netlas             https://app.netlas.io/                       <br>networksdb         https://networksdb.io/                  <br>psbdmp.ws          https://thecatapi.com/                <br>PublicWWW          https://publicwww.com/                          <br>shodan             https://shodan.io/                                 <br>alienvault         https://alienvault.com/<br>BufferOver         https://bufferover.run/   <br><br>#Domains that require business email addresses, But are Highly Recommended..!<br>Securitytrails     https://securitytrails.com/  [Bussiness-Mail Required] [Preffered]   <br>Hunter             https://hunter.io/     [Bussiness-Mail Required] [Preffered]         <br>WhoisXMLAPI        https://whoisxmlapi.com/   [Bussiness-Mail Required] [Preffered]  </pre><p><em>I’m sharing this straight from my secure and private notes, so I deserve a</em><strong><em> follow and a clap </em></strong><em>from you! :) jk</em></p><p>Anyways, You just need to visit these sites and sign up one by one. I recommend you <strong>Take NOTES</strong> of this as it will help you in the future as well. After obtaining the API keys and pasting them into your notes, just open the datasources.yaml file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NHsqaZ2tenKp9134HJmR7A.png" /><figcaption>Mousepad as an Text editor.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9n8B0CL3W9GxNPOejxd9Q.png" /><figcaption>datasources.yaml file with API keys</figcaption></figure><p>As you can see, I have pasted all the API keys into my datasources.yaml file, Save It.! You should do the same process, and you&#39;ll be good to go :)</p><p>Now run the following command to check whether Amass is configured successfully or not.</p><pre>amass enum -list</pre><p>Cross-check the result with the datasources.yaml file to ensure they match.</p><p>If you find the same result as me, Congratulations!</p><p>Your Amass has been configured successfully. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCwh0p_2gvVMUadTCseXDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*tyVobAIK3G2SIUiNHyH_Pw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A348EwKQBTccCWfmXeQS0A.png" /></figure><p>The domains that don’t contain asterisks (*) mostly require a premium subscription to use, but you don’t need to worry about it.</p><p>Through this configuration,<strong> </strong>I was able to get<strong> over 35,000 subdomains</strong> of Google within 8 hours. It’s an evident that this tool is both robust and efficient.</p><p><strong>How to RUN?</strong></p><p>I know You guys are Pro.. but still im sharing steps :)</p><pre>amass enum -d target.com | tee output.txt</pre><p>it will produce ugly output ik :(</p><p>Now run this.</p><pre>cat output.txt | awk &#39;{print $1}&#39; | grep &#39;target_name&#39; | tee final.txt</pre><p>You will get the Absolute domain names which you are looking for.</p><p><strong>Do let me know in the comments if you want to know my recon methodology :)</strong></p><p>Thanks for your patience.</p><p>Sahil Shah.</p><p>Get in touch with me here:</p><p><strong>Linkedin:</strong> <a href="https://www.linkedin.com/in/sahilshah3276/">https://www.linkedin.com/in/sahilshah3276/</a></p><p><strong>Twitter: </strong><a href="https://x.com/sahil3276">https://x.com/sahil3276</a></p><p><strong>Github:</strong> <a href="https://github.com/sahil3276">https://github.com/sahil3276</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=292b7fab6618" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unlocking the Full Potential of Amass [Part-1]]]></title>
            <link>https://sahil3276.medium.com/unlocking-the-full-potential-of-amass-part-1-0521ddbee8cc?source=rss-1b56fa38db4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/0521ddbee8cc</guid>
            <category><![CDATA[massa]]></category>
            <category><![CDATA[configuration]]></category>
            <category><![CDATA[subdomain-enumeration]]></category>
            <category><![CDATA[recon]]></category>
            <category><![CDATA[reconnaissance]]></category>
            <dc:creator><![CDATA[Sahil Shah]]></dc:creator>
            <pubDate>Sun, 26 May 2024 20:26:41 GMT</pubDate>
            <atom:updated>2024-05-26T20:32:55.929Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>A Comprehensive Guide for Proper Configuration of Amass 4.2.0</strong></p><p>Hello Hackers, In this Artical I am gonna walk you through the process of configuring Amass for optimal performance. Discover how to fine-tune settings &amp; leverage advanced techniques to <strong>expand its capabilities beyond default configurations</strong>. Whether you’re a cybersecurity enthusiast or a seasoned professional, My step-by-step instructions will empower you to maximize your reconnaissance efforts with Amass. so be with me, lets Go.!</p><p><strong>What is Amass?</strong></p><p>Amass is an open-source reconnaissance tool used in cybersecurity. It’s designed to help discover and map network infrastructure, finding domains, subdomains, and other related data to aid in security assessments and investigations.</p><p>Transitioning from the older config.ini to the newer config.yaml and datasources.yaml in Amass can be daunting. In this article, I’ll guide you through the process, providing clear instructions to configure Amass effectively and unlock its full potential for reconnaissance purposes.</p><p>I’ll strive to keep this walkthrough concise and easily understandable.!</p><p>Steps:</p><h4>1. Installing amass:</h4><p>I’m using Kali Linux OS, so it’s easy to install:</p><pre>sudo apt update &amp;&amp; sudo apt install amass</pre><h4>2. Configuration</h4><p>Open Your Terminal And Follow the steps.</p><p>2.1 Navigate to the root configuration directory:</p><pre>cd /root/.config</pre><p>Create a new directory named amass:</p><pre>mkdir amass #Remove If it&#39;s Already Created</pre><p>Navigate to the newly created amass directory</p><pre>cd amass</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*StGUTn17A-OYR-IS" /></figure><p><strong>2.2 Config.yaml Installation</strong></p><p>Now we have to download the <strong>config.yaml</strong> file. Which is very important for us to run Amass flawlessly,, I’m using the <strong>wget</strong> command. This command fetches the file from a specified URL and saves it to your current directory.</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/config.yaml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4Pcu5O3rQoo-1VDQ" /><figcaption>Path: /root/.config/amass/config.yaml</figcaption></figure><p>When you open the<strong> config.yaml </strong>file, you’ll notice that downloading certain wordlists and resolvers is necessary for Amass to run smoothly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kFo7U25SqHFr9Sn1" /><figcaption>config.yaml requires certain wordlists</figcaption></figure><p>Don’t worry about it. Here are the commands you need to paste into your terminal, and you’re good to go.</p><h4><strong>3. Wordlists Installation</strong></h4><p><strong>3.1 resolvers.txt Install</strong></p><p>Create a new directory named examples within the /root/.config directory</p><pre>mkdir /root/.config/examples</pre><p>Change the current working directory to the newly created examples directory</p><pre>cd /root/.config/examples</pre><p>Download the resolvers.txt file from the specified URL</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/resolvers.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Aa1ljbSMn6lnD7hQ" /><figcaption>Path: /root/.config/examples/resolvers.txt</figcaption></figure><p><strong>3.2 deepmagic.com_top50kprefixes.txt Install</strong></p><p>Create a new directory named wordlists within the /root/.config/amass directory</p><pre>mkdir /root/.config/amass/wordlists</pre><p>Change the current working directory to the newly created wordlists directory</p><pre>cd /root/.config/amass/wordlists</pre><p>Download the deepmagic.com_top50kprefixes.txt file from the specified URL</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/deepmagic.com_top50kprefixes.txt </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*d3hNHEVZm-iJaoaZ" /><figcaption>Path: /root/.config/amass/wordlists/deepmagic.com_top50kprefixes.txt</figcaption></figure><p><strong>3.3 deepmagic.com_top500prefixes.txt Install</strong></p><p>Download the deepmagic.com_top500prefixes.txt file from the specified URL</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/deepmagic.com_top500prefixes.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5CVYeOU9EDMZZzoj" /><figcaption>Path: /root/.config/amass/wordlists/deepmagic.com_top500prefixes.txt</figcaption></figure><p><strong>3.4 subdomains-top1mil-5000.txt Install</strong></p><p>Download the subdomains-top1mil-5000.txt file from the specified URL</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/subdomains-top1mil-5000.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pZwyf2WhDEMPfZ8M" /><figcaption>Path: /root/.config/amass/wordlists/subdomains-top1mil-5000.txt</figcaption></figure><p><strong>3.4 subdomains-top1mil-110000.txt Install</strong></p><p>Download the subdomains-top1mil-110000.txt file from the specified URL</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/subdomains-top1mil-110000.txt</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qzjD5DqPeQ_2n8xG" /><figcaption>Path: /root/.config/amass/wordlists/subdomains-top1mil-110000.txt</figcaption></figure><p>So now we Have reached the 1st stage of Configuring the amass,our <strong>config.yaml </strong>file is all set. Now, let’s configure the <strong>datasources.yaml</strong> file</p><h4>4. datasources.yaml Installation</h4><p>To unleash Amass’s full potential, we need a datasources.yaml file, which requires API keys for peak performance. I’ll guide you through obtaining the necessary API keys from various platforms to ensure seamless and effective operation. But first, let’s install the datasources.yaml file!</p><p>So here i’m in amass directory:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/668/0*WX7bp2qr7NhtV7ah" /><figcaption>Path: /root/.config/amass</figcaption></figure><p>This is the location where we’ve set up our config.yaml file. Now,<strong> download</strong> the <strong>datasources.yaml </strong>file using the command below:</p><p>Download the datasources.yaml file from the specified URL</p><pre>wget https://raw.githubusercontent.com/sahil3276/Amass_Config/main/datasources.yaml</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sYL1X9RHUd8omOIV" /></figure><p>Now that the datasources.yaml file is installed, let’s take a look. We need to provide API keys for different platforms. You’ll need to visit each platform, sign up, and obtain your own API keys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/0*fNthGSr7OZ7QG_01" /></figure><p>I have compiled a list of websites that provide API keys to users upon signing up. In Part-2, I’ll share the list of domains that offer FREE API keys. You just need to sign up there and obtain your own API key.</p><p>If you encounter any difficulties or problems, let me know in the comments.</p><p>See You Soon In Part-2</p><p>Thanks for your patience.</p><p>Sahil Shah.</p><p>Get in touch with me here:</p><p><strong>Linkedin:</strong> <a href="https://www.linkedin.com/in/sahilshah3276/">https://www.linkedin.com/in/sahilshah3276/</a></p><p><strong>Twitter: </strong><a href="https://x.com/sahil3276">https://x.com/sahil3276</a></p><p><strong>Github:</strong> <a href="https://github.com/sahil3276">https://github.com/sahil3276</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0521ddbee8cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>