<?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 Tomi McCluskey on Medium]]></title>
        <description><![CDATA[Stories by Tomi McCluskey on Medium]]></description>
        <link>https://medium.com/@tomi-research?source=rss-fdc8d4519274------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*uStYsfzjYcCfNC39mKDN8g.png</url>
            <title>Stories by Tomi McCluskey on Medium</title>
            <link>https://medium.com/@tomi-research?source=rss-fdc8d4519274------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:38:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tomi-research/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[Houthis strike Netherlands-flagged cargo vessel, setting ship ablaze. Crew injured, ship abandoned.]]></title>
            <link>https://medium.com/the-nauti-notes/houthis-strike-netherlands-flagged-cargo-vessel-setting-ship-ablaze-crew-injured-ship-abandoned-651d198158d0?source=rss-fdc8d4519274------2</link>
            <guid isPermaLink="false">https://medium.com/p/651d198158d0</guid>
            <dc:creator><![CDATA[Tomi McCluskey]]></dc:creator>
            <pubDate>Mon, 29 Sep 2025 22:32:48 GMT</pubDate>
            <atom:updated>2025-09-29T22:51:47.675Z</atom:updated>
            <content:encoded><![CDATA[<h3>Brief: Houthis strike Netherlands-flagged cargo vessel, setting ship ablaze. Crew injured, ship abandoned.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b8iHJu2y2NJdv50NtugMIg.png" /><figcaption>VOI in January 2025</figcaption></figure><p>29 September 2025 1022 UTC, Gulf of Aden <br>Vessel: MV MINERVAGRACHT (<a href="https://www.marinetraffic.com/en/photos/of/ships/shipid:271518/shipname:MINERVAGRACHT?order=date_uploaded">IMO: 9571521</a><em>)</em></p><p><strong>Equasis Info: </strong><br>Year of Build: 2021<br>Registered Owner: MINERVAGRACHT REDERIJ<br>ISM and Ship Manager: SPLIETHOFF’S BEVRACHTINGS BV</p><p><a href="https://apnews.com/article/yemen-houthis-gulf-aden-ship-fire-missile-1a42485ac4ab29188ed1ea85414aba48">Attack on Dutch-flagged ship off Yemen injures two and prompts crew to abandon vessel</a></p><blockquote>UKMTO has received a report of an incident 128NM southeast of Aden Yemen. The Master reports witnessing a splash and smoke in the distance, astern of the vessel.</blockquote><blockquote><strong>Update 001:</strong> Military authorities report that a vessel has been hit by an unknown projectile. The vessel is reported to be on fire.<br>Authorities are investigating. Vessels are advised to transit with caution and report any suspicious activity to UKMTO</blockquote><p>UKMTO Warning 033–25 Attack <a href="https://www.ukmto.org/-/media/ukmto/products/20250929_ukmto_warning_033-25.pdf?rev=e074de00db004ccd80aac11309ee0288">(link)</a></p><h3>Additional Reporting</h3><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=twitter&amp;url=https%3A//x.com/_MartinKelly_/status/1972679455714705669&amp;image=" width="500" height="281" frameborder="0" scrolling="no"><a href="https://medium.com/media/fea3dab9e807d8479c6a32c2a1b2c737/href">https://medium.com/media/fea3dab9e807d8479c6a32c2a1b2c737/href</a></iframe><h3>Global Fishing Watch, last 90 days AIS track</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCeD5k4fcK-n_bAGtrALFw.png" /></figure><h3>Context</h3><h3>Washington Institute December 2024 report</h3><p><a href="https://www.washingtoninstitute.org/policy-analysis/houthi-shipping-attacks-patterns-and-expectations-2025">Houthi Shipping Attacks: Patterns and Expectations for 2025</a></p><h3>Additional 2025 attacks by Houthis</h3><p>31 August — SCARLET RAY</p><p><a href="https://splash247.com/eastern-pacific-chemical-tanker-attacked-by-the-houthis/">Eastern Pacific chemical tanker attacked by the Houthis - Splash247</a></p><p>6 July — MAGIC SEAS sinking</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHb8XdQWkMHQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHb8XdQWkMHQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHb8XdQWkMHQ%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/173994227038336c3289c7b32a5855c0/href">https://medium.com/media/173994227038336c3289c7b32a5855c0/href</a></iframe><p>7 July -ETERNITY SEA sinking</p><p><a href="https://www.worldcargonews.com/shipping-logistics/2025/07/death-toll-from-houthi-attack-on-eternity-c-likely-rises-to-nine/">Death toll from Houthi attack on Eternity C likely rises to nine</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=651d198158d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-nauti-notes/houthis-strike-netherlands-flagged-cargo-vessel-setting-ship-ablaze-crew-injured-ship-abandoned-651d198158d0">Houthis strike Netherlands-flagged cargo vessel, setting ship ablaze. Crew injured, ship abandoned.</a> was originally published in <a href="https://medium.com/the-nauti-notes">The Nauti Notes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSINT Tools for the Tech Challenged]]></title>
            <link>https://osintteam.blog/osint-tools-for-the-tech-challenged-28ca5485143f?source=rss-fdc8d4519274------2</link>
            <guid isPermaLink="false">https://medium.com/p/28ca5485143f</guid>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[tech-tools]]></category>
            <category><![CDATA[google-earth]]></category>
            <category><![CDATA[google-colab]]></category>
            <category><![CDATA[geolocation]]></category>
            <dc:creator><![CDATA[Tomi McCluskey]]></dc:creator>
            <pubDate>Tue, 30 Jul 2024 23:31:28 GMT</pubDate>
            <atom:updated>2024-08-09T06:10:09.240Z</atom:updated>
            <content:encoded><![CDATA[<h4>Search Grid Generator by Bellingcat — a How and Why to</h4><p><strong>Updated to Add:</strong> for a more concise version of this guide, check out a version I worked with Bellingcat’s editorial team for their website (<a href="https://www.bellingcat.com/resources/how-tos/2024/08/05/tracking-your-search-a-guide-to-the-grid-generator/">link</a>).</p><ul><li>Are you new to OSINT and finding your geolocation efforts becoming unhelpfully haphazard?</li><li>Or maybe you’re a seasoned pro facing a time-sensitive project that could benefit from coordinated assistance?</li></ul><p>Enter the Search Grid Generator (<a href="https://colab.research.google.com/github/bellingcat/open-source-research-notebooks/blob/main/notebooks/bellingcat/search-grid-generator.ipynb">link</a>), a tool created by the Bellingcat tech team (<a href="https://www.bellingcat.com/tag/tech-team/">link</a>). It’s quick, easy to use, and designed to create custom grid overlays for map or satellite data. The best part? No installation, code dependencies, or tech wizardry required. It’s particularly well-suited for Google Earth (Web Version) users, but it can easily be used by pretty much any mapping/GIS application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wv6TyDsxkG1k78KrGoeFuQ.png" /><figcaption>Screen shot of the search grid generator tool by Bellingcat: simple, quick, and ready to help you better focus your geolocation searches.</figcaption></figure><p>This guide aims to help you evaluate whether this tool deserves a spot in your OSINT toolkit and, if so, how to hit the ground running with it.</p><p>But first, a bit about the brains behind the tool. Bellingcat is a collective of investigators and researchers who’ve made it their mission to harness OSINT for the common good. They’re not just about using these tools; they’re passionate about educating others in responsible OSINT methodologies and standards, and developing tools that empower the community. (Link — <a href="https://www.bellingcat.com/about/who-we-are/">Bellingcat: Who we Are</a>)</p><p>Full disclosure: While I’m a member of the Bellingcat Discord community and a big fan of their work, I don’t work for them or speak on their behalf. I’m just a fellow OSINT enthusiast who’s found this tool pretty handy and wants to spread the word.</p><h3>What does the Search Grid Generator do?</h3><p>Ever feel overwhelmed staring at a vast satellite image, wondering where to start? The Search Grid Generator brings some rhyme and reason to your area of interest in the form of a tidy, actionable grid. It’s like having a seasoned explorer sketch out a search plan right on your map.</p><p>Here’s the beauty of it: you feed in two coordinates, and out pops a custom grid. No need to wrestle with complex GIS software or dive into coding. It’s all neatly packaged in a Jupyter Notebook, humming away on Google Colab. Think of it as your own turbocharged, cloud-based mapping lab.</p><p>The end result? A KML file you can drag and drop into Google Earth (or your GIS tool of choice) faster than a New York minute. Suddenly, that daunting expanse of terrain becomes a series of manageable chunks, each one begging to be explored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBMIV1QrUDDSG23tyUTZ1A.png" /><figcaption>Satellite imagery of Kiffa, Mauritania. On the right, a grid overlay generated by a Bellingcat Tool that helps organize and focus the search.</figcaption></figure><h3>Why use the Search Grid Generator?</h3><p>Picture this: You’re knee-deep in an OSINT investigation, staring at some satellite imagery confronted with the realization that this planet of ours sure is big. Where do you even start? That’s where our grid comes in handy. Here’s why you might want to add this tool to your OSINT arsenal:</p><ul><li><strong>Kiss disorganization goodbye: </strong>Ever had that nagging feeling you’ve searched the same area twice? Or worse, missed a crucial spot entirely? The grid acts like a visual checklist, helping you keep tabs on where you’ve been and where you’re heading— no more going in circles or leaving stones unturned.</li><li><strong>Teamwork made easy:</strong> Got a crew working on a big case? This grid turns your sprawling search area into a game of battleship. Assign squares to team members and watch as that intimidating vastness gets methodically combed through.</li><li><strong>From overwhelming to underwhelming: </strong>Large-scale searches can feel like trying to find a needle in a haystack. A grid shrinks that haystack into manageable chunks. Suddenly, that impossible task doesn’t seem so impossible anymore.</li></ul><p>In short, it helps turn chaos into order, transforming hundreds of thousands of square meters into something that looks more like your grandma’s quilt — each square a manageable, bite-sized piece of the task at hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WJE_vZdiORlQuYPnCzc2Ug.png" /><figcaption>Google Earth imagery of Cuernavaca, Mexico and overlay from search grid generator. The transparent color fill could indicate different statuses such as completed (red), in progress (yellow), unassigned (no fill).</figcaption></figure><h3>Key Terms</h3><ul><li><strong>Geolocation in OSINT:</strong> Pinpointing the real-world location of something (or someone) using only publicly available information. That Instagram selfie or news footage? It’s not just a picture — it’s a potential treasure map.</li><li><strong>GIS (Geographical Information Systems):</strong> Imagine if maps and databases had a kid. That’s GIS. It’s software that doesn’t just show you where things are, but also what they are, helping you see patterns and connections you might otherwise miss.</li><li><strong>Google Colab:</strong> Your personal sandbox in the cloud. It’s like running powerful code in a hazmat suit — all the benefits, none of the risks to your own computer. Colab lets you use and experiment with tools like Bellingcat’s search grid generator in a secure, Google-hosted environment. No need to worry about installing anything or accidentally messing up your system. Just click, explore, and let Google’s servers do the heavy lifting. It’s the perfect playground for the curious but cautious OSINT investigator.</li><li><strong>Jupyter Notebooks:</strong> A rare case where we can have our cake and eat it too. It’s a web-based sandbox where creators mix code, data, text, and visualizations in one neat package. For us users, it’s like a high-tech playground: we can tweak inputs, hit the magic “run” button, and watch powerful code do its thing — all without the headache of complex setups. Change a few numbers, click, and presto! Instant results at your fingertips.</li><li><strong>KML (Keyhole Markup Language): </strong>The language that Google Earth speaks. It’s how we paint the globe with our own markers, routes, and shapes. Save your creations, and anyone can see your custom map exactly as you drew it. It’s the invisible ink that makes sure your virtual thumbtacks stick where you put them, turning abstract coordinates into something we can all explore.</li></ul><h3>Getting Started with the Search Grid Generator</h3><p>Ready to turn that satellite view sprawl into a neatly organized grid? Let’s walk through it step by step. Don’t worry, I’m not going to bombard you with every possible use case — just the essentials to get you up and running.</p><p><strong>What You’ll Need:</strong></p><ul><li>A web browser (any modern one will do)</li><li>A Google account (you probably have one, right?)</li><li>Two pairs of coordinates in decimal degree format (don’t panic, I’ll show you how to get these)</li></ul><p><strong>Step 1: Grabbing Your Coordinates</strong></p><p>Think of this as picking the corners of your digital sandbox. We need two sets of coordinates: the Top-left and Bottom-right of your area of interest.</p><pre>Top-left     •———————————•  <br>(lat_long_1) |           |<br>             |           |<br>             |           |<br>             •———————————• Bottom-right<br>                           (lat_long_2)<br></pre><p>Fire up Google Maps (<a href="https://www.google.com/maps/">link</a>) and search for your area of interest.</p><ul><li>For the Top-left corner: Right-click, select the first set of numbers. Voila! It’s copied to your clipboard. Paste these somewhere handy — they’ll be used in just a bit for lat_long_1.</li><li>Repeat for the Bottom-right corner. These will be your lat_long_2.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FtSH5U8NuQL7IIM1NPmHWw.png" /><figcaption>In Google Maps, right clicking under Westport brings up a pop menu with the needed coordinates.</figcaption></figure><p><strong>⚠️ Attention ⚠️. </strong>The decimal degree format is required by the grid generator. If you’re copying from Google Maps, you’re golden.</p><p><strong>Step 2: Generating Your Grid</strong></p><p>Now that we’ve marked our territory, let’s create that grid:</p><ul><li>Head over to the Bellingcat Search Grid Generator (<a href="https://colab.research.google.com/github/bellingcat/open-source-research-notebooks/blob/main/notebooks/bellingcat/search-grid-generator.ipynb">link</a>). Sign in to google if you haven’t already.</li><li>Under “Create Grid”, plug in your coordinates for lat_long_1 (top left corner) and lat_long_2 (bottom right corner).</li><li>(Optional) Change the grid size to suit your needs (default is 1 km).</li><li>Optional) Customize your file name if desired, but keep the .kml extension.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1P35x-CVZ3xTCiZYvjPYdA.png" /></figure><ul><li>Hit that play button and watch the magic happen. (It’s actually a Python script, but “magic” sounds cooler.)</li><li>When you hit play, you’ll see a warning: “This notebook was not authored by Google.” Don’t sweat it — this pops up for all non-Google notebooks. It’s Colab’s standard caution tape.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhSRwNY0thOWIT85ChfvLQ.png" /></figure><ul><li>Colab has built-in safeguards, but it’s giving you a heads-up. If you’re dealing with sensitive coordinates or just feeling cautious, take a moment to consider. For most users, though, it’s just a formality.</li><li>Ready to roll? Click “Run anyway” and watch your grid materialize. A little caution keeps us sharp, but don’t let it stall your mapping mission.Click “Download” and save your customized grid to a folder of your choosing.</li></ul><p><strong>Step 3: Importing to Google Earth Web</strong></p><p>Time to bring your grid to life:</p><ul><li>Open Google Earth Web (<a href="https://earth.google.com/">link</a>).</li><li>Click on “New” in the left sidebar, then “local KML file”</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PcR70qd504LL0vTdr5Q5iQ.png" /></figure><ul><li>In the pop-up, under “Local KML file,” select <strong>Import</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*oE84RuBtxmvpkA7cFokMZA.png" /></figure><ul><li>Navigate to and choose your freshly downloaded .kml file.</li><li>Watch as your grid materializes as a new layer in your project.</li><li>Google Earth will automatically zoom to your area, showing off your handiwork.</li><li>Want to play peek-a-boo with your grid? Hover over the layer you’ve added and click on the eye to hide/unhide the grid.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KM57DM01A-04NasLno2yzw.png" /><figcaption>Google Map View of Martha’s Vineyard, United States — 10 km average grid size. Clicking the eye icon will hide/unhide the grid.</figcaption></figure><p>And there you have it! You’ve just turned an unruly patch of pixels into a nice and tidy investigative workspace. Happy hunting!</p><h3>Pro Tips</h3><ul><li>Individual grid squares can be edited and with a semi transparent color to convey status</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XiNj1_YfucEoO2tkilkzRA.png" /><figcaption>Selecting the the top left corner, brings up a pop up window with the grind information. If edit is selected we can change the line and fill color to suit our needs.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W5X1hdizMonWJDtKcUVzAw.png" /><figcaption>To make the fill color visible, change the opacity from the default value of 0%. A team might find this useful to easily indicate that a grid square is off limits, or has already been searched.</figcaption></figure><ul><li>Placemarks can be added as an easy way to label grid squares (Information on adding placemarks to Google Eart Web (<a href="https://support.google.com/earth/answer/9394930?hl=en&amp;ref_topic=9395031&amp;sjid=8917658172227845284-NA#">link</a>)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JfHFAtYs-K1tRjRHKwWubA.png" /><figcaption>Example of simple letter/number grid labeling and individuals assigned</figcaption></figure><ul><li>Export your grid, placemarks, and additional annotations as a KML file to share and coordinate with your team</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PiVGdOgLC7xWsuV1vJuZeg.png" /><figcaption>The new KML will contain additional annotations or layers and can be emailed or shared by other means for your collaborators to import on their devices.</figcaption></figure><ul><li>⚠️ <strong>Advanced:</strong> ⚠️ Other KML files can be imported to combine the usefulness of a systemized grid view with additional data</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x0_4asINr3LMv2piBgf0iQ.png" /><figcaption>Results of of an Overpass Turbo Query of Open Street Maps for places of worship</figcaption></figure><h3>Example Use Case: Putting it All Together</h3><p>Claudia, Jules, and Sam are neck-and-neck with their rivals in an OSINT CTF competition. Their next challenge seems straightforward but tricky: geolocate an ATM in Ghent, Belgium, based solely on a photo showing the machine with some bikes parked in front.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qU7SL2ucH33DGBVHY-j-fQ.png" /><figcaption>The only other clue: Ghent, Belgium.</figcaption></figure><p>Sam makes a clever move, using Overpass Turbo to generate a KML file marking all of Ghent’s ATMs. But time’s running short, and their competitors are closing in. Claudia proposes a divide-and-conquer approach. She fires up the Bellingcat Search Grid Generator, and imports a KML file for Sam’s ATM coordinates to create a systematic plan for combing with Google Street View.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XqRVJGL2JiPPVS8mXbW5g.png" /><figcaption>OSINT in action: This image showcases the power of combining tools. The Bellingcat Search Grid Generator creates the overlay, dividing Ghent into manageable sections. Yellow thumbtacks, courtesy of an Overpass Turbo query, mark potential ATM locations. Grid labels (A1, B1, etc.) and investigator assignments (Jules, Sam, Claudia) guide team coordination. Color-coded squares hint at search progress: red for ruled out, yellow for potential matches. This systematic approach transforms a daunting task into an organized, collaborative effort</figcaption></figure><p>The resulting grid allows the team to divvy up search areas and track their progress efficiently. This coordinated strategy gives them the edge they need, letting them pinpoint the exact location and clinch the win.</p><h3>Conclusion</h3><p>As we wrap up our journey through the Bellingcat Search Grid Generator, let’s recap the main points:</p><ol><li>This tool transforms vast areas into manageable, searchable grids.</li><li>It’s user-friendly, requiring no coding skills or complex software installations.</li><li>The grid system enhances organization, facilitates teamwork, and makes large-scale searches less daunting.</li></ol><p>While we’ve focused on using the tool with Google Earth Web version due to its accessibility, it’s important to note that the KML files generated can be used with various GIS applications. Google Earth is just the tip of the iceberg — the possibilities extend far beyond.</p><p>That said, it’s worth mentioning that for larger projects or if grid-based searches are a significant part of your workflow, you might want to consider the greater functionality and additional benefits of a robust GIS system like QGIS. The Search Grid Generator is excellent for quick, on-the-fly efforts, but more complex projects may benefit from the advanced features of a full-fledged GIS.</p><p>The examples and use cases we’ve discussed are just food for thought — they’re by no means comprehensive or the only way to use this tool. I’d love to hear how others in the OSINT community are using the grid view. Have you found innovative ways to apply this tool in your investigations? Share your examples and experiences! Your insights could spark new ideas and applications that benefit the entire community.</p><p>Finally, I want to extend a heartfelt thank you to the Bellingcat community, and in particular, the Bellingcat tech team. Their commitment to creating cool and powerful tools like the Search Grid Generator is truly commendable. These efforts go a long way in democratizing OSINT work and elevating the quality of investigations by OSINT practitioners, whether they’re just starting out or are seasoned pros.</p><p>By making such tools freely available and easy to use, Bellingcat is not just advancing the field of open-source investigation — they’re empowering a global community of truth-seekers. So, the next time you’re using the Search Grid Generator to unravel a mystery or shed light on an important issue, take a moment to appreciate the collaborative spirit that made it possible.</p><h3>Happy and healthy investigating, and may your digital sleuthing uncover truths that matter!</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28ca5485143f" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/osint-tools-for-the-tech-challenged-28ca5485143f">OSINT Tools for the Tech Challenged</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[Raspberries for Bad OpSec]]></title>
            <link>https://osintteam.blog/raspberries-for-bad-opsec-75a264b9873d?source=rss-fdc8d4519274------2</link>
            <guid isPermaLink="false">https://medium.com/p/75a264b9873d</guid>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[osint]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[opsec]]></category>
            <dc:creator><![CDATA[Tomi McCluskey]]></dc:creator>
            <pubDate>Tue, 23 Jul 2024 01:09:23 GMT</pubDate>
            <atom:updated>2024-08-06T10:21:36.566Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or: It’s 11:30 PM, Do You Know Where Your Micro SD Cards Are?</h4><p><em>So… you want to hear a story, eh? A story of folly and potential woe — even ruin? Haha, have I got a story for you! From the dark infosec corners of Mastodon’s fediverse, a treasure hunter came upon quite the find, quite the find indeed. What they found shook them to the core–okay, okay, maybe out of laughter, but if you choose to read on, I hope it shakes you too — at least a little bit.</em></p><p><em>But a word of warning before we get on with it: the only thing uncommon about this story is that it was told. Ask around with your developer friends, and if they’re honest with you, they’ll tell you they have heard about these things happening. Maybe a flash of recognition, a twinge of regret crosses their eyes, telltale signs of those burdened by similar experiences.</em></p><p>— End Dramatic Introduction —</p><p>On July 20th, a <a href="https://digipres.club/@foone/112817523308786223">thread</a> started making the rounds across the microblogging site <a href="https://joinmastodon.org/">Mastodon</a>. <a href="https://digipres.club/@foone">@Foone</a> came across something in their tinkering that most would overlook, and certainly not take time on a Friday or Saturday to bother with. But @Foone is the sort of person who gets curious, really curious as to why someone left a MicroSD card in something the size of a pack of cigarettes. (Link for thread reader view of post <a href="https://mastoreader.io/?url=https%3A%2F%2Fdigipres.club%2F%40foone%2F112817523308786223">here</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tuE4nIhBXkFM8QQeJMVWEw.png" /></figure><p>This post is a case study of what @Foone found and why the thread commentators reacted as they did.</p><p>Who is this for? If you’re new to OSINT, OPSEC, or development, pull up a chair. There’s a lot that went wrong in this story, which means there is a lot to learn from.</p><p>Who is this not for? If your security practices and OPSEC are squared away, on point, beyond reproach, you’re good to go. Unless you’re in the mood for gallows humor. If so, stick around, and have a laugh at someone who should have known better.</p><h3>Raspberry Pi, not Raspberry Pie</h3><p>So before we dive in, let me briefly explain what a <a href="https://www.raspberrypi.com/">Raspberry Pi</a> and MicroSD card are for those who might not be familiar.</p><p>A Raspberry Pi is a compact, single-board computer. Most recent models have built-in Wi-Fi, and you can plug in a keyboard/mouse to use it like a regular computer. It can run various Linux distributions quite well, considering its size and price. They’re great for hobbyists and students. And because they’re cheap and tiny, they’re also great for software developers, OSINT researchers, and penetration testers. Some Dark Web researchers even use a Raspberry Pi enhanced OpSec during sensitive investigations. In the world of IoT (Internet of Things), developers often use Raspberry Pis to prototype and test their products before final production. This is because the Pi’s low cost and flexibility make it perfect for experimenting with different configurations and software setups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2r8pJalYGE0bNXdg" /><figcaption>Photo by <a href="https://unsplash.com/@praveentcom?utm_source=medium&amp;utm_medium=referral">Praveen Thirumurugan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>A MicroSD card is a tiny removable storage device, about the size of a fingernail. In a Raspberry Pi, it functions like a hard drive, holding the operating system and user files. They come in various storage capacities, affecting their price and capabilities. One could have one card with Kali Linux (for penetration testing), another with Ubuntu for general use, and another set up for an IoT development environment. If somehow, someway, the user completely messes something up, no problem — just swap out your MicroSD card, and you’re back up and running, easy peasy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BXiKRrA61LF-YAfTb_epwQ.jpeg" /><figcaption>Index finger pointing to Micro SD card. Image from the Pi Hut (<a href="https://thepihut.com/blogs/raspberry-pi-tutorials/34243716-what-is-actually-on-your-raspberry-pi-sd-card">link</a>)</figcaption></figure><p>Now that we understand what we’re dealing with, let’s dive into @Foone’s shocking discovery.</p><p>Being an inquisitive sort, @Foone had set out to puzzle out how an IoT device they had come across worked. Let’s take a look at their telling of how they found what they found:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tXHSVs7ecVQBYiJ3L8idlw.png" /></figure><p>That’s it. No elite haXXor skills. No magic powers. <strong>Just “lookin’</strong>”.</p><p>What’s the big deal? Why the fuss?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F23009338&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fso-what-al-bundy-married-with-children-i-dont-care-idc-gif-23009338&amp;image=https%3A%2F%2Fmedia.tenor.com%2FI5Kd6Ovry0QAAAAN%2Fso-what-al-bundy.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/b25e2a758202c8a9a14546a3726bd630/href">https://medium.com/media/b25e2a758202c8a9a14546a3726bd630/href</a></iframe><p>Well, see, the MicroSD card on a Raspberry Pi contains more than just user files like PDFs or photos you might store on a USB drive. It also has the entire operating system. And a whole lot is going on in your operating system that really, really isn’t for just anyone to see.</p><p>From Foone’s thread, here are some of the highlights:</p><ul><li>the .bash_history of the development process</li><li>operating system logs</li><li>Software secrets such as keys and passwords</li><li>Sensitive company data</li><li>Browser profile and cookies</li><li>Search history related to challenges in the development project</li></ul><p>Suffice it to say, any of the above information being found or discovered by someone not intended or authorized is a very bad and very preventable thing.</p><p>But it gets worse.</p><h3>We were warned: Pi/Pie will make you Cry</h3><p>Remember how I mentioned Raspberry Pi’s/MicroSD cards are great for IoT project development? Well, in this case, the SD card that this developer was working on got used as the image for all the devices that were produced and shipped. That means <strong>everyone</strong> who got their hands on one of the devices like @Foone <strong>got an exact image</strong> of the MicroSD card with all its sensitive messiness.</p><h3>Lessons and Reminders</h3><p>While @Foone’s discovery highlights a specific case, it’s crucial to understand that these issues apply broadly across various fields. Let’s explore some key principles that everyone working with sensitive data should keep in mind.</p><p>There’s a heap of bad practices and security issues in what @foone found, and I invite you to take a look at the full thread (<a href="https://digipres.club/@foone/112817523308786223">link</a>)if you’re interested in diving deeper. The comment section is also full of great insights. But for now, I want to keep a sharp focus on two critical points that apply whether you’re a developer, an OSINT researcher, or a Dark Web investigator:</p><ul><li>Be meticulously mindful of your sensitive data — particularly when stored on easily overlooked media like MicroSD cards.</li><li>Ensure that your working environments and tools are clean and contain nothing superfluous — certainly no remnants of personal or unrelated activities.</li></ul><p>Let’s break these down:</p><p><strong>Mindful Data Management:</strong> MicroSD cards and small USB drives are tiny, easily misplaced, and often forgotten about. For a developer, this might mean exposing source code. For an OSINT researcher, it could be revealing sources. For a Dark Web investigator, it might compromise ongoing operations or even personal safety.</p><p><strong>Best Practice: </strong>Treat all your data storage devices as potential security risks. Implement:</p><ul><li>Encryption for all sensitive data</li><li>A rigorous check-in/check-out system for removable media</li><li>Regular audits of what’s stored where</li><li>Secure erasure procedures when repurposing or disposing of devices</li></ul><p><strong>Clean Working Environments:</strong> Whether you’re building an IoT product, conducting OSINT research, or investigating the Dark Web, it’s crucial to maintain clean, purpose-specific environments.</p><p><strong>Best Practice:</strong> Create separate, sanitized environments for different aspects of your work:</p><ul><li><strong>Developers:</strong> Use a clean environment for building production images, free from development tools and personal data.</li><li><strong>OSINT Researchers:</strong> Maintain a “clean” online persona for investigations, completely separate from personal accounts and data.</li><li><strong>Dark Web Investigators:</strong> Use dedicated, isolated systems for Dark Web access, free from any personal identifiers or unrelated software.</li></ul><p>The consequences of neglecting these practices can be severe across all fields:</p><ul><li>Exposed sensitive information (company secrets, investigation details, personal data)</li><li>Compromised operations or investigations</li><li>Potential legal issues</li><li>Personal safety risks (especially for Dark Web investigators)</li><li>Damage to professional reputation</li></ul><p>Remember, in any digital investigation or development work, what you can’t see CAN hurt you. A tiny MicroSD card, a forgotten browser cookie, or an overlooked config file can be a huge liability if not managed properly.</p><h3>Ethical Considerations:</h3><p>When you stumble upon sensitive data, like @Foone did, it’s crucial to handle the situation ethically. Here are some key points to consider:</p><p>1. <strong>Resist the urge to exploit:</strong> As @Foone said, “well I’m putting this away so I don’t accidentally hack them.” This shows admirable restraint and professionalism.</p><p>2. <strong>Responsible disclosure:</strong> If you discover a security flaw or exposed data, consider informing the responsible party privately. Give them a chance to address the issue before making it public.</p><p>3. <strong>Protect privacy:</strong> Avoid sharing personal or sensitive information you may have found. In @Foone’s case, they were careful not to reveal identifying details about the company or individuals involved.</p><p>4. <strong>Legal considerations:</strong> Be aware of the legal implications of accessing or disclosing found data. When in doubt, consult with a legal professional.</p><p>5.<strong> Educational value: </strong>Use discoveries as learning opportunities for yourself and others, but always in a way that doesn’t compromise security or privacy.</p><h3>Conclusion:</h3><p>The tale of @Foone’s Raspberry Pi discovery serves as a stark reminder of the importance of sound data management and clean working environments. Whether you’re a developer working on the next big IoT device, an OSINT researcher digging for information, or a Dark Web investigator navigating murky waters, the principles remain the same:</p><ul><li>Be vigilant about your data, especially on easily overlooked media like MicroSD cards.</li><li>Maintain clean, purpose-specific environments for your work.</li><li>Always consider the ethical implications of your actions and discoveries.</li></ul><p>Remember, in our increasingly connected world, a tiny oversight can have massive repercussions. By following best practices and maintaining an ethical approach, we can all contribute to a safer, more secure digital landscape.</p><p>As you go about your work, whether it’s development, research, or investigation, take a moment to audit your practices. Are your MicroSD cards accounted for? Is your working environment free from unnecessary data? Are you prepared to handle unexpected discoveries ethically?</p><h3>Stay curious, stay secure, and never underestimate the power of “just lookin’”.</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75a264b9873d" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/raspberries-for-bad-opsec-75a264b9873d">Raspberries for Bad OpSec</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[AI is Off to the Races: Can Education Keep Pace?]]></title>
            <link>https://medium.com/@tomi-research/a-new-survey-by-common-sense-media-hopelab-and-the-harvard-graduate-school-of-educations-center-e608132746c0?source=rss-fdc8d4519274------2</link>
            <guid isPermaLink="false">https://medium.com/p/e608132746c0</guid>
            <dc:creator><![CDATA[Tomi McCluskey]]></dc:creator>
            <pubDate>Mon, 03 Jun 2024 15:08:12 GMT</pubDate>
            <atom:updated>2024-06-03T15:11:42.066Z</atom:updated>
            <content:encoded><![CDATA[<p>A new survey by Common Sense Media, Hopelab, and the Harvard Graduate School of Education’s Center for Digital Thriving reveals a surprising disconnect between the rapid growth of generative AI tools and their adoption among teens and young adults. <strong>The survey found that only 4% of respondents aged 14–22 use AI tools daily, while 41% have never used them at all.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NvHBu735wmGQBtDL" /></figure><p>This finding matches what I’ve seen in my own family. None of my four nieces and nephews in middle and high school have tried generative AI or even talked about it in their classes. It seems like schools aren’t doing much yet to help students understand and use AI in responsible ways.</p><p>I believe schools have an important role to play in preparing students for a future where AI is increasingly common. They should start teaching about AI in different subjects and giving students chances to try out these tools in class. This can help students learn about the benefits and risks of AI and develop the skills they’ll need in an AI-driven world.</p><p>Schools can also support parents in helping their children use AI responsibly at home. They could offer resources and workshops to educate parents about AI and how to guide their children’s use of these tools.</p><p>Some questions to think about:</p><ol><li>How can schools effectively teach about AI in different subjects and grades?</li><li>What training do teachers need to feel confident teaching about AI and using it in their lessons?</li><li>How can schools balance the benefits of AI with the need to develop critical thinking skills and avoid over-reliance on technology?</li><li>What can schools do to help parents understand AI and support responsible use at home?</li></ol><p>As AI keeps advancing, we must make sure young people are learning about it in thoughtful ways. By working together, schools and parents can help the next generation make the most of AI while also being prepared for its challenges.</p><p>Source: <a href="https://www.axios.com/2024/06/03/ai-teens-young-adults-survey">https://www.axios.com/2024/06/03/ai-teens-young-adults-survey</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e608132746c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No metaphors here, move along.]]></title>
            <link>https://medium.com/@tomi-research/no-metaphors-here-move-along-now-2db8b05bc086?source=rss-fdc8d4519274------2</link>
            <guid isPermaLink="false">https://medium.com/p/2db8b05bc086</guid>
            <category><![CDATA[common-goo]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[big-tech]]></category>
            <category><![CDATA[future]]></category>
            <dc:creator><![CDATA[Tomi McCluskey]]></dc:creator>
            <pubDate>Wed, 08 May 2024 17:44:52 GMT</pubDate>
            <atom:updated>2024-05-08T17:47:47.291Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qGT6fNXc4e8TOaQd" /><figcaption>Photo by <a href="https://unsplash.com/@jannerboy62?utm_source=medium&amp;utm_medium=referral">Nick Fewings</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Apple’s new iPad Pro ad features an industrial crusher smooshing a diverse assortment of human artifacts while an upbeat, cheerful soundtrack plays in the background.</p><p>Pay no attention to the nagging anxiety attempting to draw a parallel between Big Tech and the common good.</p><h3>Tim Cook on Twitter: &quot;Meet the new iPad Pro: the thinnest product we&#39;ve ever created, the most advanced display we&#39;ve ever produced, with the incredible power of the M4 chip. Just imagine all the things it&#39;ll be used to create. pic.twitter.com/6PeGXNoKgG / Twitter&quot;</h3><p>Meet the new iPad Pro: the thinnest product we&#39;ve ever created, the most advanced display we&#39;ve ever produced, with the incredible power of the M4 chip. Just imagine all the things it&#39;ll be used to create. pic.twitter.com/6PeGXNoKgG</p><p>As an aside, the House that (Steve) Jobs built should hire my niece as a penetration tester for Apple’s so-called parental controls. A 13-year-old with the beginnings of a social life makes mincemeat of that poorly designed and tested system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*w980IvcoiFP-Pomf1ave1w.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2db8b05bc086" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>