<?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 Arno Sontheim on Medium]]></title>
        <description><![CDATA[Stories by Arno Sontheim on Medium]]></description>
        <link>https://medium.com/@arno-sontheim?source=rss-a3ce9ca74b8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NHqRCc0zBq2Q4fbnR3em0w.jpeg</url>
            <title>Stories by Arno Sontheim on Medium</title>
            <link>https://medium.com/@arno-sontheim?source=rss-a3ce9ca74b8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:25:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arno-sontheim/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[The 10 biggest security incidents of October 2026]]></title>
            <link>https://medium.com/akrenon/the-10-biggest-security-incidents-of-october-2026-26b532a595d9?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/26b532a595d9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ai-security]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Thu, 29 Oct 2026 23:33:13 GMT</pubDate>
            <atom:updated>2026-10-29T23:33:13.035Z</atom:updated>
            <content:encoded><![CDATA[<p>October. Cybersecurity Awareness Month, at least on paper. This year the month didn’t need a hashtag, it ran its own campaign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KENU6LcU7W5aQ_zAbGHiNg.png" /></figure><p>PHP and Node.js, two runtimes that a huge part of the web sits on, both had remote code execution bugs (an attacker gets to run their own code on your server), and both were exploited within a week of the fix. A national cloud region in Japan was encrypted, in seven minutes if you believe the attackers. Microsoft and Oracle shipped the largest patch releases in their history. CISA added 32 entries to its Known Exploited Vulnerabilities catalog (KEV), the US list of bugs confirmed to be used in real attacks. And that was only 1 to 28 October. On top of it, the gateway many teams use to hold their AI keys was turned into a key stealer, and Microsoft blamed an intrusion campaign on a state actor running AI agents.</p><p>I follow MCP and agent security for a living, so I spent the month reading advisories instead of awareness posters. These are the ten events I think matter most, roughly in order of impact. All dates are 2026. When a number comes from an attacker’s note and not from the victim, I say so. The longer version, with full tables of exploited CVEs, patches, breaches and ransomware, is on akrenon.com.</p><h4><strong>1. LiteLLM shipped a credential stealer through its own pipeline</strong></h4><p>On 21 October, LiteLLM 1.107.0 went out on PyPI and Docker Hub with a credential stealer inside and a loader that pulled remote code every hour. LiteLLM is the proxy a large share of teams put between their apps and the model providers. So the machine it runs on holds exactly what the malware was after: provider keys, cloud credentials, SSH keys, browser cookies and the proxy’s own key database. The packages were live for less than two hours. Wiz counted about 49,000 downloads and saw stolen AWS credentials being tested the same afternoon.</p><p>How it happened is worth reading twice. A master key for LiteLLM’s Agent Platform was committed to a public repository on 27 May and never revoked. On 10 October an attacker used it to pull GitHub OAuth tokens that the platform had written into its logs. On 21 October the release workflow was pointed at a lookalike repository, Berri-AI instead of BerriAI, and the poisoned build came out signed and official. It was the project’s second supply chain compromise in 2026, after it had already hardened its pipeline following the first.</p><h4><strong>2. Microsoft put AI agents on the attacker’s side</strong></h4><p>On 21 October Microsoft linked the ConnectWise Cloud Backup compromise to Storm-0940, a China state-aligned group it has tracked since 2021. According to Microsoft, the group ran the campaign with ARTEX, an open-source Go framework that lets AI agents handle reconnaissance, password spraying and data theft with little human steering. Microsoft’s numbers: 2,900 sign-in attempts per minute, more than 2,250 Microsoft 365 tenants targeted with stolen application credentials, and privileged access in under three hours where it worked. ConnectWise disabled seven application identities on 17 October and took the service offline.</p><p>Two caveats I wouldn’t drop. Microsoft published no evidence that AI was used in the ConnectWise phase specifically, only the speed and scale. And the tenant count is attempts, not confirmed breaches. Still, it’s the first time a major vendor has described a state campaign as run by agents in a published attribution.</p><h4><strong>3. </strong>PHP2Shell: a leaked embargo and a root chain</h4><p>Two remote code execution bugs in PHP core that work without logging in, CVE-2026-109618 and CVE-2026-109619, leaked through a Hacker News post on 20 October. That was two days before the planned coordinated release. The PHP team shipped emergency fixes on 21 October in 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Anything older is end of life and stays vulnerable. CISA added both bugs to KEV on 26 October after researchers recorded successful attacks. A third PHP RCE, CVE-2026-115560, isn’t fixed by those releases. On 28 October Dream reported attacks that chained the two bugs with a Linux kernel flaw, CVE-2026-46300, to get root on 25 servers, three of them in a US government-affiliated network. That report is not independently confirmed. CISA added the kernel flaw to KEV the same day.</p><h4><strong>4. Node.js and the Brotli bug nobody had on their radar</strong></h4><p>Also on 21 October, Node.js shipped security releases for every supported line: 26.12.1, 24.22.1 and 22.23.4, with ten CVEs in total. The one that matters is CVE-2026-111497, an out-of-bounds write in the bundled Brotli decoder. Any Node service that decodes a hostile compressed response can be hit, and that includes fetch(), Express 5, axios and got. It went into KEV on 27 October. The same Brotli flaw is in .NET, PAN-OS and most Linux distributions, so Node is just the most visible place it showed up. Node 20 and 25 are end of life and got nothing.</p><h4><strong>5. </strong>Ransomware took down a national cloud region</h4><p>On 7 October ransomware took down East Japan Region 1 of IDCF Cloud, run by the SoftBank subsidiary IDC Frontier. 495 companies and local governments were affected. A day later the provider said data in four zones was probably gone for good and told customers to rebuild from backups they kept themselves. By 27 October it had partly walked that back: backup data could be retrieved for 206 customers, and the attackers had come in through a flaw in open-source software in the customer portal. The attackers left a note on the console claiming seven minutes to get in, 239 hypervisors, 3.6 PB encrypted and 554,153 snapshots wiped. None of that is confirmed. What is confirmed: JR East and Nissui reported knock-on disruptions, and at least one prefecture found out its backups were stored with the same provider. A snapshot inside your provider’s blast radius is not a backup.</p><h4><strong>6. The biggest Patch Tuesday ever, and Oracle a week later</strong></h4><p>On 13 October Microsoft fixed 1,411 to 1,413 CVEs, depending on who is counting. That’s more than in all of 2025. The one that mattered was CVE-2026-96951, a Windows Shell bug that bypasses Mark of the Web, the tag Windows puts on downloaded files so it can warn you before opening them. It was exploited before the patch and is the third Shell zero-day attacked this year. Oracle followed on 20 October with 1,209 CVEs, six of them at the maximum CVSS score of 10.0, in E-Business Suite, Access Manager, SOA Suite and JD Edwards.</p><p>I’d stop treating these record counts as news. This volume is the new normal. The only number worth watching is how many of those CVEs end up in KEV.</p><h4><strong>7. Next.js: two RCEs without login, and no patch for version 14</strong></h4><p>On 14 October Vercel shipped an out-of-band release that fixed two critical remote code execution bugs. CVE-2026-96889 lets an attacker run code by sending a crafted SVG to the Image Optimization API, through sharp and librsvg, on glibc Linux. The second is in the 16.x “use cache” directive and has no workaround. The fixed versions are 16.4.1 and 15.5.28. Next.js 14 and older never got a patched release; the only fix there is to upgrade sharp to 0.35.5. I mention this one in an MCP context because a lot of AI front ends and agent dashboards run on exactly this stack.</p><h4><strong>8. The edge device zero-day wave</strong></h4><p>In the first half of the month, four perimeter products were exploited before or right after a fix:</p><p><strong>Fortinet FortiMail</strong>, CVE-2026-104286: a 9.8 file write that needs no login. It was in KEV on 1 October, with the patch still weeks away.</p><p><strong>Citrix NetScaler</strong>, CVE-2026-88779: the third exploited NetScaler zero-day in two weeks. A single request crashed fully patched SAML appliances.</p><p><strong>Ivanti Connect Secure</strong>, CVE-2026-104935: an authentication bypass that needs no credentials.</p><p><strong>BeyondTrust Remote Support</strong>, CVE-2026-102764: exploited since late August by a suspected China-nexus actor, before CISA’s alert on 16 October.</p><p>Same story every year, different logos.</p><h4><strong>9. Five MCP findings in one month, all of a familiar kind</strong></h4><p>MCP, the Model Context Protocol, connects AI assistants to tools and data. This month it collected five findings:</p><p>- The official mcp-server-fetch reference server shipped a textbook SSRF, letting attackers make the server send requests on their behalf (CVE-2026-104120, 2 October).</p><p>- Langflow ran the command field from MCP server configs through bash with no allowlist (CVE-2026-105697, CVSS 9.9, 5 October). Because auto-login was on by default, exposed instances needed no credentials.</p><p>- The x64dbg MCP server exposed every debugger tool on 0.0.0.0 with no authentication (CVE-2026–107824, 9 October).</p><p>- OpenCode let a malicious remote MCP server run code on Windows during OAuth sign-in. The vendor fixed it silently, requested no CVE and said servers configured by users are outside its threat model (Pillar Security, 19 October).</p><p>- AWS API MCP Server skipped the token audience check in OAuth mode (CVE-2026-115413, 27 October).</p><p>On top of that, Pluto Security built two working malicious MCP servers, and five scanners passed both as clean.</p><p>None of these is a new type of vulnerability. It’s the same four classes, rediscovered one server at a time. To me that says the ecosystem has a testing problem, not a vulnerability problem.</p><h4><strong>10. So-net, Copenhagen, AfD</strong></h4><p>The largest confirmed breach of the month by record count: on 27 October, Sony Network Communications disclosed that its So-net member database had been breached on 19 October and the intrusion was detected four days later. About 2.6 million current and former customers were exposed (2,585,481 records across So-net and plala), plus 54,401 email passwords. The University of Copenhagen reported an intrusion into a test environment with data on about 525,000 people, including national ID numbers, and reissued PIN codes for 20,000 ID cards. In Germany, the AfD breach from September ended up in Have I Been Pwned with 345,439 email addresses. The leaked mailboxes contained voter registration data that municipalities had sent by unencrypted email.</p><h4><strong>What connects them</strong></h4><p>Not one of the ten needed a new exploit technique. The biggest incidents started inside a trust boundary: a signed release pipeline, an approved application credential, a provider’s snapshot store, an MCP server the user had configured and the vendor had declared out of scope.</p><p>The credentials that made them possible had outlived their purpose. A master key stayed valid for 136 days. OAuth tokens sat in log files because a model response contained them. And AI sped up both sides: Anthropic was among those Microsoft credited for finding the Windows Shell zero-day, and Microsoft says Storm-0940’s agents reached privileged access in under three hours per victim.</p><p>If you run an AI gateway or an agent platform, two checks this week will do more than any awareness training: what your logs actually contain, and which long-lived keys you could revoke today without anyone noticing.</p><p><strong><em>The full version of this review and sources, with tables of the key KEV additions, every patch release, the breaches and the ransomware numbers for October, is on </em></strong><a href="https://akrenon.com/research/articles/cybersecurity-october-2026/"><strong><em>akrenon.com</em></strong></a><strong><em>.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26b532a595d9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/akrenon/the-10-biggest-security-incidents-of-october-2026-26b532a595d9">The 10 biggest security incidents of October 2026</a> was originally published in <a href="https://medium.com/akrenon">AKRENON Security</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[30 Advanced Google Dork Queries for Uncovering Hidden Data and OSINT Insights]]></title>
            <link>https://osintteam.blog/30-advanced-google-dork-queries-for-uncovering-hidden-data-and-osint-insights-f397cd97e252?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f397cd97e252</guid>
            <category><![CDATA[online-privacy]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[google-dorks-list]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[osint]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Fri, 27 Sep 2024 15:06:35 GMT</pubDate>
            <atom:updated>2024-09-28T23:31:38.990Z</atom:updated>
            <content:encoded><![CDATA[<p>This list is about powerful search techniques for discovering exposed emails, passwords, confidential files, and sensitive information using advanced Google search operators. Ideal for cybersecurity experts and OSINT analysts, this guide enhances your ability to identify vulnerabilities and extract critical intelligence from public sources.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*pwCz5H0bfJy0gH0o8RSTiQ.png" /></figure><h3>1. Identifying Usernames in Online Forums or Comment Sections</h3><h4>Query:</h4><p>intext:”username123&quot; intitle:”forum” OR intitle:”comment” OR intitle:”discussion” OR inurl:”/profile/” OR inurl:”/user/” -intitle:”documentation” -filetype:pdf -filetype:docx</p><h4>Explanation:</h4><p>Looks for specific usernames in online forums or comment sections, useful for tracking user activity.</p><h3>2. Finding Leaked Password Lists</h3><h4>Query:</h4><p>intitle:”index of” (“passwords.txt” OR “leaked-passwords.csv” OR “passwords.bak” OR “secrets.txt”) -git -github -gitlab -bitbucket -intitle:”documentation”</p><h4>Explanation:</h4><p>This query helps locate directories containing password lists or leaks.</p><h3>3. Discovering Sensitive Config Files on Public Servers</h3><h4>Query:</h4><p>intitle:”index of” (“config.php” OR “wp-config.php” OR “database-config.php” OR “settings.conf” OR “appsettings.json”) AND (“database” OR “credentials”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Searches for publicly exposed configuration files, often containing database credentials or other sensitive information.</p><h3>4. Uncovering Exposed Camera Feeds</h3><h4>Query:</h4><p>intitle:”webcamXP 5&quot; OR intitle:”axis camera” OR intitle:”network camera” OR intitle:”IP camera” OR intitle:”live feed” inurl:”/view/” OR inurl:”/stream/” -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>This query identifies unsecured IP camera feeds that are publicly accessible.</p><h3>5. Searching for Publicly Available SSH Keys</h3><h4>Query:</h4><p>intitle:”index of” (“id_rsa.pub” OR “id_dsa.pub” OR “authorized_keys” OR “ssh_public_key” OR “ssh_keys”) AND (“key” OR “pub”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Finds publicly exposed SSH key files on servers, which can be crucial in securing systems.</p><h3>6. Finding Misconfigured Amazon S3 Buckets</h3><h4>Query:</h4><p>site:s3.amazonaws.com intitle:”index of” (“bucket” OR “files” OR “public” OR “documents” OR “images”) AND (“access” OR “public”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Targets open Amazon S3 buckets that may contain sensitive information or files.</p><h3>7. Locating Vulnerable Login Pages</h3><h4>Query:</h4><p>inurl:”/login.php” OR inurl:”/admin.php” OR inurl:”/signin.php” OR inurl:”/user/login” intitle:”login” OR intitle:”admin” OR intitle:”portal” OR intext:”username” AND intext:”password” -intitle:”documentation”</p><h4>Explanation:</h4><p>Identifies public login portals that might be vulnerable to brute force attacks or SQL injections.</p><h3>8. Discovering Public Network Device Configurations</h3><h4>Query:</h4><p>intitle:”index of” (“router.conf” OR “switch.conf” OR “firewall.conf” OR “network_settings” OR “device-config”) AND (“network” OR “configuration”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Searches for exposed network device configuration files, which could reveal network setup or credentials.</p><h3>9. Tracking Leaked Email Passwords on Pastebin</h3><h4>Query:</h4><p>site:pastebin.com intext:”email” AND intext:”password” OR intext:”credentials” OR intext:”login” OR intext:”user:pass” -api -key -intitle:”documentation”</p><h4>Explanation:</h4><p>Locates email and password combinations that have been leaked and shared on Pastebin.</p><h3>10. Uncovering Sensitive Government Documents</h3><h4>Query:</h4><p>site:.gov filetype:pdf OR filetype:xls OR filetype:doc intitle:”confidential” OR intitle:”sensitive” OR intitle:”restricted” OR intitle:”classified” -intitle:”documentation” -filetype:docx</p><h4>Explanation:</h4><p>Focuses on publicly accessible government files labeled as confidential or sensitive.</p><h3>11. Identifying Social Media Profiles via Public Posts</h3><h4>Query:</h4><p>site:facebook.com OR site:twitter.com OR site:instagram.com OR site:linkedin.com intext:”username” OR intext:”email@example.com” OR intext:”profile” OR intext:”contact”</p><h4>Explanation:</h4><p>Searches for specific usernames or emails within social media platforms to track public activity.</p><h3>12. Discovering Personal Data in Academic Papers</h3><h4>Query:</h4><p>site:*.edu intext:”personal information” OR intext:”sensitive data” OR intext:”private details” OR intext:”confidential” filetype:pdf OR filetype:docx OR filetype:doc -intitle:”documentation”</p><h4>Explanation:</h4><p>Identifies academic papers that may accidentally include personal data.</p><h3>13. Finding Exposed Database Backups</h3><h4>Query:</h4><p>intitle:”index of” (“backup.sql” OR “dump.sql” OR “database_backup.sql” OR “data_dump.sql” OR “db_backup.zip”) AND (“database” OR “backup”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Locates publicly available SQL database backup files, often stored without protection.</p><h3>14. Exposing Employee Credentials in Internal Reports</h3><h4>Query:</h4><p>intext:”employee credentials” OR intext:”staff passwords” OR intext:”HR records” OR intext:”login details” filetype:pdf OR filetype:doc OR filetype:xls OR filetype:docx -intitle:”documentation”</p><h4>Explanation:</h4><p>Searches for documents containing employee credentials that are unintentionally made public.</p><h3>15. Tracking Down Exposed Personal Identification Numbers</h3><h4>Query:</h4><p>intext:”SSN” OR intext:”Social Security Number” OR intext:”personal ID” OR intext:”national ID” OR intext:”identification number” filetype:pdf OR filetype:xls OR filetype:docx -intitle:”documentation”</p><h4>Explanation:</h4><p>Looks for files containing sensitive personal identification numbers, such as Social Security numbers in the U.S.</p><h3>16. Locating Internal Network Diagrams</h3><h4>Query:</h4><p>intext:”network diagram” OR intext:”network topology” OR intext:”infrastructure map” OR intext:”system architecture” filetype:pdf OR filetype:png OR filetype:jpg OR filetype:svg</p><h4>Explanation:</h4><p>Finds network diagrams and topologies that may reveal internal infrastructure layouts.</p><h3>17. Uncovering Publicly Shared Financial Spreadsheets</h3><h4>Query:</h4><p>intext:”balance sheet” OR intext:”financial statement” OR intext:”budget report” OR intext:”profit and loss” filetype:xls OR filetype:csv OR filetype:xlsx -intitle:”documentation”</p><h4>Explanation:</h4><p>Searches for exposed financial documents like balance sheets or income statements.</p><h3>18. Tracking Source Code Leaks</h3><h4>Query:</h4><p>intitle:”index of” (“source code” OR “src.zip” OR “codebase” OR “repository.zip” OR “source_files”) AND (“code” OR “repository”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Looks for directories containing publicly exposed source code repositories or files.</p><h3>19. Finding Exposed API Keys in GitHub Repositories</h3><h4>Query:</h4><p>site:github.com intext:”API_KEY” OR intext:”SECRET_KEY” OR intext:”access_token” OR intext:”client_secret” OR intext:”auth_token” -README -intitle:”documentation”</p><h4>Explanation:</h4><p>Targets exposed API keys that are inadvertently included in public GitHub repositories.</p><h3>20. Locating Cloud Storage Links</h3><h4>Query:</h4><p>intext:”drive.google.com” OR intext:”dropbox.com” OR intext:”onedrive.com” OR intext:”icloud.com” OR intext:”mega.nz” filetype:pdf OR filetype:txt OR filetype:doc OR filetype:xlsx -intitle:”documentation”</p><h4>Explanation:</h4><p>Searches for exposed links to cloud storage services such as Google Drive or Dropbox.</p><h3>21. Finding Personal Data in Public Legal Filings</h3><h4>Query:</h4><p>site:courtlistener.com OR site:justia.com OR site:pacermonitor.com intext:”personal information” OR intext:”confidential” OR intext:”private data” OR intext:”sensitive information” -intitle:”documentation”</p><h4>Explanation:</h4><p>Identifies personal information that may be exposed in publicly available legal documents.</p><h3>22. Discovering Vulnerable IoT Devices</h3><h4>Query:</h4><p>inurl:”/device.rsp” OR inurl:”/config.xml” OR inurl:”/status.xml” OR inurl:”/device_config” OR inurl:”/admin/config” intitle:”IoT” OR intitle:”device” OR intitle:”configuration” -intitle:”documentation”</p><h4>Explanation:</h4><p>Locates configuration or status pages of Internet of Things devices that might be misconfigured or insecure.</p><h3>23. Uncovering HR Files or Recruitment Documents</h3><h4>Query:</h4><p>intitle:”HR” OR intitle:”recruitment” OR intitle:”staff” OR intitle:”talent acquisition” OR intitle:”job applications” intext:”resume” OR intext:”CV” filetype:pdf OR filetype:docx -intitle:”documentation”</p><h4>Explanation:</h4><p>Finds recruitment documents or HR files containing resumes and other sensitive information.</p><h3>24. Searching for Public Data Breach Reports</h3><h4>Query:</h4><p>intitle:”data breach” OR intitle:”security incident” OR intitle:”breach report” OR intitle:”compromise report” filetype:pdf OR filetype:doc OR filetype:xls OR filetype:txt -intitle:”documentation”</p><h4>Explanation:</h4><p>Targets reports and documents related to data breaches, often detailing compromised data and vulnerabilities.</p><h3>25. Identifying Exposed SSL/TLS Certificates</h3><h4>Query:</h4><p>intitle:”index of” (“ssl.crt” OR “ssl.key” OR “certificate.pem” OR “private.key” OR “tls_certificate” OR “certificates”) -intitle:”documentation” -filetype:pdf</p><h4>Explanation:</h4><p>Finds directories containing SSL/TLS certificates, which may be exposed without proper security.</p><h3>26. Finding Employee Handbooks or Policy Documents</h3><h4>Query:</h4><p>intext:”employee handbook” OR intext:”HR policies” OR intitle:”company policies” OR intitle:”employee guide” OR intext:”staff manual” filetype:pdf OR filetype:docx -intitle:”documentation”</p><h4>Explanation:</h4><p>Locates public employee handbooks or HR policy documents, useful for OSINT on company procedures.</p><h3>27. Tracking Personal Contact Information in Online Directories</h3><h4>Query:</h4><p>site:linkedin.com OR site:facebook.com OR site:twitter.com intext:”contact” AND intext:”email@example.com” OR intext:”phone number” OR intext:”address” OR intext:”contact details&quot;</p><h4>Explanation:</h4><p>Focuses on personal contact information that may be shared in online profiles or directories.</p><h3>28. Discovering Publicly Accessible Bug Reports or Vulnerability Logs</h3><h4>Query:</h4><p>intext:”bug report” OR intext:”vulnerability log” OR intext:”issue tracker” OR intext:”security report” OR intext:”error log” filetype:txt OR filetype:log -intitle:”documentation&quot;</p><h4>Explanation:</h4><p>Searches for bug reports or vulnerability logs, which might contain sensitive technical information.</p><h3>29. Finding Publicly Exposed Corporate Email Lists</h3><h4>Query:</h4><p>intext:”corporate email list” OR intext:”employee email list” OR intext:”staff email addresses” OR intext:”business email list” filetype:csv OR filetype:txt OR filetype:xlsx -intitle:”documentation&quot;</p><h4>Explanation:</h4><p>Identifies publicly shared corporate email lists, useful for OSINT targeting specific organizations.</p><h3>30. Discovering Exposed Medical Records or Health Data</h3><h4>Query:</h4><p>intext:”medical record” OR intext:”patient information” OR intext:”health data” OR intext:”clinical data” OR intext:”</p><h4>Explanation:</h4><p>Locates publicly accessible medical records or health data files, often unintentionally exposed.</p><p><em>Please keep in mind that the utilization of Google Dorks should always be carried out responsibly and ethically. It is crucial to have authorization when assessing vulnerabilities. Unauthorized entry, into systems or data can be deemed illegal. It is important to adhere to privacy and security regulations while conducting any form of testing or research.</em></p><h3>Let’s get in touch:</h3><h4><a href="https://bento.me/as-squirrel">https://bento.me/as-squirrel</a></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f397cd97e252" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/30-advanced-google-dork-queries-for-uncovering-hidden-data-and-osint-insights-f397cd97e252">30 Advanced Google Dork Queries for Uncovering Hidden Data and OSINT Insights</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up Whonix on Linux using VirtualBox]]></title>
            <link>https://medium.com/@arno-sontheim/setting-up-whonix-on-linux-using-virtualbox-ae2bc17baed4?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae2bc17baed4</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[whonix]]></category>
            <category><![CDATA[operating-systems]]></category>
            <category><![CDATA[anonymity]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Wed, 17 Jan 2024 21:10:00 GMT</pubDate>
            <atom:updated>2024-01-17T21:10:00.750Z</atom:updated>
            <content:encoded><![CDATA[<p>A step-by-step guide to installing and configuring Whonix for enhanced privacy and security</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*J-AV3zuku_b0tZreuG2sRw.jpeg" /></figure><p>Whonix is an open source software (OSS) that is used as an operating system in the form of a virtual machine (VM). It specializes in security and privacy. The structure consists of two VMs: one gateway is responsible for all traffic through the Tor network, while the other VM is the workstation that is primarily used for operational purposes.</p><h3><strong>Installation:</strong></h3><h4>Prerequisites:</h4><p>The device should be capable of using VM (Virtual Machine). Here, I will demonstrate the installation on Linux using Parrot 5.3 Electro Ara (Debian 11).</p><h3>First Step:</h3><p>Download the VM <a href="https://www.virtualbox.org/wiki/Downloads">here</a>:</p><p>Once the file is downloaded, you can extract it using the following command:</p><p><em>sudo dpkg -i filename.deb</em></p><p>Now that VirtualBox is installed, we can download Whonix from this <a href="https://www.whonix.org/wiki/VirtualBox">link</a>.</p><h3>Second Step:</h3><p>After downloading the necessary resources, we can start using Whonix. Open VirtualBox with the command ‘virtualbox’. Use the ‘Ctrl-I’ command to open a new window to import Whonix into the VirtualBox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*XbfEcyfHFJelpPHeaxpHgg.png" /></figure><p>Select the .ova file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/582/1*2MieK8Z-hxNZJjXRlnpyRw.png" /></figure><p>Then, click ‘next,’ followed by ‘finish,’ and agree to the terms of the license.</p><p>After some time, you will see the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/954/1*clVzxkikB93qhkUCjwdBpg.png" /></figure><h3>Step 3:</h3><p>First, we need to start the Gateway first by pressing ‘Start.’ After the Gateway starts, you need to accept all the conditions. The next time you start the Gateway, you can press SHIFT and Start, so that the Gateway will start in the background.</p><p>Once the Gateway is started, you can launch the Workstation. Here, you also need to accept and install some things. It will look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mu9aBsuZiPZQlFkDFeoRAA.png" /></figure><p>Now, you can test if everything is functioning by entering the command “curl ip.me” in the console. This will display your IP address, and since you are connected to the Tor network, the IP address will change, as shown here:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*TjBvIIEKqXQjQKR8tJCjpg.png" /></figure><p>Happy Hacking and have fun ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae2bc17baed4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Advanced Google Dork Queries for Network Security Assessment]]></title>
            <link>https://osintteam.blog/10-advanced-google-dork-queries-for-network-security-assessment-9fad6514015a?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fad6514015a</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[google-dork]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[online-privacy]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Sat, 16 Dec 2023 09:22:15 GMT</pubDate>
            <atom:updated>2023-12-18T09:34:55.612Z</atom:updated>
            <content:encoded><![CDATA[<h4>Discovering Vulnerabilities: Advanced Techniques using Google Dorks</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*64pGtYzeU6CN3XZ3AeKXbQ.jpeg" /><figcaption>Bing <a href="https://www.bing.com/images/create?FORM=GENILP">Image Creator</a></figcaption></figure><p><strong>1. Exposed Network Devices:</strong></p><blockquote>intitle:”index of” AND (“router login” OR “device settings”) AND ext:(txt OR cfg OR conf)</blockquote><p><strong>2. Vulnerable IoT Devices:</strong></p><blockquote>intitle:”IoT device” OR intitle:”smart home” AND ext:(xml OR json OR cfg)</blockquote><p><strong>3. Exposed CCTV Cameras or Feeds:</strong></p><blockquote>intitle:”WJ-NT104 Main” OR intitle:”webcamXP 5&quot; inurl:8080</blockquote><p><strong>4. Open Remote Access Points or Servers:</strong></p><blockquote>intitle:”index of” AND (“remote access” OR “remote desktop” OR “remote login”) AND ext:(ini OR cfg OR conf)</blockquote><p><strong>5. Vulnerable FTP Servers or Credentials:</strong></p><blockquote>intitle:”index of” AND (“ftp” OR “credentials”) AND ext:(txt OR ini OR cfg OR log)</blockquote><p><strong>6. Exposed SNMP Configurations:</strong></p><blockquote>intitle:”index of” AND (“SNMP” OR “SNMP configuration” OR “SNMP settings”) AND ext:(txt OR cfg OR conf)</blockquote><p><strong>7. Open RDP Connections or Instances:</strong></p><blockquote>intitle:”index of” AND (“rdp” OR “remote desktop connection”) AND ext:(ini OR cfg OR conf)</blockquote><p><strong>8. Exposed Network Printer Configurations:</strong></p><blockquote>intitle:”index of” AND (“printer settings” OR “network printer”) AND ext:(ini OR cfg OR conf)</blockquote><p><strong>9. Vulnerable Telnet Services or Devices:</strong></p><blockquote>intitle:”index of” AND (“telnet” OR “telnet settings” OR “telnet configuration”) AND ext:(ini OR cfg OR conf)</blockquote><p><strong>10. Exposed Network Shares or Filesystems:</strong></p><blockquote>intitle:”index of” AND (“network shares” OR “file shares” OR “file system”) AND ext:(ini OR cfg OR conf)</blockquote><p><em>Please keep in mind that the utilization of Google Dorks should always be carried out responsibly and ethically. It is crucial to have authorization when assessing vulnerabilities. Unauthorized entry, into systems or data can be deemed illegal. It is important to adhere to privacy and security regulations while conducting any form of testing or research.</em></p><blockquote>Happy Hacking ;)</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fad6514015a" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/10-advanced-google-dork-queries-for-network-security-assessment-9fad6514015a">10 Advanced Google Dork Queries for Network Security Assessment</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 10 Advanced Google Dork Queries for Location-Specific OSINT Investigation]]></title>
            <link>https://osintteam.blog/top-10-advanced-google-dork-queries-for-location-specific-osint-investigation-434a702852eb?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/434a702852eb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[google-dork]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[online-privacy]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Sat, 09 Dec 2023 12:35:41 GMT</pubDate>
            <atom:updated>2023-12-10T10:01:07.158Z</atom:updated>
            <content:encoded><![CDATA[<h4>Unveiling Hidden Insights: Mastering Advanced Techniques to Discover Precise Location-Associated OSINT Details Using Google Dork Queries</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9d0kOlUkmuqT3j8aGcDgfA.jpeg" /><figcaption>Bing <a href="https://www.bing.com/images/create?FORM=GENILP">Image Creator</a></figcaption></figure><p><strong>1: Exploring Location References in Business Directories</strong></p><blockquote>site:yellowpages.com OR site:yelp.com OR site:businessdirectory.com intext:”John Doe” intext:”location” OR intext:”address” OR intext:”map”</blockquote><p>This query targets business directories, seeking mentions of “John Doe” alongside location-related terms, potentially revealing business affiliations or address information associated with the individual.</p><p><strong>2: Uncovering Location-Specific Event Listings</strong></p><blockquote>site:eventbrite.com OR site:meetup.com intext:”John Doe” intext:”location” OR intext:”venue” OR intext:”event address”</blockquote><p>Searching on event hosting platforms like Eventbrite or Meetup, this query aims to discover event listings or RSVPs associated with “John Doe,” potentially revealing event locations or venues.</p><p><strong>3: Scanning Online Classifieds for Location Mentions</strong></p><blockquote>site:craigslist.org OR site:gumtree.com intext:”John Doe” intext:”location” OR intext:”address” OR intext:”map”</blockquote><p>This query targets online classifieds, seeking mentions of “John Doe” alongside location-related terms, potentially revealing postings, listings, or advertisements with location-specific details.</p><p><strong>4: Exploring Location References in Academic Papers</strong></p><blockquote>site:academia.edu OR site:researchgate.net intext:”John Doe” intext:”location” OR intext:”coordinates” OR intext:”geotag”</blockquote><p>Searching on academic platforms, this query aims to uncover published papers or research mentioning “John Doe” alongside terms related to location or geotagging.</p><p><strong>5: Identifying Location Metadata in Online Document Repositories</strong></p><blockquote>site:slideshare.net OR site:scribd.com intext:”John Doe” intext:”location” OR intext:”coordinates” OR intext:”geotag”</blockquote><p>This query targets document repositories, seeking content mentioning “John Doe” alongside terms related to location or geotagging, potentially revealing location metadata within documents or presentations.</p><p><strong>6: Hunting for Location-Specific Reviews</strong></p><blockquote>site:yelp.com OR site:tripadvisor.com intext:”John Doe” intext:”location review” OR intext:”visited” OR intext:”place rating”</blockquote><p>Searching on review platforms, this query aims to uncover reviews or ratings by “John Doe” associated with specific locations or places visited.</p><p><strong>7: Unveiling Geo-Tagged Social Media Posts</strong></p><blockquote>intext:”John Doe” intext:”location” OR intext:”#geotag” OR intext:”#checkin” -site:facebook.com -site:twitter.com -site:instagram.com</blockquote><p>This query focuses on revealing social media posts containing hashtags related to “John Doe” and location-specific terms, excluding major platforms like Facebook, Twitter, and Instagram to explore less-traveled platforms where location information might be available.</p><p><strong>8: Uncovering Location References in Public Profiles</strong></p><blockquote>site:linkedin.com intext:”John Doe” intext:”location” OR intext:”address” OR intext:”map”</blockquote><p>Targeting LinkedIn profiles, this query aims to find mentions of “John Doe” alongside location-related terms, potentially revealing publicly available location information from professional profiles.</p><p><strong>9: Exploring Location Metadata in Public Reports</strong></p><blockquote>filetype:pdf intext:”John Doe” intext:”location” OR intext:”coordinates” OR intext:”geotag”</blockquote><p>This query targets PDF files mentioning “John Doe” alongside terms related to location or geotagging, potentially revealing location-specific information within reports or documents.</p><p><strong>10: Scanning Location References in Blog Directories</strong></p><blockquote>site:blogspot.com OR site:wordpress.com intext:”John Doe” intext:”location” OR intext:”check-in” OR intext:”geo-tag”</blockquote><p>Searching on blog platforms, this query aims to find blog posts mentioning “John Doe” alongside terms related to location or check-ins, potentially revealing personal location-related content.</p><blockquote><em>Please keep in mind that the utilization of Google Dorks should always be carried out responsibly and ethically. It is crucial to have authorization when assessing vulnerabilities. Unauthorized entry, into systems or data can be deemed illegal. It is important to adhere to privacy and security regulations while conducting any form of testing or research.</em></blockquote><p>Happy Hacking ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=434a702852eb" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/top-10-advanced-google-dork-queries-for-location-specific-osint-investigation-434a702852eb">Top 10 Advanced Google Dork Queries for Location-Specific OSINT Investigation</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSINT Unveiled: Russia’s Arctic Ambitions and the Expansion at Alexandraland]]></title>
            <link>https://osintteam.blog/osint-unveiled-russias-arctic-ambitions-and-the-expansion-at-alexandraland-f4eabe3e7fe3?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4eabe3e7fe3</guid>
            <category><![CDATA[geopolitics]]></category>
            <category><![CDATA[russia]]></category>
            <category><![CDATA[military]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[arctic]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Fri, 08 Dec 2023 18:01:53 GMT</pubDate>
            <atom:updated>2023-12-09T11:11:38.233Z</atom:updated>
            <content:encoded><![CDATA[<h4>Unveiling Russia’s Arctic Strategy: OSINT Insights into Alexandraland’s Expansion</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*xga8Mzf6gdG9SlbB9knqhA.jpeg" /><figcaption>Lev Fedoseyev/TASS</figcaption></figure><p>This article talks about how far the Russian expansion into the Arctic is progressing and what implications this has strategically and geopolitically. I also talk about how to use OSINT methods to get this information.<br>In this article I am particularly focusing on the island of Alexandraland in the Arctic, which is part of the Franz Josef Land archipelago.</p><p><strong>History:</strong></p><p>As early as 1942, the Nazis built a weather station on this island.<br>The Soviet Union also had great interest in expanding the island, whether for military, research or scientific purposes. It was already an important part of the Arctic security structures back then.</p><p><strong>Present:</strong></p><p>In recent years we have seen how Russia has massively expanded its military base.</p><blockquote>“We continue to complete our work on the Arctic islands stage by stage, upgrading airfields and building the most advanced infrastructure. I can safely say that not a single country has the same modern infrastructure as Russia does,”</blockquote><p><a href="https://arctic.ru/news/20181225/817443.html"><em>https://arctic.ru/news/20181225/817443.html</em></a></p><p><strong>Shoigu noted.</strong></p><p>For those unfamiliar, Shoigu has been the Defense Minister of Russia since 2012.</p><p>Just to classify again where the archipelago is located.</p><p><strong>Franz Josef Land archipelago:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*csHbGAXuziKgh3kB_cXAGA.png" /></figure><p><strong>Alexandraland airstrip:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Op-lbx6cRIL_A67ELfOkAQ.png" /></figure><p>If you take a closer look at the island, you will notice a large building and an airstrip in the north. If you go back a few years with satellite images you can see that this has been massively expanded, especially after 2020. Here is a small animation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*DGLEH4F0ej5_fXmmvVhwdg.gif" /></figure><p>This video shows the period from 2020 to 2023 and how the runway has become almost twice as long. The runway is now about 3.5 km long. This is particularly interesting because almost every large military and civilian aircraft can now land there, creating a completely new strategic situation. It also shows that Russia has great ambitions in the Arctic.<br>Here is more detailed information about the airfield and the aircraft that can land there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JmEB2Hzlz8tJupZS115NUQ.png" /></figure><p>The largest aircraft can now land on this runway, such as the Ilyushin Il-76 (NATO code name: Candid) as can be seen here</p><p>If we zoom in, we can see that this is the “IL-76МА” (Il-76MA) version and also that it is a Russian aircraft as can be clearly seen on the country’s flag</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*MnNtGeUNHrcw-ZESVs7RGw.png" /></figure><p>It can be assumed that this aircraft will deliver military equipment as well as civil infrastructure.</p><p><strong>Conclusion</strong>:</p><p>Russia is expanding its presence in the Arctic, as evidenced by both documents and media reports. The strategy behind this approach is based on the fact that climate change is expected to continue melting Arctic ice, creating an entirely new trade route. This has extremely interesting implications both militarily and economically. It should also be noted that the Arctic route from China to Europe would be significantly shorter, which is a significant trade consideration.</p><p><em>Please note that this is my first article of this kind, so I would appreciate any feedback. Thank you!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4eabe3e7fe3" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/osint-unveiled-russias-arctic-ambitions-and-the-expansion-at-alexandraland-f4eabe3e7fe3">OSINT Unveiled: Russia’s Arctic Ambitions and the Expansion at Alexandraland</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Advanced Google Dork Queries for OSINT Privacy Breach Identification]]></title>
            <link>https://osintteam.blog/10-advanced-google-dork-queries-for-osint-privacy-breach-identification-ec2a4daa6739?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec2a4daa6739</guid>
            <category><![CDATA[online-privacy]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[google-dork]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Mon, 04 Dec 2023 12:31:49 GMT</pubDate>
            <atom:updated>2023-12-04T15:33:54.642Z</atom:updated>
            <content:encoded><![CDATA[<p>Unveiling Sensitive Data: Advanced Techniques for OSINT Privacy Breach Detection Using Google Dorks</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*_BS-fS9AenposHQFBZsQtg.png" /></figure><p><strong>1. Confidential Documents Related to:</strong></p><p>“John Doe” AND “confidential” OR “internal use only” OR “do not distribute”</p><p><strong>2. Emails or Correspondence Involving:</strong></p><p>“John Doe” AND “email” OR “correspondence” OR “communication” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>3. Sensitive Financial Information:</strong></p><p>“John Doe” AND “bank statement” OR “financial report” OR “confidential financial” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>4. Personal Identifiable Information (PII):</strong></p><p>“John Doe” AND “social security number” OR “address” OR “phone number” OR “personal information” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>5. Passwords or Credentials:</strong></p><p>“John Doe” AND “passwords” OR “login credentials” OR “usernames” filetype:txt OR filetype:log OR filetype:sql</p><p><strong>6. Private Legal Agreements or Contracts:</strong></p><p>“John Doe” AND “confidential agreement” OR “legal contract” OR “non-disclosure agreement” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>7. Personal Health Records or Medical Data:</strong></p><p>“John Doe” AND “medical records” OR “health information” OR “patient data” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>8. Social Security or Identification Numbers:</strong></p><p>“John Doe” AND “social security number” OR “ID number” OR “government identification” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>9. Corporate Strategy or Internal Plans:</strong></p><p>“John Doe” AND “strategic plan” OR “internal roadmap” OR “corporate strategy” filetype:pdf OR filetype:doc OR filetype:txt</p><p><strong>10. Trade Secrets or Intellectual Property:</strong></p><p>“John Doe” AND “trade secrets” OR “proprietary information” OR “intellectual property” filetype:pdf OR filetype:doc OR filetype:txt</p><p><em>Please keep in mind that the utilization of Google Dorks should always be carried out responsibly and ethically. It is crucial to have authorization when assessing vulnerabilities. Unauthorized entry, into systems or data can be deemed illegal. It is important to adhere to privacy and security regulations while conducting any form of testing or research.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec2a4daa6739" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/10-advanced-google-dork-queries-for-osint-privacy-breach-identification-ec2a4daa6739">10 Advanced Google Dork Queries for OSINT Privacy Breach Identification</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 25 Advanced Google Dorks for OSINT and Bug Bounty Hunting]]></title>
            <link>https://osintteam.blog/top-25-advanced-google-dorks-for-osint-and-bug-bounty-hunting-f2d9dceed068?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2d9dceed068</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[google-dorks-list]]></category>
            <category><![CDATA[hacking]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Sat, 02 Dec 2023 15:44:16 GMT</pubDate>
            <atom:updated>2023-12-02T21:09:46.937Z</atom:updated>
            <content:encoded><![CDATA[<p>Effective Techniques for Uncovering Information Security Vulnerabilities and Open-Source Intelligence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*aXGlCevS11stNQuoIudzcg.png" /></figure><p><strong>1. Exposed Configuration Files:</strong></p><ul><li>intitle:”index of” intext:”config.yml” OR intext:”database.yml” OR intext:”settings.py”</li></ul><p><strong>2. Vulnerable Webcams:</strong></p><ul><li>intitle:”webcam” inurl:”/view”</li></ul><p><strong>3. Sensitive Server Logs:</strong></p><ul><li>intitle:”index of” intext:”access.log” OR intext:”error.log” OR intext:”server.log”</li></ul><p><strong>4. Exposed Git Repositories:</strong></p><ul><li>intitle:”index of” inurl:”.git” OR inurl:”.gitignore”</li></ul><p><strong>5. Open Network Devices:</strong></p><ul><li>intitle:”index of” intext:”config.xml” OR intext:”status.xml” OR intext:”network.xml”</li></ul><p><strong>6. Exposed Cloud Storage:</strong></p><ul><li>intitle:”index of” intext:”aws_access_key” OR intext:”gcp_credentials.json” OR intext:”azure_storage_account”</li></ul><p><strong>7. Insecure API Endpoints:</strong></p><ul><li>intitle:”index of” inurl:”/api” OR inurl:”/api/v1&quot;</li></ul><p><strong>8. Exposed Databases:</strong></p><ul><li>intitle:”index of” intext:”database.sql” OR intext:”dump.sql” OR intext:”backup.sql”</li></ul><p><strong>9. Information Disclosure in Error Messages:</strong></p><ul><li>intitle:”error message” intext:”stack trace” OR intext:”exception details”</li></ul><p><strong>10. Exposed Web Application Source Code:</strong></p><ul><li>intitle:”index of” inurl:”.php” OR inurl:”.asp” OR inurl:”.js” OR inurl:”.html”</li></ul><p><strong>11. Security Configuration Files:</strong></p><ul><li>intitle:”index of” intext:”security.yml” OR intext:”secrets.properties”</li></ul><p><strong>12. Exposed Network Devices:</strong></p><ul><li>intitle:”index of” intext:”router login” OR intext:”router settings”</li></ul><p><strong>13. Open S3 Buckets:</strong></p><ul><li>intitle:”index of” intext:”.s3.amazonaws.com” OR intext:”.s3-eu-west-1.amazonaws.com”</li></ul><p><strong>14. Exposed Configuration Dashboards:</strong></p><ul><li>intitle:”index of” intext:”dashboard.yml” OR intext:”settings.conf” OR intext:”config.properties”</li></ul><p><strong>15. Exposed API Documentation:</strong></p><ul><li>intitle:”index of” intext:”api-docs.json” OR intext:”swagger.json”</li></ul><p><strong>16. Vulnerable WordPress Plugins:</strong></p><ul><li>intitle:”index of” inurl:”/wp-content/plugins”</li></ul><p><strong>17. Open Source Intelligence on Employees:</strong></p><ul><li>intext:”site:linkedin.com/in/” OR intext:”site:twitter.com/” OR intext:”site:github.com/”</li></ul><p><strong>18. Exposed Network Devices:</strong></p><ul><li>intitle:”index of” intext:”device login” OR intext:”device settings”</li></ul><p><strong>19. Open GitLab Repositories:</strong></p><ul><li>intitle:”index of” inurl:”/gitlab”</li></ul><p><strong>20. Insecure Jenkins Instances:</strong></p><ul><li>intitle:”index of” intext:”jenkins” OR intext:”job/config.xml”</li></ul><p><strong>21. Exposed Kubernetes Dashboards:</strong></p><ul><li>intitle:”index of” intext:”k8s-dashboard” OR intext:”kubernetes-dashboard.yaml”</li></ul><p><strong>22. Exposed Jira Instances:</strong></p><ul><li>intitle:”index of” intext:”jira” OR intext:”jira-config.properties”</li></ul><p><strong>23. Exposed Docker Compose Files:</strong></p><ul><li>intitle:”index of” intext:”docker-compose.yml” OR intext:”docker-compose.yaml”</li></ul><p><strong>24. Exposed Subdomains:</strong></p><ul><li>intitle:”index of” intext:”subdomains.txt” OR intext:”subdomains.json”</li></ul><p><strong>25. Exposed IoT Devices:</strong></p><ul><li>intitle:”index of” intext:”IoT device” OR intext:”smart home configuration”</li></ul><p><em>Please keep in mind that the utilization of Google Dorks should always be carried out responsibly and ethically. It is crucial to have authorization when assessing vulnerabilities. Unauthorized entry, into systems or data can be deemed illegal. It is important to adhere to privacy and security regulations while conducting any form of testing or research.</em></p><p><strong>Let’s get in touch:</strong></p><p><a href="https://bento.me/as-squirrel">https://bento.me/as-squirrel</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2d9dceed068" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/top-25-advanced-google-dorks-for-osint-and-bug-bounty-hunting-f2d9dceed068">Top 25 Advanced Google Dorks for OSINT and Bug Bounty Hunting</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top 25 Advanced Google Dorks for Uncovering Sensitive Documents]]></title>
            <link>https://osintteam.blog/top-25-advanced-google-dorks-for-uncovering-sensitive-documents-a9705e05353d?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9705e05353d</guid>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[google-dork]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Wed, 29 Nov 2023 17:52:21 GMT</pubDate>
            <atom:updated>2023-11-29T19:15:34.356Z</atom:updated>
            <content:encoded><![CDATA[<h4>Efficient Techniques for Investigating Confidential Files and Documents</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*YkchspMAUnzOKzHLJNuyfg.png" /></figure><p><strong>Confidential Documents:</strong></p><p>1. intext:”confidential” intitle:”filetype:xls OR filetype:xlsx OR filetype:csv”</p><p>2. intitle:”classified” OR intitle:”top secret” intext:”password” filetype:pdf</p><p>3. intext:”client data” OR intext:”customer details” intitle:”confidential” filetype:docx</p><p>4. intitle:”confidential” OR intitle:”restricted” intext:”salary” filetype:pdf</p><p>5. intext:”internal use only” OR intext:”not for public release” filetype:doc</p><p><strong>Corporate Communications:</strong></p><p>6. intext:”CEO” OR intext:”CFO” OR intext:”COO” intitle:”email” filetype:txt</p><p>7. intitle:”board meeting” OR intitle:”shareholder report” intext:”draft” filetype:pdf</p><p>8. intitle:”corporate secrets” OR intitle:”proprietary information” intext:”email” filetype:docx</p><p>9. intext:”marketing strategy” OR intext:”business development” intitle:”confidential” filetype:pdf</p><p>10. intitle:”internal memo” OR intitle:”confidential communication” intext:”HR” filetype:doc</p><p><strong>Financial Records:</strong></p><p>11. intext:”financial report” intitle:”company name” OR intitle:”quarterly” filetype:pdf</p><p>12. intext:”investment portfolio” OR intext:”bank statement” intitle:”confidential” filetype:pdf</p><p>13. intitle:”invoice” OR intitle:”billing statement” intext:”confidential” filetype:xls</p><p>14. intitle:”budget plan” OR intitle:”financial forecast” intext:”confidential” filetype:docx</p><p>15. intext:”tax return” OR intext:”audit report” intitle:”restricted” filetype:pdf</p><p><strong>Employee Information:</strong></p><p>16. intext:”employee directory” OR intext:”HR records” intitle:”confidential” filetype:xlsx</p><p>17. intext:”resume” OR intext:”CV” OR intext:”job application” filetype:pdf</p><p>18. intitle:”employee contract” OR intitle:”confidential employment agreement” filetype:docx</p><p>19. intitle:”performance review” OR intitle:”disciplinary action” intext:”confidential” filetype:pdf</p><p>20. intitle:”personnel file” OR intitle:”staff records” intext:”confidential” filetype:doc</p><p><strong>Sensitive Infrastructure Data:</strong></p><p>21. intext:”security plan” OR intext:”network layout” intitle:”confidential” filetype:pdf</p><p>22. intitle:”building plans” OR intitle:”facility layout” intext:”restricted” filetype:docx</p><p>23. intext:”SCADA system” OR intext:”power grid” intitle:”critical infrastructure” filetype:pdf</p><p>24. intitle:”server configuration” OR intitle:”database schema” intext:”confidential” filetype:txt</p><p>25. intitle:”airport security” OR intitle:”seaport layout” intext:”restricted access” filetype:pdf</p><p><em>Please keep in mind that the utilization of Google Dorks should always be carried out responsibly and ethically. It is crucial to have authorization when assessing vulnerabilities. Unauthorized entry, into systems or data can be deemed illegal. It is important to adhere to privacy and security regulations while conducting any form of testing or research.</em></p><p><strong>Let’s get in touch:</strong></p><p><a href="https://bento.me/as-squirrel">https://bento.me/as-squirrel</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9705e05353d" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/top-25-advanced-google-dorks-for-uncovering-sensitive-documents-a9705e05353d">Top 25 Advanced Google Dorks for Uncovering Sensitive Documents</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Advanced Google Dork Queries for OSINT Email Identification]]></title>
            <link>https://osintteam.blog/10-advanced-google-dork-queries-for-osint-email-identification-796ce0225163?source=rss-a3ce9ca74b8------2</link>
            <guid isPermaLink="false">https://medium.com/p/796ce0225163</guid>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[investigation]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[online-privacy]]></category>
            <dc:creator><![CDATA[Arno Sontheim]]></dc:creator>
            <pubDate>Tue, 28 Nov 2023 16:00:06 GMT</pubDate>
            <atom:updated>2023-11-30T22:40:00.857Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Hello, I’m back. Since my first blog on ‘</strong><a href="https://medium.com/@as-squirrel/5-advanced-google-dork-queries-for-osint-email-identification-029aac330c41"><strong>Google Dork Queries for OSINT Email Identification</strong></a><strong>’ was well-received, I’ve created another one, this time with even better queries and explanations. I hope you find it helpful.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*zlAomF91X01z8nbAsevobA.png" /></figure><p><strong>Let’s go…</strong></p><p><strong>1. Identifying Email in Corporate Reports or Proposals:</strong></p><ul><li>Query: intext:”email: username@domain.com” intitle:”corporate report” OR intitle:”proposal” filetype:pdf OR filetype:docx</li><li>Explanation: Looks for the specific email format within the document content (intext) and restricts the search to documents titled as “corporate report” or “proposal.”</li></ul><p><strong>2. Finding Email References in Sensitive Contracts or Agreements:</strong></p><ul><li>Query: intext:”username@domain.com” intitle:”sensitive contract” OR intitle:”restricted agreement” filetype:pdf OR filetype:docx</li><li>Explanation: Searches for the email format within the document content and focuses on files titled as “sensitive contract” or “restricted agreement.”</li></ul><p><strong>3. Locating Email in Financial Reports:</strong></p><ul><li>Query: intext:”email: username@domain.com” intext:”financial report” filetype:pdf OR filetype:docx</li><li>Explanation: Targets documents containing both the specific email format and references to “financial report” in their content.</li></ul><p><strong>4. Discovering Email in Project Reports or Task Summaries:</strong></p><ul><li>Query: intext:”email: username@domain.com” intext:”project report” OR intext:”task summary” filetype:pdf OR filetype:docx</li><li>Explanation: Searches for the specific email format within documents alongside references to “project report” or “task summary.”</li></ul><p><strong>5. Email Identification in Employee Contracts or Confidential Agreements:</strong></p><ul><li>Query: intext:”username@domain.com” intitle:”employee contract” OR intitle:”confidential employment agreement” filetype:pdf OR filetype:docx</li><li>Explanation: Looks for references to “username@domain.com” within documents titled as “employee contract” or “confidential employment agreement.”</li></ul><p><strong>6. Classified Email Traces in Legal Briefs or Privileged Communications:</strong></p><ul><li>Query: intext:”email: username@domain.com” intitle:”classified legal brief” OR intitle:”privileged communication” filetype:pdf OR filetype:docx</li><li>Explanation: Targets the specific email format within files titled as “classified legal brief” or “privileged communication.”</li></ul><p><strong>7. Hidden Email in Internal Memos or Confidential Communications:</strong></p><ul><li>Query: intext:”username@domain.com” intitle:”internal memo” OR intitle:”confidential communication” filetype:pdf OR filetype:docx</li><li>Explanation: Searches for the email format within documents titled as “internal memo” or “confidential communication.”</li></ul><p><strong>8. Email Contacts in Research Findings or Confidential Studies:</strong></p><ul><li>Query: intext:”contact: username@domain.com” intext:”research findings” OR intext:”confidential study” filetype:pdf OR filetype:docx</li><li>Explanation: Targets the specific email format alongside references to “research findings” or “confidential study” within documents.</li></ul><p><strong>9. Identifying Email within Confidential Reports:</strong></p><ul><li>Query: intext:”email: username@domain.com” intitle:”confidential” intitle:”report” filetype:pdf OR filetype:docx</li><li>Explanation: Searches for the email format within documents titled as “confidential report.”</li></ul><p><strong>10. Email References in Version Histories or Revision Logs:</strong></p><ul><li>Query: intext:”username@domain.com” intitle:”version history” OR intitle:”revision log” filetype:pdf OR filetype:docx</li><li>Explanation: Looks for references to “username@domain.com” within documents titled as “version history” or “revision log.”</li></ul><p>Remember to use these with caution and respect others’ privacy. I take no responsibility for any misuse or harm.</p><p>Let’s connect:</p><p>Twitter &gt; <a href="https://twitter.com/as_squirrel_X">https://twitter.com/as_squirrel_X</a></p><p>LinkedIn &gt; <a href="https://www.linkedin.com/in/arno-sontheim-751343252/">https://www.linkedin.com/in/arno-sontheim-751343252</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=796ce0225163" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/10-advanced-google-dork-queries-for-osint-email-identification-796ce0225163">10 Advanced Google Dork Queries for OSINT Email Identification</a> was originally published in <a href="https://osintteam.blog/">OSINT Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>