<?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 Chirangi Dodiya on Medium]]></title>
        <description><![CDATA[Stories by Chirangi Dodiya on Medium]]></description>
        <link>https://medium.com/@chirangidodiya?source=rss-f1538904b072------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XXMXzj1JD4FDV_0S6Vpv4Q.jpeg</url>
            <title>Stories by Chirangi Dodiya on Medium</title>
            <link>https://medium.com/@chirangidodiya?source=rss-f1538904b072------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 12:37:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chirangidodiya/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[Unmasking a Fake Instagram Account Using OSINT A Real Investigation Case Study]]></title>
            <link>https://medium.com/@chirangidodiya/unmasking-a-fake-instagram-account-using-osint-a-real-investigation-case-study-408e1ed07adf?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/408e1ed07adf</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Tue, 30 Jun 2026 15:49:42 GMT</pubDate>
            <atom:updated>2026-06-30T15:49:42.790Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/49f68f75c58">Amish Patel</a> <a href="https://medium.com/u/87ba6554136e">Rey Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*pn-_QUWQekrQx4kxDlSiaQ.png" /></figure><p>In today’s digital world, fake identities on social media are more common than ever. But with the right approach and tools, it’s possible to uncover the truth behind them. This is a real case study of how I used OSINT (Open Source Intelligence) techniques to identify and expose a fake Instagram account.</p><p><strong>The Suspicion</strong></p><p>I came across a Female Instagram account that immediately raised doubts. The profile seemed inconsistent, and something about the identity didn’t feel authentic. Instead of ignoring it, I decided to investigate further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*j1smDJ3oUfZgYdJSrGP_XQ.png" /></figure><p><strong>Step 1: Reverse Image Search</strong></p><p>I began with the most obvious clue, the profile picture (DP). I uploaded the image to Google Image Search to check if it existed elsewhere online. This is often the fastest way to detect stolen or reused images. While this step gave me a starting point, it didn’t directly reveal the source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*qwiCF4Q3K-9jLqobRNH2zA.png" /></figure><p><strong>Step 2: Visual Analysis of Clothing</strong></p><p>Since the face search didn’t lead to clear results, I shifted focus to a different detail , the outfit in the image. I carefully analyzed the dress , its lace pattern, style, and overall aesthetic. The goal was to identify whether it belonged to a known fashion brand or was listed on any e-commerce platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*YCYOsEMV_-O-lKTLNHYjWg.png" /></figure><p><strong>Step 3: Expanding OSINT Techniques</strong></p><p>To dig deeper, I applied additional OSINT methods:</p><ul><li><strong>Search dorking</strong> to uncover indexed traces of the image</li><li><strong>Yandex Image Search</strong>, known for strong visual matching</li></ul><p>However, both approaches failed to produce useful results in this case.</p><p><strong>Step 4: Leveraging E-commerce Image Search</strong></p><p>At this point, I made a strategic shift. The outfit looked like something that would be sold online, so I used Myntra’s visual search feature. This turned out to be the breakthrough. By uploading the same image, I found a <strong>similar dress listing</strong>, which led me to a <strong>public Instagram profile</strong> connected to similar fashion content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*ZFbP8waM3yUnimJ4ZQS8TA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*8L0LF22lekyRlBn8fSO_rg.png" /></figure><p><strong>Step 5: Connecting the Dots</strong></p><p>I explored the Instagram account and carefully reviewed its posts. That’s when I noticed it , the same or highly similar images being used. This confirmed my suspicion: The Female account was<strong> using someone else’s photos without permission.</strong></p><p><strong>Real Instagram Account :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*x8F7bsMhAkHBu-ppQSrSfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*FKxD6awbgIblabKjJy79HQ.png" /></figure><p><strong>Fake Instagram Account :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*_7v0tsJ33h4_IoOcXnExGQ.png" /></figure><p><strong>Conclusion: Identifying the Truth</strong></p><p>By combining multiple OSINT techniques ,reverse image search, visual analysis, platform-based search, and profile comparison , I was able to:</p><ul><li>Trace the original source of the images</li><li>Verify that the account was fake</li><li>Expose the misuse of someone else’s identity</li></ul><p><strong>Key Takeaways</strong></p><ul><li>Always question inconsistencies in online identities</li><li>Reverse image search is powerful , but not always enough</li><li>Small details (like clothing) can unlock big leads</li><li>E-commerce platforms can be unexpected but valuable OSINT tools</li><li>Persistence and thinking differently are key in investigations</li></ul><p>Final Thought OSINT is not just about tools , it’s about observation, creativity, and connecting small clues. Even when standard methods fail, a different perspective can lead to the breakthrough.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=408e1ed07adf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uber Burned Through Its AI Budget in Four Months. Most Companies Are Headed the Same Way]]></title>
            <link>https://medium.com/@chirangidodiya/uber-burned-through-its-ai-budget-in-four-months-most-companies-are-headed-the-same-way-4ed655495f03?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ed655495f03</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 19:10:53 GMT</pubDate>
            <atom:updated>2026-06-08T19:10:53.267Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JmRNtvoqgL-PztaC0nC3Lw.png" /></figure><p><strong>The AI Gold Rush Has a Cost Problem</strong></p><p>For the past two years, companies have been racing to adopt AI.Executives promised faster software development, smarter operations, and unprecedented productivity gains. Developers embraced AI coding assistants. Marketing teams generated content at scale. Legal departments automated research. Everyone wanted a piece of the AI revolution.</p><p>Then reality arrived.</p><p>Uber reportedly burned through its entire 2026 AI budget in just a few months, forcing executives to ask an uncomfortable question:</p><p><strong>Are we actually getting enough value from all this AI usage?</strong></p><p>It’s a question many organizations are beginning to ask.</p><p>Because while AI capabilities continue to improve, the bill is growing even faster.</p><p>And unlike traditional software subscriptions, AI doesn’t charge by the seat.</p><p>It charges by intelligence consumed.</p><p><strong>The Productivity Paradox</strong></p><p>When companies first rolled out AI tools, the logic seemed simple.</p><p>Give employees access to powerful models and productivity will increase.</p><p>And in many cases, it did.</p><p>Developers generated code faster.</p><p>Analysts processed information more quickly.</p><p>Writers produced content in minutes instead of hours.</p><p>The problem is that productivity gains are easy to celebrate but difficult to measure.</p><p>Costs, however, are very easy to measure.</p><p>Every prompt.</p><p>Every code generation.</p><p>Every AI-powered search.</p><p>Every autonomous agent.</p><p>They all consume tokens.</p><p>And tokens cost money.</p><p>Lots of it.</p><p>Many organizations now find themselves in a strange situation where AI adoption is growing exponentially while their ability to measure return on investment remains uncertain.</p><p><strong>The Hidden Psychology Behind AI Overspending</strong></p><p>The Uber story isn’t really about Uber it’s about human behavior. Give a software developer access to the most powerful AI model available, and they’ll naturally use it for everything: coding, code reviews, documentation, brainstorming, debugging, and architecture design. Why wouldn’t they? When management says, “Use AI to become more productive,” most employees interpret it as, “Use the best AI available as much as possible.” Developers are wired to optimize; give them faster hardware and they’ll run bigger workloads, give them powerful AI and they’ll throw more problems at it. The behavior is completely rational. The budgeting often isn’t.</p><p><strong>The Rise of AI Tokenomics</strong></p><p>A new concept is becoming increasingly important in enterprise technology:</p><p><strong>AI Tokenomics</strong>. Much like cloud computing introduced consumption-based infrastructure costs, AI is introducing consumption-based intelligence costs. The more intelligence you consume, the more you pay. Unlike traditional software licenses, AI expenses are highly variable and difficult to predict. One engineer using advanced reasoning models all day can cost significantly more than another using lightweight models for routine tasks. Scale that across thousands of employees, and suddenly AI spending starts looking less like software costs and more like a utility bill.</p><p><strong>AI Is Becoming the New Electricity</strong></p><p>OpenAI CEO Sam Altman recently compared AI to utilities like electricity and water, and the comparison is surprisingly accurate. Nobody thinks about how many watts they consume when switching on a light, just as employees rarely think about how many tokens they use when interacting with AI. Businesses, however, do care — because someone ultimately has to pay the bill. The challenge isn’t that AI is inherently expensive; it’s that organizations are only beginning to understand what normal AI consumption looks like and how to manage it effectively.</p><p><strong>The Metric Nobody Is Tracking</strong></p><p>Many companies closely monitor AI adoption metrics such as user counts, prompt volumes, and monthly token consumption. However, very few track the metric that truly matters: <strong>business value created per token spent</strong>. Spending millions on AI isn’t a problem if it generates significantly greater business value. The real objective shouldn’t be minimizing token usage — it should be maximizing outcomes. Unfortunately, measuring business impact is far more difficult than measuring costs, which is why many organizations are still struggling to justify their growing AI investments.</p><p><strong>Why AI Leaders and CFOs See Different Realities</strong></p><p>There’s a growing divide within organizations when it comes to AI adoption. Technology leaders view AI as a strategic investment that accelerates development, improves efficiency, and helps teams deliver products faster, while finance leaders increasingly see it as a rapidly expanding expense that grows with every prompt, token, and AI-powered workflow. Both perspectives are valid the technology team sees faster innovation and improved productivity, while the finance team sees budgets swelling month after month with no clear ceiling in sight. The real challenge lies in proving that the productivity gains and business outcomes generated by AI are substantial enough to justify the rising costs. Until organizations develop reliable ways to measure AI’s return on investment and connect AI spending directly to business value, the tension between innovation and cost control will continue to grow.</p><p><strong>The Third Phase of AI: Optimization</strong></p><p>The first phase of enterprise AI was experimentation. The second was widespread adoption. Now, the third phase is optimization.</p><p>Companies are realizing that unlimited AI access without governance creates inefficiencies. Not every task needs the most powerful model, not every problem requires agentic reasoning, and not every workflow benefits from maximum compute power.</p><p>The organizations that succeed won’t be the ones using the most AI — they’ll be the ones using it smartest: choosing the right model, for the right task, at the right cost.</p><p><strong>The Bigger Lesson from Uber</strong></p><p>Uber’s reported AI budget overrun is not evidence that AI has failed.</p><p>It’s evidence that AI has matured.</p><p>Every transformative technology eventually reaches a moment where organizations stop asking:</p><p><em>“What can it do?”</em></p><p>And start asking:</p><p><em>“What is it worth?”</em></p><p>Cloud computing went through this phase.</p><p>Big data went through this phase.</p><p>Now AI is entering the same stage.</p><p>The winners won’t be the companies consuming the most tokens.</p><p>They’ll be the companies creating the most value from every token consumed.</p><p>Because in the end, intelligence may become a utility.</p><p>But like every utility, efficiency matters.</p><p>And the companies that learn that lesson first will gain the biggest advantage.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ed655495f03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Generic University , One API. Multiple Bugs. Full Compromise]]></title>
            <link>https://medium.com/@chirangidodiya/generic-university-one-api-multiple-bugs-full-compromise-4079ab8b3911?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/4079ab8b3911</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Thu, 26 Mar 2026 21:18:39 GMT</pubDate>
            <atom:updated>2026-03-26T21:18:39.932Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/49f68f75c58">Amish Patel</a> <a href="https://medium.com/u/87ba6554136e">Rey Patel</a></p><p><strong>Lab Setup</strong></p><p>Special thanks to:</p><ul><li><a href="https://medium.com/u/cebabe10eb46">Katie Paxton-Fear</a> (for the vulnerable app)</li><li><a href="https://medium.com/u/d562bca4d3cd">Nishith K</a><strong> (@busk3r)</strong> (for Docker setup on LinkedIn)</li></ul><p>Before starting the exploitation, we first need to set up the vulnerable application locally.</p><p><strong>Docker(Windows)</strong></p><p><strong>Step 1 : </strong>Make sure <strong>Docker Desktop</strong> is installed on your system.<br>Also ensure it is running with <strong>administrator privileges</strong>.</p><p><strong>Step 2 :</strong> <strong>Pull the Lab Image</strong></p><p>Open <strong>Command Prompt (Run as Administrator)</strong> and execute:</p><pre>docker pull busk3r/genericuniversity:latest</pre><p>This dwnloads the vulnerable <strong>Generic University</strong> application.</p><p><strong>Step 3 — Run the Container</strong></p><p>Now start the lab environment using:</p><pre>docker run --name genericuniversity -itd --rm -p 80:8000 busk3r/genericuniversity &amp;&amp; docker exec genericuniversity service mysql start &amp;&amp; docker exec genericuniversity mysql -u root -p -e &quot;ALTER USER &#39;root&#39;@&#39;localhost&#39; IDENTIFIED BY &#39;password&#39;;&quot;</pre><p>This command:</p><ul><li>Runs the container</li><li>Starts the MySQL service</li><li>Sets the database password</li></ul><p><strong>Step 4 — Start the Application</strong></p><pre>docker exec genericuniversity php /root/Generic-University/artisan serve --host 0.0.0.0</pre><p>This launches the web application inside the container.</p><p><strong>Step 5 — Access the Application</strong></p><p>Now open your browser and visit:</p><pre>http://localhost/login</pre><p>OR use your system IP if running in a VM.</p><p><strong>Resources</strong></p><ul><li>GitHub: <a href="https://github.com/InsiderPhD/Generic-University">https://github.com/InsiderPhD/Generic-University</a></li><li>Docker Hub: <a href="https://hub.docker.com/r/busk3r/genericuniversity">https://hub.docker.com/r/busk3r/genericuniversity</a></li></ul><p>With the lab environment ready, it’s time to start exploring the API and uncovering its vulnerabilities.</p><p><strong>Your Goals</strong></p><ol><li>Find the emails of the administrator</li><li>Brute force the API to find new endpoints</li><li>Find out what grades everyone got in a class</li><li>Edit someone’s grade</li><li>Make an account</li><li>Access the GraphQL API</li><li>Change another account’s password</li><li>Login to your account</li><li>Access admin API</li><li>Find out what vulnerabilities the IT admins have ignored</li><li>Make your account an admin</li><li>Access the admin control panel</li><li>Fire a blind XSS in the admin control panel and validate with your new admin account</li><li>Delete everything</li><li>Restore everything</li></ol><p>Power up your <strong>BurpSuite</strong></p><ol><li><strong>Finding Admin Email (IDOR)</strong></li></ol><p><strong>Understanding Roles First</strong></p><p>Before identifying the administrator, I first needed to understand how the application manages user roles.</p><p>While interacting with the application as a normal user, I kept <strong>Burp Suite Proxy enabled</strong> to monitor all HTTP traffic.</p><p>During this process, I observed multiple API endpoints such as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*dDmPPW9iOAoO_amR9MPiIw.png" /></figure><p><strong>Analyzing Requests</strong></p><p>To further analyze these endpoints: /api/users/6</p><ul><li>I right-clicked on the request</li><li>Selected <strong>“Send to Repeater”</strong></li><li>Navigated to the <strong>Repeater tab</strong></li><li>Sent the request to the server</li></ul><p>This allowed me to manually inspect both the <strong>request and response</strong> in detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IdYRYKGAEwU_WUJuT2SyEg.png" /></figure><p>change /api/users to /api/roles and send request</p><p>The responses returned structured JSON data containing:</p><ul><li>Role information (Admin, Student, Teacher)</li><li>User details (name, role_id)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/956/1*N8I_SeLeIGQbbpOOdSYKjQ.png" /></figure><p>The above response indicates that the <strong>Admin role corresponds t</strong><strong>role_id = 1</strong>.<br>Using this information, I proceeded to enumerate all user data and identify which user had role_id = 1.<br>From the results, I observed that <strong>user ID 6 was assigned </strong><strong>role_id = 1, confirming that this account belongs to an administrator</strong>.<br>By accessing this user’s details, I was able to retrieve the <strong>administrator’s email address</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*iNqU1_9VetLAHCppHaCoxw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XjZ5lymI-KaSsaXpTPfRg.png" /></figure><p><strong>Done</strong>: From the response, we were able to extract the administrator’s email address: <strong>ynitzsche@grant.com</strong></p><p><strong>2. Brute force the API to find new endpoints</strong></p><p>To discover additional endpoints, we used <strong>Burp Suite Intruder</strong> to perform directory and endpoint brute-forcing.</p><p>We first captured a request such as:</p><pre>GET /login HTTP/1.1</pre><p>Next, we sent this request to <strong>Intruder</strong> and configured the payload position</p><p><strong>Intruder Configuration</strong></p><ul><li><strong>Attack Type:</strong> Sniper</li><li><strong>Payload Type:</strong> Simple List</li><li><strong>Payload Source:</strong> Custom wordlist (common API endpoints)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XkpOA4Li-YiESHtMzL15CQ.png" /></figure><p>After starting the attack, Burp Intruder tested multiple endpoint names automatically.</p><p>From the results, we identified valid endpoints based on:</p><ul><li><strong>HTTP 200 responses</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ol65cijPTqUgW-nn0kgytw.png" /></figure><p><strong>3. Find out what grades everyone got in a class</strong></p><p>To retrieve students’ academic data, we sent a request to the following endpoint:</p><pre>GET /api/grades</pre><p>The response returned a complete list of students along with their respective grades.</p><p>This confirms that the API exposes sensitive academic data without any access control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BipjhhCZr6srOgHNnkXCJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*lasp8VgSxHK6SxaF4sR7ug.png" /></figure><p>4. <strong>Edit someone’s grade</strong></p><p><strong>Step 1 : Retrieve a Specific Grade</strong></p><p>We first fetched an grade using:</p><pre>GET /api/grades/{grade_id}</pre><p>This returned detailed information for a student.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1jmGLkN-L326s23k_vL7fg.png" /></figure><p><strong>Step 2 : Check Allowed Methods</strong></p><p>Next, we tested the endpoint using the <strong>OPTIONS</strong> method: See if “<strong>PATCH</strong>’’ is allowed. The response revealed that the <strong>PATCH method was allowed</strong> for this endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WPzbPk8pF8D-A3PXQRv3Dw.png" /></figure><p><strong>Step 3 : Exploit the Vulnerability</strong></p><p>copied the original response body and modified it as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/1*p2Y2VrobwJ2BwXup7g_8_A.png" /></figure><p>now , in request body paste this json response</p><p>modify grade</p><p><strong>{</strong></p><p><strong>“grade”:&lt;new_grade&gt;</strong></p><p><strong>}</strong></p><p>Add the header : <strong>Content-Type: application/json</strong></p><p>Change the HTTP method to <strong>PATCH</strong>. Send the request and see the response.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8d3u1v4Y4BVT4mTJFCvjPQ.png" /></figure><p>The grade was successfully modified, confirming that the API allows unauthorized data manipulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sYXBVerdpxkuzozHu5D7CA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6gBq4TeT6aJrlsrvilLSqA.png" /></figure><p><strong>5. Make an account</strong></p><p>During enumeration, we identified a hidden <strong>/register</strong> endpoint that was not accessible through the application interface.</p><p>By directly navigating to this endpoint, we were able to register a new user account successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*fPBKEuczgxauDzNO9PilDA.png" /></figure><p><strong>6. Access the GraphQL API</strong></p><p>While continuing the enumeration process, we discovered that the <strong>/graphql</strong> endpoint exists and is accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*m7-8FAW-2oCYuTn5daM1dQ.png" /></figure><p>We sent the following query as a POST request:</p><pre>{<br>  &quot;query&quot;: &quot;{ __typename }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Un7KDvmcX7Qks0xoIekqcA.png" /></figure><p><strong>{<br> “query”: “{ __schema { types { name fields { name } } } }”<br>}</strong></p><p><strong>Initial Issue</strong></p><p>The server returned an error. This occurred because the request was missing the required header: <strong>Content-Type: application/json</strong></p><p>Without this header, the server was unable to properly interpret the request body as JSON, resulting in parsing errors such as:</p><p><strong>Syntax Error: Unexpected &lt;EOF&gt;</strong></p><p><strong>Fix the Request</strong></p><p>After adding the correct header : <strong>Content-Type: application/json</strong></p><p>we resent the request.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*WjLUSkG-2LU1qq1abaok7g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*4zNTLZHKfjkKWQsNv-n0zQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*LLm2L92m-8jgw0bK9irlOQ.png" /></figure><p>This query retrieves a list of all users along with their IDs, names, and email addresses from the GraphQL API.</p><p><strong>{</strong></p><p><strong>“query”: “{ users { id name email } }”</strong></p><p><strong>}</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*bXv0yorOg2dns3atMOy9kw.png" /></figure><p>This query retrieves detailed grade records, including scores, comments, timestamps, and associated user and class information from the GraphQL API.</p><p><strong>{</strong></p><p><strong>“query”: “{ grades { id grade comments created_at user { id name email } class { id name } } }”</strong></p><p><strong>}</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*BvlxouKelwgfgv1fY5oLAA.png" /></figure><p><strong>7. Change another account’s password</strong></p><p>This mutation allows us to change the password of a specific user by providing their ID, demonstrating a lack of proper authorization controls.</p><p><strong>{“query”: “mutation updateUserPassword($id: String!, $password: String!) { updateUserPassword(id: $id, password: $password) { id email } }”,“variables”: {“id”: “5”,“password”: “testuser123”}}</strong></p><p>we targeted the user with <strong>ID = 5 , person name : Deron Kemmer</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*cpsTpxkqbFPATDgLhAXkFQ.png" /></figure><p>Using the associated email and the newly set password, we successfully logged into the compromised account, confirming the effectiveness of the attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*G9dywHubNSW-KAasnjtTAA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*fvL-YTLqr4qptf-3_jTYkA.png" /></figure><p><strong>8. Login to your account</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*NaodeMcnSOsCGiJgGMWVSA.png" /></figure><p><strong>9. Access admin API</strong></p><p>During enumeration, we identified an <strong>/api/admin</strong> endpoint and proceeded to test access to this path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*NzZVCttD_ddinhHRT-L7Ow.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*rVDuXRjTOBtWqbMpouKafQ.png" /></figure><p><strong>10. Find out what vulnerabilities the IT admins have ignored</strong></p><p>To further explore administrative functionality, we performed endpoint enumeration on the <strong>/api/admin/</strong> path using <strong>Burp Suite Intruder</strong>.</p><ul><li>The request was configured with a payload position at:</li></ul><pre>/api/admin/§FUZZ§</pre><ul><li><strong>Attack Type:</strong> Sniper</li><li><strong>Payload:</strong> Wordlist containing common endpoint names</li></ul><p>After launching the attack, multiple endpoints were tested automatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*ZUEixjUcsBR-t9aXvDgd9w.png" /></figure><p>From the Intruder results, we identified the following endpoints returning <strong>HTTP 200 OK</strong>:</p><p>/api/admin/vulnerabilities</p><p>/api/admin/delete</p><p>This indicates that these endpoints exist and are accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*uCXaTe-fZEeIUBHvN4dxkw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*zWZ5bOfQ1aKumGTLJSUsXg.png" /></figure><p><strong>11. Make your account an admin</strong></p><p>Identify the admin’s role_id (usually 1).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*O591ROMGUreQDdPueUqdwg.png" /></figure><p>Your account likely has a different role_id (e.g., 2 for students).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33fwTczWKkAcDS3U7mAHpg.png" /></figure><p>We checked the allowed methods for /api/users/{id} and observed that the <strong>PATCH method was enabled</strong>, allowing us to modify the user role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*lgsxE8QwM3drDT43SZ4wGw.png" /></figure><p>Now, using <strong>PATCH </strong>method to update our role id from 2 → 1</p><p>(student → admin)</p><p><strong><em>{</em></strong></p><p><strong><em>“role_id”:1</em></strong></p><p><strong><em>}</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cgpWmp5lP_qykVp6TtGrfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*ogTSOxjzTIh2oi0AK15wqw.png" /></figure><p>We successfully gained access to the <strong>/api/admin/vulnerabilities</strong> endpoint, achieving Goal 10</p><p><strong>12. Access the admin control panel</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*AAfhQwGi8ajumpCtMxGo0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*74Xp3QfGrb2P5spuhLx3Pw.png" /></figure><p><strong>13. Fire a blind XSS in the admin control panel and validate with your new admin account</strong></p><p>As this feature is not available in the Community Edition,full verification of this step could not be performed.</p><p><strong>14. Delete everything</strong></p><p>Use the admin API’s <strong>/delete</strong> function to remove all users from the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BVnldCMnmsBblA_0txl7JQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bIJyOqb3-Bue2Rel86SobA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vtixd4VP-KGwa5270fmjSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqU77qIY72OXPA9Q1SDXlQ.png" /></figure><p>Only one user remains, and this account corresponds to the administrator (Admin ID).</p><p><strong>15. Restore everything</strong></p><p>use the admin API’s <strong>/restore</strong> function to restore data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PbJMd5KKu7Dt4Td6C55gUg.png" /></figure><p>That’s a complete walkthrough!</p><p>If this helped you understand API hacking better, consider giving it a clap and sharing it with others</p><p>Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4079ab8b3911" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Qubes OS: The Operating System That Assumes You’ve Already Been Hacked]]></title>
            <link>https://medium.com/@chirangidodiya/qubes-os-the-operating-system-that-assumes-youve-already-been-hacked-f009c0a94440?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/f009c0a94440</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Tue, 03 Mar 2026 12:15:53 GMT</pubDate>
            <atom:updated>2026-03-03T12:15:53.474Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/649/1*B_d0PrgZt3bwpPG4tYP61w.png" /></figure><p>What if your operating system didn’t try to <strong>prevent every attack</strong>, but instead assumed one day something <em>will</em> break and prepared for it?</p><p>That’s exactly the philosophy behind <strong>Qubes OS</strong>.</p><p><a href="https://www.google.com/search?q=Qubes+OS&amp;sca_esv=cb0b2358a0071c17&amp;sxsrf=ANbL-n4lN6P6kI-xc_y71dc0vaBAwSafog%3A1772531478630&amp;ei=Fq-maa-hJsG8seMPhNCz2QY&amp;biw=1536&amp;bih=730&amp;ved=2ahUKEwi9xrOtu4OTAxWAcWwGHbzXOOgQgK4QegQIARAD&amp;uact=5&amp;oq=what+is+qubes+os&amp;gs_lp=Egxnd3Mtd2l6LXNlcnAiEHdoYXQgaXMgcXViZXMgb3MyCxAAGIAEGJECGIoFMgYQABgHGB4yCxAAGIAEGJECGIoFMgsQABiABBiRAhiKBTIGEAAYCBgeMgsQABiABBiGAxiKBTIIEAAYgAQYogRIwOcPUK7XD1jn3g9wBHgBkAEAmAHBAqABgg6qAQcwLjQuMi4yuAEDyAEA-AEBmAIFoALlAsICChAAGLADGNYEGEfCAg0QABiABBiwAxhDGIoFmAMAiAYBkAYKkgcFNC4zLTGgB5s8sgcDMy0xuAfGAsIHBTItNC4xyAcZgAgA&amp;sclient=gws-wiz-serp&amp;mstk=AUtExfCvlSPCmDmsDIA2Zsdi5pjxbltbRLjTVZ26wVUzfmsGhr6zVSBOl0AkYFqiHIm6Ll_2qYtMsxfFoks90IJ6KHyW67tY_xGVaHbnb2M0Qjyr2qLAysyU7OvGkXhdU46x5B5stoZyCjsZfkUZwFqTnp4zyH3FLbvJ4WJxTgI6TYTYHW4DNXKWYKxqV6W9E3_70B06-CMlGKVyAuwuF-KBMffSnVI_ShoH0bS_hmTrU0KZOIkM-fPIs2R-iMFh7QH8QGPma0Molsh73WYAsVNBIV2w&amp;csui=3">Qubes OS</a> is a security-focused, open-source operating system that utilizes a “security by compartmentalization” model. Based on the <a href="https://www.geeksforgeeks.org/introduction-of-qubes-os/">Xen hypervisor</a>, it isolates applications and network stacks into separate, lightweight virtual machines called “qubes,” ensuring that a compromise in one area (e.g., browser) does not affect the rest of the system.</p><p><em>If one thing gets compromised, the rest of your system stays safe.</em></p><p><strong>Deep Dive: The Mechanics</strong></p><p><strong>1.Building the Walls</strong></p><p>Developed on the philosophy of <strong><em>“Trust No One, Isolate Everything.” </em></strong>By containing the blast radius, catastrophes become isolated incidents. Famous advocates like Edward Snowden rely on its physical-air-gap-equivalent security.</p><p><strong>2.Living in the Qube</strong></p><p>Operates using the Xen hypervisor to create autonomous “qubes” for Work, Personal, and Disposable tasks. Closing a disposable qube removes every trace of interaction, offering true peace of mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*Yq2bCjsrMCHbXVIf_s0V9Q.png" /></figure><p><strong>Understanding the Architecture of Qubes OS: A Layered Security Model</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*regqetupeRCNtBkPdo8UfA.png" /></figure><p>When people first hear about <strong>Qubes OS</strong>, they often assume it is just another Linux distribution with strong security defaults. In reality, Qubes OS is a carefully engineered system built around one central idea:</p><p><em>Security is strongest when components are isolated by design.</em></p><p>To understand how Qubes achieves this, we need to look at its layered architecture. Each layer has a specific responsibility, and together they create a highly compartmentalized and controlled computing environment.</p><p><strong>1. Physical Hardware and PCI Passthrough</strong></p><p>At the foundation of Qubes OS is the physical hardware:</p><ul><li>Network interfaces (Wi-Fi, Ethernet)</li><li>Storage devices (SSD, HDD)</li><li>USB controllers</li><li>Graphics hardware</li><li>Audio devices</li></ul><p>In traditional operating systems, hardware drivers run within the same environment as user applications. This creates risk: if a device driver is compromised, the attacker may gain access to the entire system.</p><p>Qubes OS takes a different approach by using <strong>PCI passthrough</strong>. Instead of the main system directly controlling hardware, individual devices are assigned to specific virtual machines.</p><p>For example:</p><ul><li>The Wi-Fi adapter is assigned to a dedicated network qube.</li><li>USB controllers can be assigned to a separate USB qube.</li><li>Audio hardware is handled by an isolated audio backend.</li><li>Storage devices are managed by a block backend.</li></ul><p>This separation significantly reduces risk. If a hardware driver is exploited, the compromise is contained within that specific qube rather than affecting the entire system.</p><p><strong>2. Isolation Provider Layer : The Hypervisor</strong></p><p>Above the hardware sits the hypervisor layer. Qubes OS is primarily built on the <strong>Xen</strong> hypervisor.</p><p>The hypervisor is a type-1 (bare-metal) virtualization layer that runs directly on hardware. Its core responsibilities include:</p><ul><li>Creating and managing virtual machines (VMs)</li><li>Isolating memory between VMs</li><li>Allocating CPU resources</li><li>Enforcing strict separation so VMs cannot directly access each other</li></ul><p>This layer forms the technical foundation of Qubes security. Without a strong hypervisor, the entire isolation model would fail. Xen ensures that each qube operates within its own protected memory and execution space.</p><p><strong>3. Qubes Hypervisor Abstraction Layer (HAL)</strong></p><p>On top of the hypervisor sits the Qubes-specific management layer, often referred to as the Hypervisor Abstraction Layer (HAL).</p><p>This is where Qubes OS differentiates itself from a standard virtualization setup.</p><p>The HAL is responsible for:</p><ul><li>Creating and configuring qubes</li><li>Managing inter-qube communication</li><li>Enforcing security policies</li><li>Assigning hardware devices to specific qubes</li><li>Controlling permissions and trust levels</li></ul><p>In other words, this layer turns raw virtualization into a structured security architecture. It defines how trust is distributed, how data flows between environments, and how isolation boundaries are enforced.</p><p>Without this layer, Qubes would simply be a collection of virtual machines. With it, Qubes becomes a coherent security model.</p><p><strong>4. The Qubes (Virtual Machines)</strong></p><p>At the top of the architecture are the qubes themselves — the environments where applications actually run.</p><p>Each qube is an isolated virtual machine designed for a specific purpose or trust level.</p><p>Common examples include:</p><p><strong>1.Personal Qube : </strong>Used for everyday private activities such as browsing, document editing, and communication.</p><p><strong>2.Work Qube : </strong>Dedicated to professional tasks and corporate resources.</p><p><strong>3.Untrusted or Random Qube : </strong>Designed for risky activities such as opening unknown files or visiting unfamiliar websites.</p><p>Each qube operates independently. If the untrusted qube becomes compromised, the work and personal qubes remain unaffected due to enforced isolation at the hypervisor level.</p><p><strong>Backend Qubes: Isolated System Services</strong></p><p>In addition to user-facing qubes, Qubes OS uses specialized backend qubes that manage system services.</p><p><strong>Network Backend : </strong>Handles all networking tasks. Other qubes connect to the internet indirectly through this backend, preventing them from interacting directly with network hardware.</p><p><strong>Block Backend : </strong>Manages storage devices such as disks and external drives.</p><p><strong>GUI Backend : </strong>Handles graphical display services.</p><p><strong>Audio Backend : </strong>Manages sound hardware.</p><p><strong>Admin Domain (dom0) : </strong>The most privileged and trusted domain in Qubes OS.</p><p>dom0:</p><ul><li>Controls the desktop environment</li><li>Manages creation and configuration of qubes</li><li>Has no direct internet access</li><li>Does not run network-facing applications</li></ul><p>This design is critical. Even if a browser inside a user qube is compromised:</p><ul><li>It cannot directly access hardware.</li><li>It cannot communicate freely with other qubes.</li><li>It cannot reach dom0.</li><li>It cannot control system management functions.</li></ul><p>The attack surface is intentionally fragmented.</p><p><strong>How the Layers Work Together</strong></p><p>The Qubes architecture can be understood as a layered trust model:</p><ol><li>Physical hardware provides computing resources.</li></ol><p>2. The hypervisor isolates virtual machines at the memory and CPU level.</p><p>3. The Qubes management layer enforces security rules and device assignments.</p><p>4. Backend qubes control hardware services in isolated environments.</p><p>5. Application qubes run user tasks at defined trust levels.</p><p>6. dom0 manages the system while remaining offline.</p><p>Each layer minimizes implicit trust. No single component is allowed unlimited authority.</p><p>Instead of relying on a single large security boundary, Qubes distributes trust across isolated compartments. If one compartment fails, the system as a whole remains intact.</p><p><strong>Conclusion :</strong></p><p>The architecture of Qubes OS demonstrates a fundamental shift in operating system design. Rather than attempting to prevent every possible vulnerability, it assumes that compromises may occur and focuses on containment.</p><p>By combining hardware-level virtualization, strict hypervisor isolation, structured management policies, and dedicated service qubes, Qubes OS creates a resilient environment built around compartmentalization.</p><p>It is not simply a secure operating system — it is an operating system engineered around the principle that isolation is the strongest form of defense.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f009c0a94440" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can Recuva Recovered Files Stand in Court? Section 65B Holds the Key!]]></title>
            <link>https://medium.com/@chirangidodiya/can-recuva-recovered-files-stand-in-court-section-65b-holds-the-key-8a44f894a029?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a44f894a029</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Tue, 03 Mar 2026 08:08:08 GMT</pubDate>
            <atom:updated>2026-03-03T08:08:08.199Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*zz5pebKFB7qz2cWHFB5sjA.png" /></figure><p><strong>Introduction to Section 65B (Indian Evidence Act, 1872) :</strong></p><p>Section 65B of the <a href="https://indiankanoon.org/doc/487818/">Indian Evidence Act, 1872</a>, often discussed in the context of cyber law, governs the admissibility of electronic records as evidence. It mandates that computer-generated output, such as emails, digital documents, or logs, must be accompanied by a certificate to be admissible in court, ensuring the device was functioning properly and not tampered with.</p><p><strong>Key Aspects of Section 65B:</strong></p><ul><li><strong>Admissibility of Electronic Records:</strong> It deems information from a computer (printed, stored, or copied) as a document if specific conditions are met, allowing it to be admissible without needing the original device.</li><li><strong>Mandatory Certificate (65B(4)):</strong> A certificate is required to verify the electronic record’s authenticity, identifying the device and the manner of production.</li><li><strong>Conditions for Validity:</strong> The computer must have been in regular use, information must have been fed in the ordinary course of activity, and the device must have been operating properly.</li><li><strong>Purpose:</strong> It ensures that digital evidence (secondary evidence) is reliable and authentic before being admitted in legal proceedings.</li></ul><p>This provision is critical in cyber forensics, email fraud investigations, and analysis of digital documents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YCqzJWtPNiW9aAHS" /></figure><p><strong>Case Context</strong></p><p><strong>Tool Used:</strong> Recuva<br> <strong>Device:</strong> 16GB USB Flash Drive<br> <strong>Purpose:</strong> Recovery and forensic analysis of deleted data<br> <strong>Legal Compliance:</strong> Section 65B</p><p><strong>About Recuva :</strong></p><p>Recuva is a, free, user-friendly Windows utility by CCleaner used for data recovery and basic forensic analysis to retrieve deleted files, photos, videos, and documents from hard drives, USB drives, and memory cards. It works by scanning the Master File Table (MFT) for file markers, supports deep scans for formatted/damaged drives, and allows secure file overwriting.</p><p><strong>Key Features of Recuva for Data Recovery</strong></p><ul><li><strong>Deep Scan Mode:</strong> If a standard scan fails, Deep Scan searches for file signatures (header/footer) to recover deeply buried or heavily corrupted data.</li><li><strong>Recover from Damaged/Formatted Disks:</strong> Recuva can recover files from reformatted or severely damaged drives.</li><li><strong>Virtual File System Analysis:</strong> It works by reading the MFT for file markers and file metadata, which allows it to locate files even if the operating system considers the space empty.</li><li><strong>File Type Flexibility:</strong> Recuva can recover photos, music, documents, videos, and emails.</li><li><strong>Secure Deletion:</strong> It includes a secure overwrite feature to permanently erase files, making them unrecoverable.</li></ul><p><strong>Forensic Analysis Workflow with Recuva :</strong></p><p>Recuva helps forensic investigators in the early stages of evidence gathering (Identification and Preservation).</p><p>1. <strong>Launch &amp; Select Drive:</strong> Open Recuva and select the storage device (e.g., USB stick, external drive) to be analyzed.</p><p>2. <strong>Initial Scan:</strong> Run a quick scan to find files deleted from the Recycle Bin or recently deleted.</p><p>3. <strong>Color-Coded Analysis:</strong> Recuva identifies file state by color:</p><p>1. <strong>Green:</strong> Excellent (fully recoverable).</p><p>2. <strong>Yellow:</strong> Poor (partially overwritten).</p><p>3. <strong>Red:</strong> Unrecoverable (overwritten).</p><p>4. <strong>Deep Scan &amp; Advanced Mode:</strong> If necessary, enable “Deep Scan” in options for a more thorough investigation of unallocated space.</p><p>5. <strong>Recovery:</strong> Select the files and restore them to a <em>different</em> drive to avoid overwriting existing evidence.</p><p><strong>Forensic Best Practices</strong></p><ul><li><strong>Do Not Write to Source:</strong> When performing forensics, never recover files to the same drive you are scanning, as this can destroy other evidence.</li><li><strong>Use Read-Only Mode:</strong> Ensure that if you are using Recuva on a forensic image, you do not alter the source, or if working on a live system, you follow, secure, and document the process.</li></ul><p>Recuva is effective for quick, non-technical forensic investigations, but for deep, legal-grade, or complex forensics, it is often paired with more advanced forensic tools.</p><p><strong>Forensic Analysis of 16GB USB (65B Compliant)</strong></p><p><strong>STEP 1: Seizure &amp; Documentation</strong></p><p>· <strong>Photograph USB device</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/264/1*oE9_Or6sFHRiAMl4PsAfOw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/261/1*BCdzZNjbn8-goMjFxklOBw.png" /></figure><p>· <strong>Identified Device</strong></p><p><strong>Device Type : </strong>USB Flash Drive</p><p><strong>Brand: </strong>Sony</p><p><strong>Manufacturer: </strong>Sony Corp.</p><p><strong>Country of Manufacture: </strong>Made in Korea</p><p><strong>Model Code (Visible): </strong>USM16W</p><p><strong>Serial Number (Visible): </strong>16930AGSNN</p><p><strong>Color : </strong>Black</p><p><strong>Regulatory Markings:</strong></p><ul><li><strong>EAC (Eurasian Conformity)</strong></li><li><strong>KC (Korea Certification)</strong></li><li><strong>FCC (Federal Communications Commission)</strong></li><li><strong>CE (European Conformity)</strong></li></ul><p><strong>STEP 2: Write Protection (Critical)</strong></p><p><strong>To prevent alteration:</strong></p><ul><li><strong>Use a hardware write blocker<br> OR</strong></li><li><strong>Use forensic boot environment</strong></li></ul><p><strong>Never directly scan the original USB in normal OS.</strong></p><p><strong>STEP 3: Create Forensic Image</strong></p><p><strong>Tool Used : FTK imager</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*t-DoG8Un2p70qEMLoABaGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*4WI_4wZvIQxkIw1bU0lGrw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*1keXUSoVfPI-78Cd1QkITQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*zqNZCJOeXo7jhQgq736DKA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*eI1fVDotIWwaMaRUltQX-A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*Yb6O9OjGINsPfHHud0Xe2g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/582/1*u3erO26sZ6bs6oa9BcRevQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/501/1*KV34o4TLTSXkH8eFtiLy9Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/471/1*_cNZZs2QuOSS5Hs0kQBloQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*mdjCAtda5wHfT79NlS_e1w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*9_8L1FfnaplD__renr7FYw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/464/1*ZSbKLK_eGCJiXkvtKiojaQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*MfkTpVJLYR_eYoLqrEmEFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*Vs-ZISH01TItec7KSeJw2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aEjBi5nM1wR6977Aqx0H1A.png" /></figure><p><strong>STEP 4: Generate Hash Value</strong></p><p>· Using Command Prompt (Windows)</p><p>· Case101.E01</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rFWrQ-HUPyWKrt2IUOUwug.png" /></figure><p><strong>STEP 5 : Mount the E01 Image</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*WkKI-_so-jiMl9WKvSf9IQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/644/1*XJrUgCI9OIM8AsWzUPSHIA.png" /></figure><p><strong>STEP 6: Perform Recovery Using Recuva</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/1*hrCXou9c-R2tXoyL_48PEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*nyH1TyeDMiihjI4UoZEV5A.png" /></figure><p>· <strong>Select File Location -&gt; Select your Mount USB drive</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/371/1*SCmqWpq8gEagb6MSt0ZcqA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*6kF8aYczhV-zri2vnmXMIg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*ws1aDtjgg4Ufcs1L86ts3w.png" /></figure><p>· <strong>View Scan Results</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ohGs-Hs3b8LismCOz98ApQ.png" /></figure><p>· <strong>Recover Files</strong></p><p>· <strong>Steps:</strong></p><p>1. Select the checkbox next to file</p><p>2. Click Recover</p><p>3. Choose recovery location</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VA0xRVhHNsPDszeXV2yEFQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/518/1*oun7jLiBvmgZAP-Y46xMRg.png" /></figure><p>· <strong>Verification Step</strong></p><ol><li>Open recovery folder</li><li>Check recovered file</li><li>Verify file content opens correctly</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Nu1LwDa5O_Yy47CjrvCzQ.png" /></figure><p>· <strong>Result</strong></p><p>Deleted files from USB drive were successfully recovered using Recuva. The software identified recoverable files and restored them to a secure location.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*49eMqQWAvquzeaMxsWYwNg.jpeg" /></figure><p><strong>STEP 7: Generate Hash for Recovered Files</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MWI-EQ7Veqxkj2GjNlKmqw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a44f894a029" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Email Compromise : It Looked Like an Email From My Boss ,Until Millions Were Gone]]></title>
            <link>https://medium.com/@chirangidodiya/business-email-compromise-it-looked-like-an-email-from-my-boss-until-millions-were-gone-9d789e5deb8c?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d789e5deb8c</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Tue, 20 Jan 2026 11:46:27 GMT</pubDate>
            <atom:updated>2026-01-20T11:46:27.676Z</atom:updated>
            <content:encoded><![CDATA[<h3>Business Email Compromise : It Looked Like an Email From My Boss ,Until Millions Were Gone</h3><p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*yhlpnzNzn-wg4wL5PEMNag.png" /></figure><p>It’s 4:47 PM.<br>You’re wrapping up work, half-thinking about heading home, when a new email pops up.</p><p><strong>From:</strong> CEO<br><strong>Subject:</strong> Urgent need this done now</p><p><em>“I’m in a meeting. Please wire this payment immediately. Keep this confidential. I’ll explain later.”</em></p><p>Your heart rate jumps.</p><p>The request isn’t unusual. The tone feels right. The timing makes sense.<br>And the sender? Someone you trust.</p><p>You act fast , because that’s what good employees do.</p><p>Minutes later, the money is gone.<br>And the email?<br>It was never from your CEO.</p><p>This is <strong>Business Email Compromise (BEC)</strong> : one of the most expensive and dangerous cyber scams in the world. Not because it’s flashy, but because it feels normal.</p><p><strong>What Is Business Email Compromise (BEC)?</strong></p><p>Business Email Compromise is a form of <strong>targeted social-engineering</strong> attack that leverages <strong>email spoofing</strong>, account compromise, and reconnaissance to fraudulently initiate financial transactions or data exfiltration without deploying malware.</p><p><strong>Business Email Compromise (BEC)</strong> is a targeted cybersecurity threat in which attackers impersonate trusted individuals such as</p><ul><li><strong>executives, finance staff, lawyers, or vendors</strong></li></ul><p>using compromised or spoofed email accounts to steal money or sensitive information.</p><p>Unlike traditional phishing attacks that rely on malicious links and are sent in bulk, BEC attacks are <strong>highly targeted and research-driven</strong>. Attackers study organizational structures, payment processes, and email conversations to identify employees with financial authority.</p><p>BEC is difficult to detect because the emails closely resemble legitimate business communication and often bypass technical security controls. What makes it especially dangerous is that it exploits <strong>human trust, urgency, and routine workflows</strong>, rather than technical vulnerabilities.</p><ul><li><strong>How BEC Attacks Actually Work</strong></li></ul><p>Business Email Compromise (BEC) attacks succeed because they combine <strong>technical email manipulation</strong> with <strong>psychological pressure on employees</strong>. Instead of hacking systems directly, attackers focus on making their messages look <strong>legitimate and urgent</strong>, so people act without verifying.</p><ol><li><strong>Targeting &amp; Reconnaissance</strong>: Cybercriminals use public information from social media and corporate websites to identify key personnel, such as HR or finance employees and high-ranking executives (CEO, CFO).</li><li><strong>Impersonation</strong>: Attackers create fraudulent email accounts that look nearly identical to a legitimate one (e.g., john.kelley@ instead of john.kelly@) or gain access to a real email account through credential theft.</li><li><strong>Social Engineering</strong>: The attacker sends a convincing email using tactics like urgency (“immediate action required”), authority (impersonating a superior), and confidentiality (“keep this private”) to pressure the victim into acting quickly without verification.</li><li><strong>Execution</strong>: The victim performs the requested action, such as an unauthorized wire transfer to a fraudulent bank account or the release of sensitive employee W-2 forms.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*WzTBdeHjADLsP1mITspI9A.png" /></figure><p><strong>Why BEC Attacks Are Hard to Detect</strong></p><p>BEC emails often <strong>bypass traditional security defenses</strong> because:</p><ul><li>They don’t contain malicious links or attachments</li><li>They look like normal business emails</li><li>They come from legitimate or trusted-looking accounts</li><li>They arrive during busy or high-stress moments (end of quarter, audits, deals)</li></ul><p>Employees may hesitate to question requests that appear to come from senior leadership, especially when urgency is emphasized.</p><p><strong>Common Types of BEC Scams</strong></p><ul><li><strong>CEO Fraud</strong>: The scammer impersonates a high-level executive, typically the CEO, and pressures a finance employee to make an urgent, confidential wire transfer for a bogus reason, such as a time-sensitive acquisition.</li><li><strong>False Invoice/Vendor Email Compromise (VEC)</strong>: Attackers pose as a legitimate supplier and send a fake or altered invoice with modified banking details to redirect payments.</li><li><strong>Attorney Impersonation</strong>: The scammer pretends to be a lawyer or legal representative working on a confidential legal matter, pressuring employees into hasty payments or data disclosure, often targeting lower-level employees who may be less likely to question the request.</li><li><strong>Data Theft</strong>: These attacks primarily target HR departments to steal sensitive employee or customer data (like Social Security numbers or tax information), which can be used for future, more sophisticated attacks or sold on the dark web.</li></ul><p><strong>Prevention and Mitigation Strategies</strong></p><p>A multi-layered defense combining technical controls, procedural safeguards, and employee education is the most effective approach.</p><p><strong>Technical Controls</strong></p><ul><li><strong>Implement Multi-Factor Authentication (MFA)</strong>: Enforce MFA across all email accounts and critical systems to prevent unauthorized access, even if passwords are stolen.</li><li><strong>Deploy Email Authentication Protocols</strong>: Utilize protocols like SPF, DKIM, and DMARC (which many industries now mandate be set to ‘reject’ to prevent domain spoofing) to verify the authenticity of email senders.</li><li><strong>Use Advanced Email Security Solutions</strong>: Employ AI-driven filtering solutions that analyze behavioral patterns and content for anomalies, rather than just malicious links or attachments.</li><li><strong>Label External Emails</strong>: Configure email systems to automatically flag emails originating from outside the organization to alert employees to potential impersonation attempts</li></ul><p><strong>Employee Education</strong></p><ul><li><strong>Conduct Regular Security Awareness Training</strong>: Train employees to recognize red flags, such as unusual urgency, requests for confidentiality, and mismatched email addresses.</li><li><strong>Foster a Culture of Skepticism</strong>: Encourage employees to question unusual requests without fear of reprisal and to report anything that “feels off”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kTe7xwZ1d0Tpa2or.jpg" /></figure><p>Reporting a BEC Attack</p><p>If a BEC attack is suspected or successful, act immediately:</p><ol><li><strong>Freeze the transaction</strong>: Contact your bank or financial institution immediately to halt any initiated transfers.</li><li><strong>Alert your IT department or security team</strong>.</li><li><strong>File a complaint with the FBI’s Internet Crime Complaint Center (IC3)</strong> at <a href="https://www.ic3.gov/">ic3.gov</a>.</li></ol><p><strong>Final Thought: BEC Is a Trust Problem, Not a Tech Problem</strong></p><p>Business Email Compromise works because it looks like business as usual.</p><p>The strongest defense isn’t fear it’s <strong>verification, awareness, and culture</strong>.<br> When employees feel empowered to double-check <em>any</em> request even from leadership scammers lose their advantage.</p><p>Because in cybersecurity, <strong>it’s always okay to ask twice</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d789e5deb8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Click, One Mistake: How Cyber Laws in India Decide Your Digital Fate]]></title>
            <link>https://medium.com/@chirangidodiya/one-click-one-mistake-how-cyber-laws-in-india-decide-your-digital-fate-14110f0c2fe8?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/14110f0c2fe8</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Thu, 08 Jan 2026 18:52:04 GMT</pubDate>
            <atom:updated>2026-01-09T04:21:03.724Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*_g9jI9qAdF-dQEWmUhgzyw.png" /></figure><p>You don’t need to be a hacker to get into trouble under <strong>cyber law in India</strong>.</p><p>In today’s digital world, a single wrong click sharing an OTP, forwarding a message, posting a photo, or replying to a stranger online can turn into a <strong>cyber crime case</strong> without you even realizing it.</p><p>From UPI frauds and identity theft to cyberstalking and data misuse, <strong>India’s cyber laws under the Information Technology Act, 2000</strong> affect every person who uses a smartphone, social media, or online banking.</p><p>Yet most people still believe cyber law is only for criminals or tech experts.</p><p>It’s not.</p><p>Every WhatsApp message, email, Instagram DM, and online transaction you make leaves a <strong>digital footprint</strong> and Indian courts are increasingly treating these digital actions as <strong>real legal evidence</strong>.</p><p>This article explains India’s cyber laws in <strong>simple language</strong>, using <strong>real Indian court cases and everyday examples</strong>, so you understand how easily an ordinary person can fall into legal trouble and how to stay safe.</p><p>You don’t need to be a hacker to break a cyber law. Sometimes, all it takes is one careless click.</p><p><strong>The Digital Life We Live Today</strong></p><p>From ordering food and paying bills to storing photos and chatting with friends our lives now exist online.</p><p>But here’s the uncomfortable truth:</p><p>The internet remembers everything and the law watches quietly.</p><p><strong>The Backbone of Cyber Law in India</strong></p><p>India handles most cyber crimes through the Information Technology Act, 2000, along with provisions from the Indian Penal Code and laws related to electronic evidence.</p><p>Let’s understand them without legal jargon.Information Technology Act, 2000 India’s Cyber Shield</p><p><strong>This law exists to protect:</strong></p><p>Your data</p><p>Your identity</p><p>Your privacy</p><p>Your dignity online</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*33nRZj4xKIgfpGFfFSlPEA.png" /></figure><p><strong>What Crimes Does It Cover?</strong><br>Section 66 : Hacking into someone’s system<br>Section 66C : Identity theft (misusing Aadhaar, PAN, passwords)<br>Section 66D : Online cheating &amp; phishing<br>Section 67 : Publishing obscene content online<br>Section 43 : Damage to computer systems<br>Section 72 : Breach of confidentiality &amp; privacy<br>Section 69 : Intercepting or monitoring data</p><p><strong>Case Study 1: “I Just Shared an OTP”</strong></p><p><strong>Rohit</strong>, a 27 year old working professional, received a call claiming to be from his bank.</p><p><em>“Sir, your account will be blocked. Please share the OTP.”</em></p><p>He shared it.</p><p>Within minutes, ₹1.8 lakh vanished from his account.</p><p><strong>→What Law Applied?</strong></p><ul><li><strong>Section 66D (Cheating by personation online)</strong></li><li><strong>Section 66C (Identity theft)</strong></li><li><strong>IPC 420 (Cheating and fraud)</strong></li></ul><p><strong>→ Lesson: </strong>Banks <strong>never ask for OTPs</strong>.<br>One moment of panic can turn into months of legal struggle.</p><p><strong>Cyberstalking Is Not “Just Messaging”</strong></p><p><strong>Case Study 2: “He Said It Was Love”</strong></p><p><strong>Ananya</strong>, a college student, started receiving messages from an unknown Instagram account.</p><p>At first, compliments.<br> Then obsession.<br> Then threats.</p><p>Fake accounts were created. Her photos were morphed. She was scared to step out.</p><p><strong>→ Laws That Protected Her</strong></p><ul><li><strong>IPC Section 354D →Cyberstalking</strong></li><li><strong>IT Act Section 67 →Obscene content online</strong></li><li><strong>Section 72 →Breach of privacy</strong></li></ul><p>→ <strong>Lesson: </strong>Online harassment is <strong>not harmless flirting</strong>.<br> The law recognizes <strong>digital trauma as real trauma</strong>.</p><p><strong>When Screenshots Become Courtroom Evidence</strong></p><p>Many people ask:</p><p><em>“Can WhatsApp chats or emails really be used in court?”</em></p><p>Yes. And that’s where <strong>Electronic Evidence Law</strong> comes in.</p><p>These rules explain <strong>how digital data becomes legal proof</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/542/1*azE1IoHa7yeq1TnL0hJORw.png" /></figure><p><strong>Case Study 3: “The Screenshot Saved Her”</strong></p><p><strong>Meera</strong>, an HR executive, was accused of misconduct by a former colleague.</p><p>She had:</p><ul><li>Emails</li><li>Office chat logs</li><li>System login records</li></ul><p>All backed by <strong>Section 65B certification</strong>.</p><p><strong>→ Outcome:</strong></p><p>The court accepted the digital evidence.<br> Meera was cleared. The false case collapsed.</p><p><strong>→ Lesson: Screenshots alone are not enough</strong>.<br> They must follow legal procedures to be accepted.</p><p><strong>Common Myths About Cyber Law :</strong></p><p>“Deleting messages means deleting evidence”<br> “Fake accounts are untraceable”<br> “Online crimes aren’t serious”<br> “Only big hackers get caught”</p><p><strong>Reality</strong>: Digital footprints never disappear.</p><p><strong>How You Can Stay Safe (And Legal) :</strong></p><ul><li>Never share OTPs or passwords</li><li>Use strong, unique passwords</li><li>Avoid clicking unknown links</li><li>Save important digital conversations</li><li>Enable two-factor authentication</li><li>Report cyber crimes immediately</li></ul><p>In India, cyber crime can be reported online via government portals or local cyber cells.</p><p><strong>Final Thought :</strong></p><p>The internet gives us <strong>power</strong>, but power comes with <strong>responsibility</strong>.</p><p>You don’t need to fear cyber laws you need to <strong>understand them</strong>.</p><p>Because in today’s world:</p><p><strong><em>Ignorance of cyber law is no longer an excuse ,it’s a risk.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14110f0c2fe8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Inside a Digital Investigation: How Deleted Data Is Recovered Using Linux Forensic Tools]]></title>
            <link>https://medium.com/@chirangidodiya/inside-a-digital-investigation-how-deleted-data-is-recovered-using-linux-forensic-tools-e8389e0bfa9f?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8389e0bfa9f</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Sat, 27 Dec 2025 19:56:28 GMT</pubDate>
            <atom:updated>2025-12-27T20:02:33.938Z</atom:updated>
            <content:encoded><![CDATA[<h4>Introduction</h4><p>Digital evidence plays a critical role in modern investigations. From cybercrime to corporate incidents, investigators rely on <strong>forensic disk images</strong> to uncover what happened on a storage device — without ever touching the original data.</p><p>In this article, I’ll take you inside a <strong>realistic digital forensic workflow</strong> using <strong>Kali Linux</strong>, where we analyze a forensic disk image, explore its internal structure, and recover <strong>deleted files</strong> using industry-standard tools.</p><p>This guide is designed for <strong>beginners</strong>, <strong>students</strong>, and <strong>anyone curious about how digital forensics actually works in practice</strong>.</p><h4>Why Investigators Use Disk Images Instead of Real Devices</h4><p>In digital forensics, working directly on a suspect’s device can:</p><ul><li>Alter timestamps</li><li>Modify metadata</li><li>Destroy evidence</li></ul><p>To avoid this, investigators create a <strong>forensic image</strong>, which is an exact bit-by-bit copy of a storage device.<br> All analysis is performed on this image, ensuring:</p><ul><li>🔒 Evidence integrity</li><li>⚖️ Legal admissibility</li><li>📜 Repeatable results</li></ul><h4>Investigation Environment</h4><ul><li><strong>Operating System:</strong> Kali Linux</li><li><strong>Analysis Method:</strong> Read-only forensic analysis</li><li><strong>Evidence Source:</strong> A disk image stored in a pendrive</li><li><strong>Objective:</strong></li><li>Verify evidence integrity</li><li>Examine disk structure</li><li>Identify deleted files</li><li>Recover deleted data</li></ul><h4>Tools Used in the Investigation</h4><h4>🧰 EWF Tools</h4><p>Used to access forensic disk images in a safe, read-only manner.</p><h4>🧰 The Sleuth Kit</h4><p>A powerful open-source forensic toolkit used to:</p><ul><li>Analyze file systems</li><li>View metadata</li><li>List deleted files</li><li>Recover lost data</li></ul><p>These tools are <strong>widely accepted in academic and professional forensic investigations</strong>.</p><h4>Case Scenario</h4><ul><li>Operating System: <strong>Kali Linux</strong></li><li>Evidence Location:<br> /home/kali/PendriveEvidence/</li><li>Evidence Files:</li><li>test1.E01</li><li>test1.E02 (split image segment)</li><li>test1_hash.txt (hash value)</li></ul><p>The goal is to <strong>analyze the image and recover deleted data</strong> without modifying the original evidence.</p><h4>Evidence Integrity Verification</h4><p>Before any analysis begins, investigators must verify that the evidence has not been altered.</p><p>This is done using <strong>cryptographic hash values</strong>.</p><pre>sha1sum test1.E01</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*J1pFzKWZYA9MRoli5AHkLg.png" /></figure><p>The generated hash is compared with the original hash recorded during acquisition.</p><p>✅ <strong>Matching hash confirms that the evidence is authentic and unchanged</strong></p><p>This step is mandatory in professional forensic workflows.</p><h4>Step 1: Update Package Repository</h4><p>Before installing tools, update the system:</p><pre>sudo apt update</pre><h4>Step 2: Install Sleuth Kit</h4><p>Sleuth Kit is used for file system analysis and data recovery.</p><pre>sudo apt install sleuthkit</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*LAbGB7vAiUNL30ipT3qzcA.png" /></figure><p>Verify installation:</p><pre>fls -V</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*OMRRAZpM8bHvwLHT6UOsLQ.png" /></figure><h4>Step 3: Install EWF Tools</h4><p>EWF tools allow us to mount and access E01 image files.</p><pre>sudo apt install ewf-tools</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/1*zvvx_xbtlBoSsZ5oGZypsw.png" /></figure><h4>Step 4: Create a Mount Directory</h4><p>Create a directory where the E01 image will be mounted:</p><pre>sudo mkdir /mnt/ewf</pre><h4>Step 5: Mount the E01 Image</h4><p>Mount the forensic image using ewfmount.</p><pre>sudo ewfmount test1.E01 /mnt/ewf</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*IVade1KvR93iqTXdqyvA0Q.png" /></figure><p>After mounting, a virtual file named <strong>ewf1</strong> will be created:</p><pre>/mnt/ewf/ewf1</pre><p>This represents the raw disk image.</p><h4>Step 6: Identify Partition Layout</h4><p>Use mmls to see the partition structure of the disk image:</p><pre>sudo mmls /mnt/ewf/ewf1</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*eG9zbYSOLJj4w7sdgyHOFA.png" /></figure><p>This reveals:</p><ul><li>Partition types</li><li>Start and end sectors</li><li>Disk layout information</li></ul><p>📌 The <strong>starting sector (offset)</strong> is critical for all further analysis.</p><p>here, offset is 8064 so for all further analysis this offset use</p><h4>Step 7: File System Examination</h4><p>After identifying the correct offset, the file system is analyzed:</p><pre>fsstat -o 8064 /mnt/ewf/ewf1</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*1lBATYSjzLDJq241wMpZRg.png" /></figure><p>This provides valuable metadata such as:</p><ul><li>File system type (NTFS, FAT, EXT)</li><li>Cluster size</li><li>Volume label</li><li>Last mount time</li></ul><p>Metadata often plays a crucial role in timeline reconstruction.</p><h4>Step 8: Listing Files — Including Deleted Ones</h4><p>One of the most powerful aspects of forensic analysis is the ability to view deleted files.</p><pre>fls -o 8064 /mnt/ewf/ewf1</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/941/1*Dv_5aSKKtZ7uG1WFb48hiw.png" /></figure><p>🔍 Files marked with an asterisk (*) indicate <strong>deleted content</strong>.</p><p>Example:</p><pre>r/r * 37: Pearls.jpg</pre><p>Even though the file is deleted, its metadata and data blocks may still exist on disk.</p><h4>Step 9: Recovering Deleted Data</h4><p>To recover a deleted file, investigators use its <strong>inode number</strong>.</p><pre>icat -o 8064 /mnt/ewf/ewf1 37 &gt; Pearls_confidential.jpg</pre><p>🎉 The deleted file is successfully extracted without modifying the original evidence.</p><p>👉 Image open :</p><pre>xdg-open Pearls_confidential.jpg</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*BvaeYHhcY_DPWmqt9gthkw.png" /></figure><p>This demonstrates how <strong>deletion does not mean destruction</strong> in digital systems.</p><h4>Core Forensic Principles Followed</h4><p>Throughout this investigation, key forensic principles were maintained:</p><ul><li>🔐 Read-only analysis</li><li>🧾 Hash-based integrity verification</li><li>📜 Proper documentation</li><li>⚖️ Use of court-accepted tools</li></ul><p>These principles ensure that findings remain <strong>technically accurate and legally defensible</strong>.</p><h4>What This Teaches Us About Digital Evidence</h4><ul><li>Deleted files can often be recovered</li><li>File systems retain metadata long after deletion</li><li>Proper tools reveal information invisible to normal users</li><li>Digital forensics is as much about <strong>process</strong> as it is about <strong>tools</strong></li></ul><h4>Conclusion</h4><p>Digital forensics transforms raw data into meaningful evidence.<br> By carefully analyzing disk images using Linux forensic tools, investigators can uncover hidden files, reconstruct user activity, and recover critical information — all while preserving evidence integrity.</p><p>This hands-on approach demonstrates why digital forensics remains one of the most fascinating and impactful fields in cybersecurity today.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8389e0bfa9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Nobody Told You About File Systems: Understanding FAT32, exFAT & NTFS in Minutes]]></title>
            <link>https://medium.com/@chirangidodiya/what-nobody-told-you-about-file-systems-understanding-fat32-exfat-ntfs-in-minutes-aa3dd18ed3f3?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa3dd18ed3f3</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 15:02:12 GMT</pubDate>
            <atom:updated>2025-12-04T15:02:12.336Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*eM7nomgZ9qkrF7L0Wth2LA.png" /></figure><h4>Introduction</h4><p>Have you ever tried copying a large movie file to your USB drive and suddenly got hit with the dreaded message:</p><p><strong>“File is too large for the destination file system.”</strong></p><p>It doesn’t matter that your USB stick has <em>plenty</em> of space — the file just refuses to move.<br> Or maybe your SD card works in your camera but magically stops working on your laptop.<br> Or your external hard drive is readable on Windows, but your friend’s Mac won’t even acknowledge it exists.</p><p>We run into these problems all the time, yet most people never realize the real reason behind them:</p><p><strong>Your storage device speaks a language — a file system — and not all devices speak the same one.</strong></p><p>Whenever you save a photo, install a game, record a video, or drag a file to a USB drive, your device isn’t simply “putting it somewhere.” It’s organizing it in a structured, rule-based system so it can find that data later.<br> That invisible system — the thing that decides how your drive stores and retrieves information — is called a <strong>file system</strong>.</p><p>And in the world of everyday devices, three file systems dominate:</p><ul><li><strong>FAT32</strong></li><li><strong>exFAT</strong></li><li><strong>NTFS</strong></li></ul><p>They look similar, but they behave very differently.<br> Choose the wrong one, and your files won’t copy, your drive won’t open, or your 4K video suddenly won’t fit.</p><p>Let’s make this simple — and finally explain FAT32, exFAT, and NTFS in a way anyone can understand.</p><h4>What Exactly Is a File System? (In Simple Terms)</h4><p>A file system is like a <strong>digital librarian</strong>.<br> It keeps track of where every file goes, what it’s called, how big it is, and what folder it belongs to.</p><p>Without a file system?</p><p>Your storage device would be a pile of meaningless bits — impossible to search or retrieve.<br> Every phone, camera, tablet, PC, and flash drive uses a file system to stay organized.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/538/1*8fSe7arxfppHYzLYd_Y2og.png" /></figure><p>Windows devices typically offer three options:</p><ul><li><strong>FAT32</strong> — old but extremely compatible</li><li><strong>exFAT</strong> — newer, faster, designed for modern storage</li><li><strong>NTFS</strong> — advanced, secure, used in all Windows installations</li></ul><p>Let’s break each one down — with the real pros, cons, and reasons they fail.</p><h4><strong>FAT32 — The Old King of Compatibility</strong></h4><p>FAT32 has been around since the 90s, and despite its age, it still dominates USB sticks and SD cards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/423/1*SpOciiWtGWterbQQjqNvCg.png" /></figure><p><strong>✔ Why It’s Still Popular</strong></p><ul><li>Works on <strong>almost every device worldwide</strong></li><li>Supported by Windows, macOS, Linux, Android, cameras, TVs, game consoles — everything</li><li>Lightweight and fast</li><li>Perfect for small removable drives</li></ul><p>This is why you can plug a FAT32 USB drive into literally anything and it “just works.”</p><p><strong>✘ The Big Catch</strong></p><p>FAT32 comes with <strong>two deal-breakers</strong>:</p><ol><li><strong>It can’t store a file larger than 4 GB.</strong><br> Not even a single byte more.</li><li><strong>Partitions must be under 8 TB.</strong></li></ol><p>Those 4K video files?<br> Those large game installers?<br> Those 10 GB backups?</p><p>FAT32 simply can’t handle them.</p><p><strong>Best for:</strong></p><ul><li>USB sticks used everywhere</li><li>SD cards up to 32 GB</li><li>Devices that require old standards (cars, TVs, cameras)</li></ul><p>If compatibility is your priority and your files are small, FAT32 is still a champ.</p><h4>exFAT — FAT32 Without the Annoying Limits</h4><p>exFAT was introduced by Microsoft in 2006 specifically to replace FAT32 for flash storage.</p><p>It’s essentially FAT32’s smarter, stronger, modern sibling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/407/1*_SuOYhlaUk8659BJskFucw.png" /></figure><p><strong>✔ Why People Love exFAT</strong></p><ul><li><strong>No 4 GB file size limit</strong></li><li><strong>No realistic partition size limit</strong></li><li>Works on Windows, macOS, and most modern devices</li><li>Lightweight and fast</li><li>Ideal for SDXC (64GB+) cards and external SSDs</li></ul><p>If FAT32 is a universal language, exFAT is a fluent multilingual one.</p><p><strong>✘ What exFAT Struggles With</strong></p><ul><li>Not supported by some older devices</li><li>No journaling (less resistant to corruption)</li><li>Not built for operating systems or system drives</li></ul><p><strong>Best for:</strong></p><ul><li>Flash drives</li><li>External SSDs</li><li>SD cards larger than 32 GB</li><li>Drives shared between Windows and macOS</li><li>Large files like 4K/8K videos, backups, and game files</li></ul><p>If you’re formatting a modern external drive, <strong>exFAT is usually the best option.</strong></p><h4>NTFS — The Powerful Workhorse of Windows</h4><p>NTFS is Windows’ main file system — used for every system drive, program drive, and internal SSD/HDD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*SDq07ZELkbg0uopwGXJxuA.png" /></figure><p>It is loaded with modern features.</p><p><strong>✔ Why NTFS Is the Most Advanced</strong></p><ul><li>No file size limits</li><li>No partition size limits</li><li>Built-in <strong>security permissions</strong></li><li><strong>File encryption</strong> (EFS)</li><li><strong>Journaling</strong> — protects data from corruption</li><li>Compression, quotas, hard links, and more</li></ul><p>NTFS is designed for <strong>robustness</strong>, not compatibility.</p><p><strong>✘ Where NTFS Falls Short</strong></p><ul><li>macOS can read but <strong>not write</strong> to NTFS without extra tools</li><li>Not supported by many cameras, TVs, consoles</li><li>Slightly slower for USB flash drives</li></ul><p><strong>Best for:</strong></p><ul><li>Windows system drives</li><li>Internal HDDs/SSDs</li><li>Drives storing installed programs</li><li>Any environment where data integrity matters</li></ul><p>If it’s inside your PC and running Windows, NTFS is the only logical choice.</p><p><strong>⭐ So Which File System Should You Use?</strong></p><p>Here’s the answer, simplified:</p><p><strong>✔ Use FAT32 if:</strong></p><p>You need maximum compatibility and your files are under 4GB.</p><p><strong>✔ Use exFAT if:</strong></p><p>You’re using a flash drive, SD card, or external SSD with big files.</p><p><strong>✔ Use NTFS if:</strong></p><p>You’re formatting an internal Windows drive or need top-tier security.</p><h4>Final Thoughts</h4><p>File systems are one of those invisible technologies we never think about — until something breaks.</p><p>Once you understand how FAT32, exFAT, and NTFS actually work, you’ll never choose the wrong format again.<br> No more copy errors.<br> No more unreadable drives.<br> No more “file too large” headaches.</p><p>Just smooth, predictable storage that works the way <em>you</em> expect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa3dd18ed3f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AMD vs ARM — The Architecture War Powering Our Digital Lives]]></title>
            <link>https://medium.com/@chirangidodiya/amd-vs-arm-the-architecture-war-powering-our-digital-lives-8f040837d5b4?source=rss-f1538904b072------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f040837d5b4</guid>
            <dc:creator><![CDATA[Chirangi Dodiya]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 11:57:50 GMT</pubDate>
            <atom:updated>2025-12-03T11:57:50.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>AMD vs ARM — The Architecture War Powering Our Digital Lives</h3><p><a href="https://medium.com/u/87ba6554136e">Rey Patel</a> <a href="https://medium.com/u/49f68f75c58">Amish Patel</a></p><p>From smartphones to supercomputers, the digital world runs on two major processor families: <strong>AMD’s x86 architecture</strong> and <strong>ARM’s RISC-based architecture</strong>.<br>Although both drive modern computing, they follow <strong>very different design philosophies</strong> — one prioritizes raw performance, the other power efficiency.</p><p>This article explains <strong>how AMD and ARM work</strong>, where they are used, and why both matter in today’s technology ecosystem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*l4hcL0Oco98yj8-E_yc1pw.png" /></figure><h4><strong>1. What Is AMD? Power-Focused x86 Architecture</strong></h4><p><strong>AMD (Advanced Micro Devices)</strong> is a leading manufacturer of high-performance CPUs and GPUs. AMD processors use the <strong>x86 / x86–64 architecture</strong>, a CISC (Complex Instruction Set Computing) design known for backward compatibility and strong performance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*JKcXZ8Hs5acd_7Zix2En6Q.png" /></figure><p><strong>Key Characteristics</strong></p><ul><li><strong>Architecture</strong>: x86 / x86–64 (CISC)</li><li><strong>Products</strong>: Ryzen CPUs, Radeon GPUs, EPYC server CPUs</li></ul><p><strong>Strengths</strong>:</p><ul><li>Excellent performance (single &amp; multi-core)</li><li>Broad software compatibility (Windows, Linux, most desktop apps)</li><li>Ideal for high-end desktops, gaming, servers</li></ul><p><strong>Use Cases</strong>:</p><ul><li>PCs &amp; laptops</li><li>Workstations</li><li>Servers &amp; cloud computing</li><li>Gaming systems</li></ul><p><strong>Why AMD excels</strong></p><p>Modern AMD architectures (like <strong>Zen 3 and Zen 4</strong>) deliver:</p><ul><li>High clock speeds</li><li>Strong multi-threading</li><li>Competitive perf-per-watt</li><li>Large core counts</li></ul><p>This makes AMD a great fit for workloads that demand <strong>raw computational power</strong>.</p><h4>2. What Is ARM? Efficiency-Focused RISC Architecture</h4><p><strong>ARM Holdings</strong> does <em>not</em> manufacture chips — it <strong>designs</strong> the ARM architecture and licenses it to companies like Apple, Qualcomm, Samsung, MediaTek, and many others.</p><p>ARM uses a <strong>RISC (Reduced Instruction Set Computer)</strong> architecture, emphasizing simplicity, lower power consumption, and high efficiency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*bwlQNhqnb93zYxLtpo9gGg.png" /></figure><p><strong>Key Characteristics</strong></p><ul><li><strong>Architecture</strong>: ARM / ARM64 (RISC)</li><li><strong>Products</strong>: CPU designs licensed to other manufacturers (e.g., Apple M-series, Snapdragon)</li></ul><p><strong>Strengths</strong>:</p><ul><li>Excellent power efficiency</li><li>Highly integrated SoC designs</li><li>Ideal for mobile and embedded systems</li></ul><p><strong>Use Cases</strong>:</p><ul><li>Smartphones</li><li>Tablets</li><li>IoT devices</li><li>Embedded systems</li><li>Increasingly in servers &amp; laptops</li></ul><p><strong>Why ARM excels</strong></p><p>ARM’s focus on minimalism and efficiency allows:</p><ul><li>Lower heat generation</li><li>Longer battery life</li><li>Compact SoC systems integrating CPU, GPU, NPU, modem, and more</li></ul><p>This is why ARM dominates the <strong>mobile world</strong> and powers devices like the iPhone, iPad, and most Android phones.</p><h4>3. AMD vs ARM: Key Differences at a Glance</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*mssTwqERxZ66otqxE97tZA.png" /></figure><h4>4. How AMD and ARM CPUs Work in Real Life</h4><p>💻 <strong>In Laptops &amp; Desktops</strong></p><ul><li><strong>AMD:</strong> Delivers powerful performance for gaming, video editing, 3D rendering, and multitasking.</li><li><strong>ARM:</strong> Apple’s M-series leads with long battery life + great performance through tight hardware–software integration<strong>.</strong></li></ul><p><strong>📱 In Smartphones</strong></p><ul><li>Nearly all smartphones run ARM-based SoCs because of:</li><li>Efficiency</li><li>Integrated features</li><li>Low heat</li></ul><p><strong>☁️ In Cloud &amp; Servers</strong></p><ul><li><strong>AMD EPYC:</strong> High core counts, strong server performance.</li><li><strong>ARM (AWS Graviton / Ampere):</strong> Lower cost and energy use for cloud-scale workloads.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/432/1*ivLtFICzLHTHoyfXjTpPXQ.png" /></figure><h4><strong>5. Why Both Matter in the Future</strong></h4><p><strong>ARM is rising</strong></p><ul><li>Apple switched all Macs from Intel to ARM</li><li>Cloud providers (AWS, Google, Microsoft) deploy ARM servers</li><li>ARM cores are becoming more powerful every year</li></ul><p><strong>AMD is evolving</strong></p><ul><li>Continues to dominate desktops and workstations</li><li>Increasing efficiency of x86 CPUs</li><li>Strong competition in the server market</li></ul><p>Both ecosystems are expanding — the future will likely see <strong>coexistence</strong>, not replacement.</p><h4>Conclusion :</h4><p><strong>AMD and ARM represent two different philosophies of computing:</strong></p><ul><li><strong>AMD (x86)</strong><br> Designed for <em>maximum performance</em> and <em>broad compatibility</em>. Ideal for PCs, gaming, servers, and heavy workloads.</li><li><strong>ARM (RISC)</strong><br> Built for <em>power efficiency</em> and <em>integration</em>. Ideal for smartphones, tablets, IoT, and portable devices — and now rising in laptops and servers.</li></ul><p><strong>Neither is “better” overall — the best choice depends on your device, workload, and priorities.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f040837d5b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>