<?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 GrayhatWarfare on Medium]]></title>
        <description><![CDATA[Stories by GrayhatWarfare on Medium]]></description>
        <link>https://medium.com/@grayhatwarfare?source=rss-3ca2d46d1b94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*k18u1gLTFUF0HBFg</url>
            <title>Stories by GrayhatWarfare on Medium</title>
            <link>https://medium.com/@grayhatwarfare?source=rss-3ca2d46d1b94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 15:12:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@grayhatwarfare/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[Introducing Public Git: Search Public Repositories for Exposed Secrets]]></title>
            <link>https://grayhatwarfare.medium.com/introducing-public-git-search-public-repositories-for-exposed-secrets-38d4f39b6f7e?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d4f39b6f7e</guid>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Sun, 18 Oct 2026 14:37:35 GMT</pubDate>
            <atom:updated>2026-10-18T14:47:29.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LYpAhqKe57JzcdCe4PA7HA.png" /></figure><h3>Introduction</h3><p>Introducing Public Git, GrayhatWarfare’s new tool for finding exposed secrets and potentially sensitive files in public Git repositories, including:</p><ul><li>Credentials and passwords</li><li>API tokens</li><li>Private keys</li><li>Database files and dumps</li><li>Configuration files for a wide range of applications</li><li>High-entropy strings that may be passwords or other secrets</li></ul><h3>Indexed Files and Search Filters</h3><p>We discover publicly accessible repositories on GitHub, GitLab, and Bitbucket, then clone and scan them for potentially sensitive files. Given the volume of files, we index only those flagged by our detection rules. We exclude forks of open-source projects that contain no new commits.</p><h3>How We Identify Files</h3><p>We identify potentially sensitive files by cloning public repositories and scanning them with open-source secret-detection tools. These tools use rules to flag potential credentials, API keys, and other sensitive data based on file contents, filenames, and paths. These tools use rules based primarily on two methods:</p><ul><li><strong>Matching file contents</strong>, such as private key headers (-----BEGIN RSA PRIVATE KEY-----) or database connection strings (mongodb+srv://user:password@host).</li><li><strong>Matching filenames</strong> associated with potentially sensitive data, such as settings.php.</li></ul><p>We tag each matching file with the rules that identified it. We also scan commit history, allowing you to find deleted files and secrets that are no longer present in the latest version of a file.</p><p>For each file that matches a rule, we store:</p><ul><li>Filename</li><li>File extension</li><li>Size</li><li>Contents, limited to the first 500 lines</li><li>Tags identifying the matching rules</li><li>A copy of the text that matched the rule, where applicable</li><li>The version of the file in which the match was found</li></ul><h3>Handling False Positives</h3><p>We have reviewed the results repeatedly to reduce false positives while retaining potentially useful findings. We also include files with names commonly associated with configuration data, such as settings.php, even when no specific secret is detected. Searching the indexed contents helps users investigate these files and filter out irrelevant results.</p><p>A rule match indicates potentially sensitive data; it does not necessarily mean a file contains an exposed secret.</p><h3>Coverage</h3><p>As of September 15, 2026, the index includes more than:</p><ul><li>62,259,443 repositories</li><li>151,952,454 potentially sensitive files</li><li>25,955,956 unique user email addresses across 3,251,891 domains</li></ul><h3>Search and Sorting</h3><p>You can search for files using the following filters:</p><ul><li>Filename</li><li>Tag (the rule that matched)</li><li>File contents (search covers only the first 500 lines)</li></ul><p>You can sort matching files by:</p><ul><li>File size</li><li>Date the file was last modified</li><li>Date the file was created</li><li>Date the file was discovered</li></ul><h3>Contributor Search</h3><p>We also index publicly available contributor information, including usernames and email addresses. You can:</p><ul><li>Search for email addresses</li><li>Search for email domains</li><li>Find committers associated with a specific domain</li><li>Find repositories a specific committer has contributed to</li></ul><h3>Explore Public Git</h3><p>Public Git is our new monitoring tool and a valuable addition to your security toolkit, extending GrayhatWarfare’s search capabilities to public Git repositories. By bringing indexed files, commit history, and contributor information together, it helps you gain a clearer view of your organization’s public footprint. Its API lets you integrate Public Git into your ongoing monitoring workflow. We’re excited to share it with you and hear how it fits into your workflow. Explore Public Git on <a href="https://git.grayhatwarfare.com/">https://git.grayhatwarfare.com/</a>, and let us know what you think.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d4f39b6f7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Early Access Buckets Stream]]></title>
            <link>https://grayhatwarfare.medium.com/early-access-buckets-stream-8990613b5092?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/8990613b5092</guid>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Sat, 25 May 2024 14:57:07 GMT</pubDate>
            <atom:updated>2024-05-25T14:57:07.793Z</atom:updated>
            <content:encoded><![CDATA[<p>We are excited to announce our latest product called Early Access Buckets Stream. This product allows you to peek into our internal databases between releases and search for newly found open buckets and see locked but valid ones. You can find the product here <a href="https://buckets.grayhatwarfare.com/buckets-stream.">https://buckets.grayhatwarfare.com/buckets-stream.</a></p><p>Early Access Buckets Stream is the first of our Add-ons, and it works with credits that you can purchase at any point. We have given some free credits to every one of you that has made at least one payment, and some credits are gifted with each renewal of Enterprise subscriptions. Filtering is based on user defined keywords, and the first 5 ones are free for life as long as the Add-on is active.</p><p>For all details check out the documentation <a href="https://buckets.grayhatwarfare.com/buckets-stream/docs">https://buckets.grayhatwarfare.com/buckets-stream/docs</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8990613b5092" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Organize Searches & get notified for new results for grayhatwarfare.com]]></title>
            <link>https://grayhatwarfare.medium.com/organize-searches-get-notified-for-new-results-for-grayhatwarfare-com-1526020996c0?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/1526020996c0</guid>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Sun, 08 Oct 2023 13:29:41 GMT</pubDate>
            <atom:updated>2023-10-08T13:29:41.346Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*zwikyTMdk1sSHo2TwfhPQw.png" /></figure><p>Numerous users have requested automated notifications for new query results upon each data release. To meet this need and enhance query organization, we’ve introduced a feature called “Saved Searches.”</p><p>Refining your search query to accurately track your assets is crucial. Our new feature lets you save these queries and receive real-time notifications, enabling you to address potential leaks promptly.</p><p>With Saved Searches, you can:</p><ul><li>Preserve the specifics of a search query for quick future access.</li><li>Opt in for email notifications when new files are added to your search results.</li><li>View the number of new results since last release</li></ul><p>Creating a saved search is as easy as clicking the Save &amp; Notify button in the search results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*GJifod0AIt-FZNeVDcI48g.png" /></figure><p>You can also manage the Saved Searches here: <a href="https://buckets.grayhatwarfare.com/user/searches/bucket_files">https://buckets.grayhatwarfare.com/user/searches/bucket_files</a> (Search Files — Saved Searches in the menu)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*p7h4o7qtWd3Uj_b__dfJCg.png" /></figure><p>For easy access you can click the Saved Searches button in the search results:</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*h-cUpIRoU7qQqliKIT9O_Q.png" /></figure><p>The new functionality is available for premium users for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1526020996c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to search URLs exposed by Shortener services]]></title>
            <link>https://grayhatwarfare.medium.com/how-to-search-urls-exposed-by-shortener-services-f68e199cd560?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/f68e199cd560</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[leak-detection]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[url-shorteners]]></category>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Sun, 07 Mar 2021 16:26:50 GMT</pubDate>
            <atom:updated>2021-03-08T10:57:41.621Z</atom:updated>
            <content:encoded><![CDATA[<p>Almost two years after the release of our <a href="https://grayhatwarfare.medium.com/how-to-search-for-open-amazon-s3-buckets-and-their-contents-https-buckets-grayhatwarfare-com-577b7b437e01">Buckets Search</a> tool, we are happy to announce the release of <a href="https://shorteners.grayhatwarfare.com/">http://shorteners.grayhatwarfare.com</a>, the second tool in the GrayhatWarfare arsenal, that allows you to search exposed <a href="https://en.wikipedia.org/wiki/URL_shortening">Shortened Urls</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mLNj9qKL4EVJS2kU0YVNdA.png" /><figcaption>shorteners.grayhatwarfare.com - Shortened URLs search engine</figcaption></figure><p>TinyURL, bit.ly, and other similar services allow long URLs to be converted to smaller ones hosted on their service; the small URL is visited by a consumer and their web browser is redirected to the long URL. Common use-case is Twitter where the number of characters is limited but also emails and DMs.</p><p>There is always the risk, that a Shortener service, for whatever reason might stop delivering urls. Teams like <a href="https://archive.org/details/301works">301Work</a> and <a href="https://wiki.archiveteam.org/index.php/URLTeam">URLTeam</a> are trying to mitigate the risk. URLTeam is periodically visiting the urls and archiving the results. The design of Shortener services made this process easier, because they use the minimum characters to accommodate the number of links they host, meaning the number of possible urls is really low and can be brute forced.</p><p>There are some security risks associated with Shortener services. First, you never know where you are redirected when you click a shortened url — there could be a malicious url on the other end. Second Shortener services can track users and their behavior. Also there are other risks when shortening urls that should remain private. Those include things like:</p><ul><li>Links to shared/unlocked files in Cloud services (Dropbox, Google Drive, OneDrive). OneDrive in particular used to generate short URLs for documents and folders using the 1drv.ms domain. This is a “branded short domain” operated by Bitly and uses the same tokens as bit.ly. Searching by any cloud service domain (dropbox.com, drive.google.com), reveals a lot of downloadable files. This reveals files and directories and some of them even have write access.</li><li>Links to locations (Google Maps or other maps/location services), which often contain personal information, or routes to sensitive areas.</li><li>Links to internal/hidden but accessible urls with sensitive information. Those could be, Admin panels, Hidden directories, or private documents</li><li>Accidentally public trello.com boards or other similar services.</li></ul><p>It’s a common practice for pentesters to search for sensitive urls, or gather information for a domain name, through Shortened urls. <a href="https://twitter.com/utkusen">Utku Sen</a> did an excellent job creating <a href="https://github.com/utkusen/urlhunter">https://github.com/utkusen/urlhunter</a>, which is the most known tool that tackles the problem of searching through the urls. However there are some limitations:</p><ul><li>The tool needs to download the files from Archive.org before it’s operational. This process is rather slow because Archive.org limits the bandwidth.</li><li>The user must have 500GB of free disk space available to save all data.</li><li>Filtering the results is relatively slow.</li><li>It’s a command line tool which might be intimidating for some people.</li><li>Most of the urls are inactive (404 links, expired domains etc).</li></ul><p>In order to improve the search experience we:</p><ul><li>Removed urls from expired domains.</li><li>Removed all non existing urls (404)</li><li>Removed urls from parked domains, that falsely respond with 200 to all requests.</li><li>Deduced content-type from the contents of all urls and guessed the file extension.</li></ul><p>The functionality we offer is:</p><ul><li>Filter by keywords</li><li>Filter by extension, calculated from the contents of the url and not its url extension.</li><li>Allow to filter by domain and keywords.</li><li>Sort by size when known.</li><li>Sort by discovery date, based on URLTeam release date.</li></ul><p>Our primary goal for the first release was to clean up as much junk as possible and create a robust filtering mechanism while keeping the tool as minimal as possible. As always we want your input on what functionality you want to see in the tool. <a href="https://shorteners.grayhatwarfare.com/">shorteners.grayhatwarfare.com</a> is the second tool we released and we have a lot more on the way.</p><p>Follow us on twitter to get announcements for new tools and updates first:</p><h3>JavaScript is not available.</h3><p>We are happy to announce the release of https://t.co/90RSfy44AH, the second tool in the @grayhatwarfare arsenal, that allows you to search exposed Shortened URLs.More info here: https://t.co/WMWnApJgQg</p><p>Thanks for your support, it makes delivering new tools feasible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f68e199cd560" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Open Azure blobs search on grayhatwarfare.com and other updates]]></title>
            <link>https://grayhatwarfare.medium.com/open-azure-blobs-search-on-grayhatwarfare-com-and-other-updates-89f709b10412?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/89f709b10412</guid>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[azure-blob]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Sun, 22 Nov 2020 20:07:59 GMT</pubDate>
            <atom:updated>2020-11-22T20:19:00.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uQTAwBZlk0BnaXcn.png" /></figure><p>We are <a href="https://buckets.grayhatwarfare.com/">grayhatwarfare.com</a> — a group of individuals working on displaying various ways that common information security practices fail. Our first — and only so far — released project has been open s3 buckets search described <a href="https://medium.com/@grayhatwarfare/how-to-search-for-open-amazon-s3-buckets-and-their-contents-https-buckets-grayhatwarfare-com-577b7b437e01">here</a>. We have received many feature requests and after 2 and a half years we have implemented them all!</p><p>Although we are working on many projects, non of them is quite production ready yet. So wanting to release something, we have decided to add Open Azure blobs in our platform which was roughly prepared some time ago. We have added the final touches and we are happy to announce that it is released!</p><p>As of now, we have 17552 open Azure blobs and over 300 Million files. The format of the azure blobs is a little bit different. Each Azure Blob consists of an account name and a container name in the in the form of https://{accountName}.blob.core.windows.net/{containerName}. However we have merge it in such a way so that the inclusion of Azure Blobs will be seamless with the existing functionality of the website with minimal changes. Also we will regularly update the contents of Azure Blobs and add new ones — just like s3 buckets.</p><p>In other news we have added the Last Modified information for each file and you can now sort your results with Modified Time:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*1gpzfi3S3PgxrwbO-A49qQ.png" /></figure><p>Also we have rescanned all the open s3 buckets and we have added ~25000 more. We now have 318 000 buckets and over 4 Billion files to for you to search.</p><p>You can check out the new version here: <a href="https://buckets.grayhatwarfare.com/buckets">https://buckets.grayhatwarfare.com/buckets</a></p><p>In the immediate future we are going to release Google Cloud storage buckets and we are going to release a new and interesting tool that allows pentesters to scan for a very common and rarely known or exploited vulnerability</p><p>Follow us on twitter for more news and updates.</p><h3></h3><p>Open Azure blobs search on grayhatwarfare and other updateshttps://t.co/7bviHqkGcQ</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89f709b10412" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The real 10x developer]]></title>
            <link>https://grayhatwarfare.medium.com/the-real-10x-developer-63cb0a44e273?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/63cb0a44e273</guid>
            <category><![CDATA[10x-engineer]]></category>
            <category><![CDATA[hacker]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Sun, 31 May 2020 21:29:23 GMT</pubDate>
            <atom:updated>2021-03-12T15:31:21.705Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*67g9_7kQfjQmFvOmRF2Giw.jpeg" /></figure><p>10x developer is defined as the developer that is 10 times more productive than the average developer. Whether these developers exist is a matter of debate. Usually, people will tell you that 10x developers don’t exist. Most of them are trying to tell you what this article will try to explain.</p><p>10x programmers, or even 100x programmers, do, in fact, exist. But real 10x programmers are not the ones who “can perform a task 10 times faster than the average programmer”. Don’t get me wrong, there are people who can implement something extremely quickly, much faster than the average programmer. Does that, however, make these individuals 10x more valuable? I would argue not. And most of the time, those individuals do more harm than good. <strong>Real gains in software development are usually not measured in implementation times, but in future maintenance man-hours. </strong>The right person in the right position can save tens of thousands of man-hours for a company, essentially being 10x or 100x more valuable than others. Software engineering, because of its chaotic nature, really allows for such large gains, or losses, when practiced in the wrong way. Small mistakes have a tendency to pile up in huge technical dept over time.</p><p>So, why is completing a task very fast harmful? Writing solid software is hard. Systems are usually chaotic; maintenance is very hard, and there are a lot of pitfalls. Good programmers know this. When a programmer makes something work as described, he/she has finished about a third of the job. Then comes the hard part. That is, hold the task, until you are certain that you can answer yes to the following questions:</p><ol><li>Is the task completely finished?</li><li>If I deploy this, am I reasonably sure that I didn’t break anything else?</li><li>Is the way I implemented the feature easy to maintain or change in the future?</li><li>Does my solution scale reasonably well?</li><li>Does my implementation deviate from the existing architecture?</li></ol><p>Managers, salesmen and rookie “10x programmers” only care about the first question. Real 10xers know that the only constant is change. Somebody will ask you to change or add to the existing feature. Your first priority must be to make your future self’s life easier. That means a few things:</p><ul><li>Writing unit/system/integration tests. Contrary the widespread misconception that tests are for testing your features, this is not true. Tests are used mostly for regression. You create tests so that you can answer the question: “What did I break implementing this?”</li><li>Do not deviate from the system’s architecture. Kent Beck said, “For each desired change, make the change easy (warning: this may be hard), then make the easy change.” If you see that, to support the new feature, you have many special cases, multiple ifs, forks in logic in various places; that means that you have to re-evaluate your architecture. Break things down, refactor, make the feature feel natural and easy on your framework, then actually re-implement it. Something really hard to pull off when you don’t have any tests to begin with.</li><li>Do the math, do some tests. Does this SQL query scale? What will happen when we are in production and we have several million lines in x and y table? Often “easy”, straightforward solutions do not scale well. Do I need to create indexes, or secondary data structures, to efficiently support my queries? If you have to re-implement everything in six months and on top, migrate the old data, you are not very valuable, are you?</li><li>Write clean and simple code. If you have trouble while developing the feature, when everything is fresh in your brain, imagine maintaining it in two years.</li></ul><p>Thinking like this will certainly make your development slower. Development of the feature will most likely take two or three times longer, if implemented correctly. But if everything goes well, you won’t have to touch it again, and modifying it will be a lot faster and more straightforward. On the other hand, a hastily implemented piece of code can lead to thousands of hours of future maintenance, QA testing, server crashes, debugging, etc.</p><p>What is making things even worse is that managers, unless they come from a technical background of a sufficient level, cannot understand what all the fuss is about. They will pressure good programmers that take longer to implement features but deliver good code, and they will praise the ignorant programmer, who delivers quickly, for their “work ethic”, especially when they will rush to fix the myriad of inevitable production errors that will occur, mostly because the feature was not implemented correctly in the first place. Technical dept is not only a thing, but if not kept in check, can destroy a company. This is the first thing I look for when considering a new job. Will my boss understand when I explain a technical issue to him/her?</p><p>And all of the above are what you achieve as a developer, in the scope of a simple task. People in better positions, like Tech leads and other positions that have more influence on the company, can use the same principles to simplify procedures with code and automated systems that will be extremely beneficial in the future. Think differently, outside the box. You can eliminate entire classes of bugs by enforcing a specific architecture. If the rise of Devops taught us a lesson, it is that you can free the hands of many people that are forced doing trivial and boring tasks and avoid human errors by writing code and using tools to automatic a procedure. Many times, the only thing you have to do is just sit down and think what you can do to improve your situation and not take things for granted. That is why I think that most hackathons, programming challenges and “how do you know this or that” interview questions are pointless. They do not show the true qualities that define a good software engineer.</p><p>The Ultimate example of a truly valuable coder is Misko Hevery, the co-creator of AngularJs. Essentially, he and Adam Abrons invented AngularJS, and Hevery rewrote the Google feedback application in just 1500 lines of code, as opposed to the original, which was close to 17.000. These guys not <a href="https://twitter.com/newsycombinator/status/1266474792045154304">https://twitter.com/newsycombinator/status/1266474792045154304</a>only created AngularJs and Angular, they first introduced the principles that all the modern Javascript frameworks rely on. Before, Angular front-end development was a tedious and difficult job. By introducing Angular, they showed everybody that, even though we didn’t realize it for many years, there is an easier way of doing things. They believed that there was a better way to do things, and they proceeded to invent it. Imagine the millions of man-hours these guys saved for all front-end engineers worldwide.</p><p>And that, for me, is the true definition of a hacker:</p><p>Most people see what <em>is</em>, hackers see what <em>can be</em>.</p><h3>grayhatwarfare on Twitter</h3><p>Help spread the word, brothers and sisters ! The real 10x engineer: https://t.co/PIqtknjarY</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63cb0a44e273" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to search for Open Amazon s3 Buckets and their contents — https://buckets.grayhatwarfare.com]]></title>
            <link>https://grayhatwarfare.medium.com/how-to-search-for-open-amazon-s3-buckets-and-their-contents-https-buckets-grayhatwarfare-com-577b7b437e01?source=rss-3ca2d46d1b94------2</link>
            <guid isPermaLink="false">https://medium.com/p/577b7b437e01</guid>
            <category><![CDATA[pentest]]></category>
            <category><![CDATA[data-breach]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[GrayhatWarfare]]></dc:creator>
            <pubDate>Fri, 06 Jul 2018 20:42:42 GMT</pubDate>
            <atom:updated>2024-05-11T11:01:28.684Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*dTKoXXin7iu2wHW2gCgP0Q.jpeg" /></figure><h3>Intro</h3><p>TLTR — This is the story of why I created <a href="https://buckets.grayhatwarfare.com/">https://buckets.grayhatwarfare.com/</a> a free tool that lists open s3 buckets and helps you search for interesting files.</p><p>For an intro on what Amazon open buckets is you can read this <a href="https://blog.rapid7.com/2013/03/27/open-s3-buckets/">https://blog.rapid7.com/2013/03/27/open-s3-buckets/</a> . In essence, many files are publicly accessible, some by design, some by incompetence of the admins. These files sometimes include very sensitive data. <a href="https://github.com/nagwww/s3-leaks">https://github.com/nagwww/s3-leaks</a> has a list of the biggest leaks recorded.</p><p>Since this was exposed, many projects have been created that can enumerate s3 buckets:</p><ul><li><a href="https://github.com/jordanpotti/AWSBucketDump">https://github.com/jordanpotti/AWSBucketDump</a> — takes an argument a wordlist and can check if buckets with that name exist. Also it can download the files from the first page of results.</li><li><a href="https://buckhacker.com/">https://buckhacker.com/</a> — The original buckhacker as I am informed by him personally. Medium buckethacker and twitter buckethacker is the real, below is copycat.</li><li><a href="https://www.thebuckhacker.com/">https://www.thebuckhacker.com/</a> — Search engine for some buckets. It include (according to their posts) ~100 000 buckets, and they index the first page of each — copy of buckhacker.com</li><li><a href="https://github.com/sa7mon/S3Scanner">https://github.com/sa7mon/S3Scanner</a> —</li><li><a href="https://github.com/kromtech/s3-inspector">https://github.com/kromtech/s3-inspector</a> — Uses amazon keys to check if some of you buckets are open.</li></ul><p>All these tools/projects have some common problems:</p><ul><li>The real problem (at least for me) is where to find the list to bruteforce for buckets, not actually doing the bruteforce.</li><li>All tools/projects only scan the first page for results.</li><li>thebuckhacker.com includes uninteresting files and useful results tend to be lost in the noise. Also the first 1000 results of each bucket is fairly limited.</li><li>The process is slow and not productive. Its not very useful for pentesters to run a tool to run for days, save the exports somewhere and then grep them whenever they want to search for something. What is better is a useful tool in front of a large database.</li></ul><h3>buckets.grayhatwarfare.com</h3><p>And like that I have created <a href="http://buckets.grayhatwarfare.com/">https://buckets.grayhatwarfare.com/</a>. I took ideas from the tools/projects above, but I mostly rewrote them myself, and ran them on my infrastructure. The project’s features are:</p><ul><li>It is a searchable database of open buckets.</li><li>I have included up to million results of each bucket. (In the future might be more).</li><li>I removed all uninteresting (in my opinion) files like images. Most images names are auto-generated.</li><li>I currently have ~180.000.000 files. In I included all images that number would go up to a few billion, which is a completely different system.</li><li>As of today, 70 000 buckets are listed (not all of them have “interesting” files)</li><li>Full text search with binary logic (can search for keywords and also stopwords)</li><li>I include the list of the buckets.</li><li>The user can browse the contents of the bucket.</li><li>Excluded a lot of other things that are not interesting like cloudwatch logs.</li><li>Found a solution the problem on how to generate possible names for buckets. My process reviles some hundreds new buckets per day.</li><li>I have mostly automated the process.</li></ul><h3>Why create this ?</h3><p>Although I consider my self a software engineer, I was always fascinated with security. I have on many occasions created multiple tools that mass scan for vulnerabilities, just to see if is possible. Although I created the tools, I never publish anything it always felt like I was wasting my time. grayhatwarfare.com is my attempt to present some of my work, even if it is anonymous.</p><p>The project is currently free and running on servers paid by me. There are some limitations in place to protect resources, but otherwise pentesters can use this on their daily tasks.</p><h3>Whats to come in grayhatwarfare.com</h3><p>Lots of cool things, if I have the time:</p><ul><li>Subdomains pointing to expired buckets which can lead to something like this: <a href="https://www.reddit.com/r/netsec/comments/8t0pb2/how_i_hacked_applecom/">https://www.reddit.com/r/netsec/comments/8t0pb2/how_i_hacked_applecom/</a></li><li>Exposed cameras/IOT devices.</li><li>Huge resources like extremely large (actual) cracked password lists.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=577b7b437e01" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>