<?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 Voldemort on Medium]]></title>
        <description><![CDATA[Stories by Voldemort on Medium]]></description>
        <link>https://medium.com/@vold3mort?source=rss-19348ce5fa19------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eD8cfAK_UFl6n67qwv09fQ.png</url>
            <title>Stories by Voldemort on Medium</title>
            <link>https://medium.com/@vold3mort?source=rss-19348ce5fa19------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:31:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vold3mort/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[I Built a Recon Tool That Runs While I Sleep. Meet Wraith. ]]></title>
            <link>https://osintteam.blog/i-built-a-recon-tool-that-runs-while-i-sleep-meet-wraith-5707af535bef?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/5707af535bef</guid>
            <category><![CDATA[bug-bounty]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Sun, 10 May 2026 09:40:32 GMT</pubDate>
            <atom:updated>2026-05-14T00:57:00.050Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://darkarts.voldemort.co.in/blog/i-built-a-recon-tool-that-runs-while-i-sleep-meet-wraith"><strong>FREE-LINK!!</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3a7oyEmFugI0RaPDP4vZJA.png" /></figure><p>There’s a version of bug bounty hunting that looks cinematic.</p><p>Dark room. Terminal glowing. You’re methodically dissecting some company’s attack surface like you were born for this. You find the thing nobody else found. You write it up clean. It lands.</p><p>That version exists. I’ve lived it.</p><p>But honestly? That’s maybe 20% of the time. 😩</p><p>The other 80% looks like this : run subfinder, copy output, paste into httpx, copy <em>that</em> output, open naabu, realize you forgot to save the subfinder results anywhere permanent, run subfinder again, terminal crashes, 45 minutes gone, nothing to show for it.</p><p>And then you do it again on the next scope. And the next.</p><p>At some point I got tired of being a human pipe operator. So I built something to replace myself for that part.</p><p>That something is <strong>Wraith</strong>. 👻</p><h3>Let Me Be Honest About What This Is</h3><p>The “I built a tool” story has a shape you’ve seen before.</p><p>Guy gets annoyed. Guy hacks together a script over a weekend. Script becomes a tool. Tool gets shipped. Everyone claps. 👏</p><p>That’s a good story. It’s also not what happened here.</p><p>Wraith took months. Not because I’m slow, but because building a CLI tool you actually <em>trust</em> is harder than it looks. The part that takes time isn’t wiring in the tools. It’s everything around them. The error handling. The state management. The interrupts. The edge cases that only show up when you’re mid-scan at 2AM on a target that actually matters.</p><p>The Ctrl+C handler alone cost me more hours than I’m comfortable admitting. Sounds trivial, right? It wasn’t. Python signal handlers and readline have a conflict, if a signal fires while input() is waiting, the whole thing corrupts your scan state silently and crashes. Found that out the hard way. The fix required bypassing readline entirely and dropping to raw terminal I/O. Not fun. But now when you hit Ctrl+C mid-scan, you get this:</p><pre>[WRN] Ctrl+C caught. What now?<br>  [1] Skip this tool   → move to next step<br>  [2] Exit entirely    → state saved, resume anytime<br>  [3] Keep going       → pretend nothing happened</pre><p>No crash. No corruption. Your scan is exactly where you left it.</p><p>I’m not telling you this to sound impressive. I’m telling you because if you’re thinking about building something like this yourself, know that the interesting part is never the tools. It’s always the plumbing. 🔧</p><h3>Okay But What Does It Actually Do?</h3><p>One command. 11 steps. 18 tools. Walk away.</p><pre>python3 wraith.py</pre><p>Pick your project &amp; your target, hit Full Auto Pipeline and go make chai. ☕</p><p>Wraith chains subdomain enumeration, live host filtering, port scanning, web crawling, URL gathering from every source (Wayback, gau, katana), parameter discovery, directory bruteforce, fuzzing, vulnerability scanning, and 14 active recon checks - all feeding into each other automatically. No copy-pasting. No babysitting. No “wait which file was I supposed to feed into this next.”</p><p>The output lands in one organized folder, everything labeled, everything there when you come back.</p><p><strong>The active recon checks are where it gets interesting.</strong> Step 10 runs 14 targeted checks across every live host and param URL it’s collected:</p><ul><li>CORS misconfigurations (sends Origin: https://evil.wraith-recon.com, checks what bounces back)</li><li>Host header injection</li><li>Open redirect testing</li><li>403 bypass via IP-spoofing headers</li><li>Subdomain takeover fingerprinting</li><li>XSS via dalfox</li><li>SQLi detection via sqlmap (detect-only, never exploits)</li><li>SSRF-prone parameter flagging</li><li>SSTI, XXE, NoSQLi, CRLF injection</li><li>Security headers audit</li><li>JS endpoint extraction</li></ul><p>None of it pops shells or submits forms. It finds, flags, and steps aside. The thinking is still yours. That’s on purpose.</p><p>A full wildcard run takes 2–3 hours end to end. The intended workflow is: start it before bed, wake up to results. That’s the whole pitch. 🌙</p><h3>The Resume System (The Feature I’m Actually Proud Of)</h3><p>Not the tool count. Not the 14 active checks. Not the sarcastic greeting at 3AM.</p><p>The resume system. This one’s mine. 🏆</p><p>I lost a 2-hour scan once to a random crash. Had to start from step 1 all over again. I was so annoyed I spent the rest of that night building a state system instead of hunting, which was a completely disproportionate reaction and I regret nothing.</p><p>Now if Wraith crashes, or you Ctrl+C out, or close the laptop, or the WiFi dies, the state is saved automatically. Next time you open the same project and target:</p><pre>[WRN] Previous pipeline scan was interrupted! (last: 2025-08-14 03:22:11)<br>[INF] Completed : subdomain_enum, httpx_live, port_scan, hakrawler<br>[INF] Remaining : url_gathering, paramspider, dirsearch, ffuf, nuclei, active_recon, bifurcate</pre><pre>  [1] Resume from where it stopped<br>  [2] Start fresh</pre><p>And it’s granular. If the port scan was halfway through 12 hosts when it died, it picks up from host 9. Not from step 1. Not from step 3. From exactly where it stopped.</p><p>That detail matters more than it sounds when you’re hunting on a large scope. 🎯</p><h3>Why No AI? (I Know You’re Wondering)</h3><p>Yeah, I know. Every recon tool dropping in 2025 has some AI layer bolted on. So why doesn’t Wraith?</p><p>Short answer: I’m paranoid. 🔒</p><p>Longer answer: I want to know exactly what ran, exactly what it found, and exactly <em>why</em> it flagged something. When a regex match fires or a header is missing, I can trace that. When a model says something “looks suspicious,” I can’t. One of those I can put in a report with full confidence. The other makes me nervous before I hit submit.</p><p>I built Wraith to handle the baseline so that when I sit down to actually hack, my brain is fresh for the part that actually requires one. I want to offload the grunt work, not the thinking. Those are two very different things, and conflating them is how you end up chasing AI-hallucinated endpoints.</p><p>If you want AI in your pipeline, there are solid tools built specifically for that. Wraith is for the paranoid ones. You know who you are. 😏</p><h3>It Has a Personality. This Is Not a Bug.</h3><p>Wraith knows what time it is when you launch it.</p><p>3AM? The greeting knows. It’s not sympathetic about it.</p><p>Skip a step mid-pipeline? It has thoughts. Unhelpful ones.</p><p>Something crashes? The error message is technically accurate and emotionally unhelpful, which honestly describes most of my debugging experience anyway.</p><p>This started as a joke between me and my terminal and stayed because it made the tool less miserable to stare at for hours. A tool that has opinions somehow feels less like running commands and more like — I don’t know, a sarcastic assistant who does the work but isn’t going to pretend any of this is glamorous.</p><p>The sarcasm is non-negotiable. It ships with the repo. 😂</p><h3>Getting It Running</h3><pre>git clone https://github.com/vold3mort-at-dev/wraith.git<br>cd wraith<br>chmod +x install.sh<br>./install.sh<br>source ~/.zshrc   # or ~/.bashrc<br>python3 wraith.py</pre><p>install.sh handles everything -- distro detection (apt, pacman, dnf, yum), Go installation if missing, 13 Go tools, dirsearch + LinkFinder + paramspider cloned to ./tools/, SecLists (~1GB, checks disk space first), nuclei template updates, and a final table showing every tool&#39;s path and status.</p><p>One gotcha worth knowing: if gau is aliased to git add --update on your machine -- super common if you&#39;ve set up git shortcuts -- the installer will warn you. If you don&#39;t fix it, step 5 silently runs nothing and you miss a chunk of URL gathering. Easy fix, easy miss.</p><p>Requirements: Linux, Python 3.8+, Go 1.22+, sudo access, 5GB disk, 2GB RAM.</p><h3>The Moment I Knew This Was Real</h3><p>I remember it clearly.</p><p>I was testing the full pipeline on an actual target. Wildcard scope, decent size. Started the scan, went to make chai, came back 20 minutes later.</p><p>The pipeline was just… running. On its own. Subdomain enum done, httpx filtering live hosts, nmap quietly doing port scans in the background, every output feeding into the next step automatically.</p><p>No intervention from me. No copy-pasting. No “wait which file was I supposed to use here.”</p><p>I just watched it work.</p><p>That was the moment this stopped being a personal script and became something I actually wanted to share. If it can do that for me, spend my actual hacking time on the things that need a human brain instead of being a glorified clipboard, it can probably do that for someone else too. 🧙‍♂️</p><h3>Final Thoughts (And a Genuine Ask)</h3><p>I built this for me first. To stop losing recon output, to stop babysitting tools, to stop starting over every time something crashed.</p><p>But it’s out now. And the best thing that could happen is other hunters use it, break it, and tell me what’s wrong.</p><p>Issues tab is open. If something doesn’t work on your setup, I want to know. If a check is giving false positives, I want to know. If you added something and it’s better now, I <em>really</em> want to know.</p><p>🔗 <a href="https://github.com/vold3mort-at-dev/wraith"><strong>github.com/vold3mort-at-dev/wraith</strong></a></p><p>If it saves you a few hours on your next target, that’s the whole point. ⭐</p><p>👉 <strong>Tools powering this beast:</strong></p><ul><li><a href="https://github.com/projectdiscovery/subfinder">subfinder</a>, <a href="https://github.com/owasp-amass/amass">amass</a>, <a href="https://github.com/tomnomnom/assetfinder">assetfinder</a>, <a href="https://github.com/projectdiscovery/httpx">httpx</a>, <a href="https://github.com/projectdiscovery/naabu">naabu</a>, <a href="https://github.com/hakluke/hakrawler">hakrawler</a></li><li><a href="https://github.com/tomnomnom/waybackurls">waybackurls</a>, <a href="https://github.com/lc/gau">gau</a>, <a href="https://github.com/projectdiscovery/katana">katana</a>, <a href="https://github.com/projectdiscovery/nuclei">nuclei</a>, <a href="https://github.com/ffuf/ffuf">ffuf</a></li><li><a href="https://github.com/hahwul/dalfox">dalfox</a>, <a href="https://github.com/PentestPad/subzy">subzy</a>, <a href="https://nmap.org/">nmap</a>, <a href="https://sqlmap.org/">sqlmap</a></li><li><a href="https://github.com/maurosoria/dirsearch">dirsearch</a>, <a href="https://github.com/GerbenJavado/LinkFinder">LinkFinder</a>, <a href="https://github.com/devanshbatham/ParamSpider">paramspider</a></li><li>☕ Coffee (unofficial but mandatory)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5707af535bef" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/i-built-a-recon-tool-that-runs-while-i-sleep-meet-wraith-5707af535bef">I Built a Recon Tool That Runs While I Sleep. Meet Wraith. 👻</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[How I Built My Own Email Tracker (Because Mailtrack Annoyed Me)]]></title>
            <link>https://osintteam.blog/how-i-built-my-own-email-tracker-because-mailtrack-annoyed-me-5a8be31df847?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a8be31df847</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[email-tracking]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Fri, 10 Oct 2025 10:40:22 GMT</pubDate>
            <atom:updated>2025-10-11T14:53:45.583Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7zqwqD2s0QQ_dWEM3Bq8g.png" /></figure><p>You know those moments when you send an important email, maybe a job application, a complaint, or a pitch, and then spend the next few days refreshing your inbox like it’s a slot machine?<br>Yeah, that was me 😩.</p><p>Every time I sent something that actually mattered, I caught myself wondering: “Did they open it?” “Did it even land in their inbox?” “Should I follow up, or will that make me look desperate?”</p><p>Naturally, being a tech person, my first instinct wasn’t patience. It was “There has to be a tool for this.” 💻</p><p>So I found Mailtrack.<br>And it worked beautifully… until it didn’t.<br>Because every free tool on Earth eventually decides you’ve had too much fun for free 🙃.<br>One fine day, Mailtrack politely told me that if I wanted to keep tracking emails, I had to upgrade.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*4Mi4A_bt3FRfwvYb.gif" /></figure><p>That was it. I took it personally 😤.</p><h4>The Idea Spark 💡</h4><p>At first, it wasn’t even about practicality. It was about ego.<br>I wanted to prove I could build something that worked just as well, without being charged for my own curiosity.</p><p>The concept was simple in theory.<br>Attach a 1x1 invisible pixel image to an email, host it on a small server, and log whenever someone’s email client loads it.<br>Sounds easy, right? Spoiler, it wasn’t 😅.</p><h4>The First Version: The “What Could Possibly Go Wrong” Phase 🤦‍♂️</h4><p>My first attempt was just a Flask app that served a GIF.<br>When the GIF was requested, it would log the visitor’s IP and timestamp.<br>I hit “send” on my test email, opened it on another device, and waited…</p><p>Nothing happened 🫠.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*1Lj8b97L6l2aIEtT.gif" /></figure><p>Turns out, half of modern email clients block external images by default.<br>So I started digging deeper into how trackers actually work, how they log IPs, when they fail, and how Gmail’s image proxy can ruin your day.</p><p>By this point, I had a small Flask app, a broken pixel, and a caffeine problem ☕.</p><h4>Adding the Magic: Making It Actually Work ⚙️</h4><p>Once the basics were in place, I needed a way to send those tracked emails easily.<br>Manually editing scripts every time wasn’t the vibe.<br>So I wrote a simple CLI setup tool that would ask for SMTP credentials, verify them, and store them safely in a config file.</p><p>That’s when the real chaos began 💀.</p><p>Each email provider, Gmail, Yahoo, and Outlook, had its own version of App Passwords and connection quirks.<br>Half my time went into debugging weird errors that said “AUTH failed” even when everything was correct.<br>I later realized Gmail likes to block sign-ins from “less secure apps.”<br>So I made the CLI smart enough to detect that and guide users through setting up proper credentials.</p><p>It felt like the tool was slowly learning to babysit humans 🤖.</p><h4>When Paranoia Meets Engineering 🧠</h4><p>At this point, I realized something important.<br>If I was building a mail tracker, I needed to trust it completely.<br>And honestly, I don’t even trust my toaster with Wi-Fi 🔥, so there was no way I was storing credentials in plain text.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*Y3hnnpedN-p5JoPb.gif" /></figure><p>So I added safety checks.<br>Passwords are masked, configs are permission-locked, and everything sensitive gets verified before saving.<br>Basically, if someone tries to peek inside your config.ini, they’ll only see gibberish or nothing at all 🕵️.</p><p>And yes, I even made it auto-generate missing files like track.gif or log.txt automatically.<br>If the tool was going to act paranoid, it might as well do it properly 😎.</p><h4>Smart Features That Weren’t Planned (But Stayed Anyway) ⚡</h4><p>The biggest feature upgrades came from frustration in real-world testing.</p><p>At one point, my server was already running something else on port 5050.<br>Instead of crashing, the script now checks for conflicts, asks permission to free the port, and handles it gracefully.</p><p>Then came the problem of hosting.<br>Not everyone has a VPS or a domain, so I made the tool smart enough to adapt.</p><p>If you’re using a Cloudflare tunnel with a .trycloudflare.com link, it detects it automatically.<br>If you’re on a cloud server with a reverse proxy, it figures that out too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/374/0*c5fS1lnlWkSEdOuI.gif" /></figure><p>Basically, it learns your setup and adjusts the tracking URL automatically.<br>No manual edits, no half-broken configs, no “oops I forgot the port” moments 😂.</p><h4>That First Successful Ping 🎯</h4><p>After weeks of testing, refactoring, and arguing with SMTP errors, it finally happened.</p><p>I sent an email to myself, opened it from my phone, and watched the terminal log light up with a neat little entry:</p><pre>[2025-09-02 17:05:02] 📬 Open detected for user@example.com <br>| ID: dcc7fb49-9823-4889-a953-bf414fdfc475 <br>| IP: 74.125.151.201 <br>| UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64)</pre><p>I genuinely grinned like a villain in a hacking movie 😈.<br>It worked. My own personal Mailtrack, minus the upgrade emails.</p><h4>Lessons Learned (aka How I Accidentally Leveled Up) 📈</h4><p>This wasn’t just about building a mail tracker. It taught me a lot more along the way:</p><ul><li>Never trust “it’s simple.” What sounds like a weekend project can turn into a bug-hunting marathon.</li><li>Error messages lie. Sometimes the issue is nowhere near where the traceback points.</li><li>Good UX matters, even in CLI. Clear banners, confirmations, and flow make a huge difference.</li><li>Paranoia pays off. Keeping control of your own credentials feels way safer than relying on browser extensions.</li><li>And finally: building your own tools is addictive 🔥. Once you start, you can’t stop.</li></ul><h4>Looking Ahead 🔮</h4><p><a href="https://github.com/vold3mort-at-dev/email-tracker">This project</a> isn’t just a standalone script anymore. It’s part of something bigger.<br>I’ve been slowly building a small arsenal of hacker-style tools for developers and cybersecurity enthusiasts.</p><p>My plan:</p><ul><li>Keep making small, sharp utilities that solve annoying problems.</li><li>Open-source them one by one.</li><li>Share the stories behind them weekly on Medium.</li></ul><p>The <a href="https://github.com/vold3mort-at-dev/email-tracker">Email Tracker v1.0</a> isn’t just code.<br>It’s proof that frustration, caffeine, and stubbornness can turn into something that actually works 💪.</p><p>👉 Tools that powered this little beast:</p><ul><li><a href="https://www.python.org/">Python</a> (Flask, smtplib, requests)</li><li><a href="https://sweetalert2.github.io/">SweetAlert2</a> (for web form magic)</li><li><a href="https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/">Cloudflare Tunnel</a> (for quick exposure testing)</li><li><a href="https://buymeacoffee.com/voldemort">Coffee</a> ☕ (unofficial but mandatory)</li></ul><h3>Final Thoughts ❤️</h3><p>This project started with pure curiosity, and maybe a little paranoia.<br>I just wanted to know if my emails were even being seen. Simple, right? But that “simple idea” pulled me down a rabbit hole of SMTP quirks, pixel requests, and how every mail client handles images differently.</p><p>Somewhere between testing open logs and fighting proxy servers, I realized I wasn’t just building a tracker.<br>I was building trust — trust in my own tools, in my own code, and in knowing exactly what happens after I hit “send.”</p><p>It’s funny how something so small, like a 1x1 GIF, can teach you so much about systems, security, and patience.<br>There’s a strange satisfaction in watching those first logs appear. It feels like a mix of “finally” and “I actually built that.” 😌</p><p>Would I say it was worth it? Every sleepless, coffee-fueled minute. ☕<br>Would I do it again? Probably, with a little less swearing next time.</p><p>So yeah, this wasn’t just about tracking emails. It was about taking control of uncertainty.<br>And that’s something I’ll happily keep building for.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a8be31df847" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/how-i-built-my-own-email-tracker-because-mailtrack-annoyed-me-5a8be31df847">How I Built My Own Email Tracker (Because Mailtrack Annoyed Me)</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[From a Messy Script to Cloud Backup Manager ☁️⚡]]></title>
            <link>https://osintteam.blog/from-a-messy-script-to-cloud-backup-manager-%EF%B8%8F-01dac56ec9bd?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/01dac56ec9bd</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[devtools]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Tue, 23 Sep 2025 11:02:41 GMT</pubDate>
            <atom:updated>2025-09-25T18:37:37.029Z</atom:updated>
            <content:encoded><![CDATA[<p>So here’s the thing… I never planned to build a “Cloud Backup Manager.”<br>All I wanted was a simple way to save my bug bounty findings before they vanished into thin air.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hgX7gQ-ixYWMhDzqYeBPuA.png" /></figure><h3>Why It All Started 🐞💾</h3><p>If you’ve done bug bounty before, you know the drill:<br>Run waybackurls → get a bunch of URLs.<br>Run it again → half of them are different, some are missing, some new ones appear.</p><p>Me:</p><blockquote><em>“Wait… what?? That was important. Where’d it go??”</em></blockquote><p>This problem kept bugging me. Some findings are so time-sensitive that losing them for even a second means wasted hours of recon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*7Qxh3d-LbwTmHeS9.gif" /></figure><p>That’s when it clicked: I needed a way to capture everything as soon as it got created. No manual backups. No “I’ll save this later.” Just an always-on safety net.</p><p>So I whipped up a dirty Python script + rclone to dump files into the cloud.</p><p>And then… the chaos began. 😅</p><h3>The Chaos Phase (a.k.a. Me vs Myself) ⚔️</h3><p>That first script worked… kinda. But every time I wanted to tweak something, it broke.</p><p>I had:</p><ul><li>Multiple .py files like backup_final_v2.py, backup_final_final_v3.py, and the dreaded backup_NEW_NEW_final_fixed.py.</li><li>AI chats across incognito tabs, hopping between different versions like a mad scientist.</li><li>Random crashes where services refused to stop.</li><li>And uninstall routines that… well, didn’t.</li></ul><p>At one point, I had this gem:</p><pre>systemctl start mybackup.service  <br># Service &quot;starts&quot;  <br># Does literally nothing 😭</pre><p>Honestly, I almost gave up there. But every bug pushed me to rewrite, rethink, and rebuild.</p><h3>The Nerdy Bits I Wrestled With 🤓</h3><p>Here’s where the script started levelling up into an actual tool:</p><h4>1. Systemd Services 🛠️</h4><p>I wanted backups to just <em>run in the background</em>. That meant generating .service files dynamically.</p><pre>[Unit]<br>Description=Realtime Cloud Backup<br>After=network.target<br>[Service]<br>ExecStart=/usr/bin/python3 /path/to/runner.sh<br>Restart=always<br>[Install]<br>WantedBy=multi-user.target</pre><p>The first time it restarted after a crash by itself? I felt like a wizard. 🧙</p><h4>2. Realtime Sync with inotify 📡</h4><p>Polling every few minutes? Too slow.<br>I wanted instant uploads.</p><p>Enter inotifywait — it watches every file change and triggers rclone immediately.</p><p>Result: as soon as a new file pops up → boom, uploaded.</p><h4>3. Config File Lockdown 🔒</h4><p>Configs are delicate. One accidental edit = chaos.<br>So I decided to lock them with chattr +i (immutable).</p><p>The script temporarily lifts it, makes changes, then locks it back.<br>Think of it like a diary with a padlock: you can only open it with the right key.</p><h4>4. Proper Uninstalls 🧹💣</h4><p>This part nearly broke me.<br>Creating new backups? Easy.<br>Editing them? Tough, but doable.<br>But uninstalling? That felt like launching a nuke and a hydrogen bomb together. 💥</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*-EcDTZTEh2eTyxUo.gif" /></figure><p>Why? Because uninstalling means <em>destroying everything you created</em>:</p><ul><li>finding all the right configs</li><li>making sure services are stopped and disabled</li><li>removing the runner and log files without breaking other stuff</li><li>cleaning up systemd properly</li><li>and only THEN nuking configs if you’re absolutely sure</li></ul><p>I added triple confirmations so you don’t accidentally wipe everything in rage-click mode.<br>I even let you choose: remove a single backup (safely) or purge ALL of them with multiple “are you SURE??” prompts.</p><p>Feels less like hitting rm -rf / and more like a polished uninstall wizard. Still nerve-wracking, though. 😅</p><h4>5. ASCII Banners 🎨</h4><p>Because honestly? A boring CLI hurts my soul.<br>So I threw in 5 random banners (ASCII Shadow, DOS Rebel, Banner-3D, Poison, Reverse) that swap each run.</p><p>Footer? Centered. Cyan-colored. With links to Report Issues, version number, and GitHub profile.<br>Totally unnecessary, but totally worth it. 😎</p><h3>What It Looks Like 🚀</h3><p><a href="https://github.com/vold3mort-at-dev/cloud-backup-manager">Fire it up:</a></p><pre>python3 cloud_backup_manager.py</pre><p>You’ll see a flashy banner and a menu:</p><ul><li>Create a new backup</li><li>Edit existing backup</li><li>Uninstall backup</li></ul><p>Behind the scenes, it’s doing the heavy lifting: systemd setup, service management, cloud sync, log cleanup, and immutable configs.</p><p>All you see? Clean options and simple interaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*pNCZRQRo1fLKk_mX.gif" /></figure><h3>Lessons Learned (aka How I Levelled Up) 📈</h3><p>This wasn’t just about making a backup tool. It taught me:</p><ul><li>Automation &gt; manual effort: If something can break when you’re tired at 2 AM, automate it.</li><li>Services are tricky: Systemd can feel like black magic until it finally clicks.</li><li>Good UX matters: Even in CLI. The confirmations, the banners, the flow — they make the tool less intimidating.</li><li>Resilience is everything: The tool shouldn’t just <em>work</em>; it should recover when things go sideways.</li></ul><p>And honestly? It gave me a newfound respect for developers who make polished CLI tools. It’s not easy making something feel <em>simple</em>.</p><h3>Looking Ahead 🔮</h3><p>This is just <a href="https://github.com/vold3mort-at-dev/cloud-backup-manager">Tool #1</a> in my bigger open-source journey. My plan?</p><ul><li>Build a set of small but useful hacker/dev tools.</li><li>Drop them on GitHub together.</li><li>Share their stories weekly on Medium.</li></ul><p>The Cloud Backup Manager v1.0.0 isn’t just a script anymore.<br>It’s my story of turning frustration into automation, of learning the hard way, and of shipping something real.</p><p>And this is just the beginning.</p><p>👉 Tools that powered this:</p><ul><li><a href="https://rclone.org/">rclone</a></li><li><a href="https://systemd.io/">systemd</a></li><li><a href="https://github.com/inotify-tools/inotify-tools">inotify-tools</a></li></ul><h3>Final Thoughts ❤️</h3><p>I built this first for me — to back up my bug bounty findings with precision.<br>But now, it’s shaped into something others can use too.</p><p>Was it frustrating? Yep.<br>Did I break things? Absolutely.<br>Would I do it again? …probably 😅.</p><p>That’s the thing about side projects. They start small, but before you know it, they shape <em>you</em> just as much as you shape them.</p><p>Stay tuned. More chaos coming soon.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01dac56ec9bd" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/from-a-messy-script-to-cloud-backup-manager-%EF%B8%8F-01dac56ec9bd">From a Messy Script to Cloud Backup Manager ☁️⚡</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[☠️ How I Broke into a Fintech Giant’s Core — And Landed in Their Hall of Fame  (after rejections…]]></title>
            <link>https://osintteam.blog/%EF%B8%8F-how-i-broke-into-a-fintech-giants-core-and-landed-in-their-hall-of-fame-after-rejections-1a91a269ab77?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a91a269ab77</guid>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[bug-bounty]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Sun, 29 Jun 2025 10:31:51 GMT</pubDate>
            <atom:updated>2025-06-30T00:35:57.182Z</atom:updated>
            <content:encoded><![CDATA[<h3>☠️ How I Broke into a Fintech Giant’s Core — And Landed in Their Hall of Fame 💥 (after rejections, roasts, and a revenge arc)</h3><blockquote>It’s been a minute, huh? 👀 Well — guess who’s back. And let me just say: I’ve been away, but not idle. A lot went down, and I’ve got a LOT to unpack here. So yeah, this blog might be a long one — but I promise it’s a damn good one 🔥 (you probably figured that out from the title already, right? 😏)</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JXUFgVf2vRYTZX2j7IoeOQ.jpeg" /></figure><h3>🧩 The Story Begins: With Coffee, Curiosity, and Chaos</h3><p>So, I stumbled onto this <strong>publicly listed</strong> program on “a certain well-known platform”. Fintech domain. Big scope. Seemed solid.</p><p>Immediately started digging — running recon, checking subdomains, passive intel, login flows, redirect logic, everything. What did I find?</p><p>Nothing. Nada. Zilch. Not even a misconfigured cookie 🍪</p><p>But I knew better than to give up early.</p><p>Some of the best bugs? They hide in plain sight 🫣</p><h3>🐛 Report #1: The challenge.html Curveball</h3><h4><strong>🔍 The Discovery</strong></h4><p>While poking around archived URLs using <strong>waybackurls</strong>, I stumbled upon:</p><pre>https://sandboxcheckout.[redacted].net/3ds/challenge.html?redirection_data=&lt;urlencoded_payload&gt;</pre><p>Inside that redirection_data, guess what was hiding?</p><p>A classic 🍷 acs_action_url parameter.</p><h4>🚪 The Exploit</h4><p>By tampering the acs_action_url inside the URL-encoded redirection_data, I achieved a <strong>GET-based Open Redirect</strong>. Pretty clean — browser redirected to my attacker site without any validation.</p><h4>🤕 The Outcome</h4><p>I reported it, excited. Days later?</p><blockquote>❌ Marked as Duplicate.</blockquote><p>Turns out someone submitted the <strong>same vuln on the same domain</strong>, earlier in 2023.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*MiR8tULpadIJ8eAH" /></figure><p>Bummer. But hey, it proved I was on the right track.</p><h3>🐛 Report #2: The method.html Deja Vu</h3><h4>🔍 Familiar Vibes</h4><p>Again using waybackurls, I found:</p><pre>https://sandboxcheckout.[redacted].net/3ds/method.html?redirection_data=&lt;urlencoded_payload&gt;</pre><p>Just like challenge.html, the redirection_data param carried:</p><pre>{<br>  &quot;acs_action_url&quot;: &quot;https://webhook.site&quot;<br>}</pre><p>Boom 💥 — <strong>same Open Redirect</strong>, different endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*urIZYuG7y5miQ0ET" /></figure><h4>🤔 The Response</h4><blockquote><em>✅ Valid<br> ℹ️ Marked as Informational</em></blockquote><p>They acknowledged it but didn’t consider it impactful enough for a reward. Fair enough — two out of two reports recognized. Just no bounty… yet 😅</p><h3>🧠 Report #3: The One That Hit Hard 💥</h3><p>This was <strong>the big one.</strong></p><h4>🔎 Vulnerability: OTP Bypass via Token IDOR</h4><p>Here’s what went down:</p><ul><li>I visited a <strong>publicly accessible</strong> URL (archived via Wayback again) that hosted a <strong>KYC form</strong>.</li><li>Normally, it loads <strong>after</strong> OTP verification.</li><li>But… turns out I could directly access it if I had a valid happ_{UUID} token.</li></ul><pre>curl -X GET &quot;https://sandboxverify.[redacted].net/v1/verify/applications/hosted/happ_1234-uuid-value&quot;</pre><p>🎯 Guess what it returned?</p><pre>{<br>  &quot;data&quot;: {<br>    &quot;phone_number&quot;: &quot;+972********3&quot;,<br>    &quot;target_entity_token&quot;: &quot;...&quot;,<br>    &quot;application_token&quot;: &quot;...&quot;,<br>    &quot;complete_url&quot;: &quot;...&quot;,<br>    &quot;cancel_url&quot;: &quot;...&quot;,<br>    &quot;application&quot;: { ...full user KYC metadata... }<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*vfgVD5_7L5EP-YkD" /></figure><p>YUP. <strong>No OTP needed.</strong> Just the token.</p><h3>⚙️ How Did I Test?</h3><ul><li>Started with waybackurls to discover the form URL.</li><li>Intercepted the request in Burp.</li><li>Replayed it directly with the token.</li><li>Fuzzed with ffuf and uuidgen to simulate token enumeration.</li><li>Bypassed logic completely without authentication.</li></ul><blockquote><strong><em>Vuln Type:</em></strong><em> Insecure Direct Object Reference (IDOR)<br> </em><strong><em>Severity:</em></strong><em> 🔥 Critical<br> </em><strong><em>Impact:</em></strong><em> Full KYC data leak<br> </em><strong><em>Exploitability:</em></strong><em> Easy — no auth required</em></blockquote><p>Submitted it with full PoC and clear breakdown. This time?</p><blockquote><em>✅ </em><strong><em>Accepted</em></strong><em><br> 🏆 </em><strong><em>Rewarded</em></strong><em><br> 🧢 </em><strong><em>Hall of Fame</em></strong><em> unlocked</em></blockquote><h3>🔐 Let’s Talk About Recon — Like, Real Recon</h3><p>One thing this entire experience screamed at me?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*kt9dB_yLEgrPM8wK" /></figure><p>🗣️ STOP. UNDERRATING. WAYBACKURLS.</p><p>Like seriously. Tools are tools. But they’re not cheat codes. They don’t think for you. They don’t understand context.</p><p>But when you <em>combine tools with a good mindset</em>, with strategic thinking — you become dangerous 🥷</p><p>All I did was use waybackurls, gau, ffuf, and sprinkled in some intuition. I wasn’t chasing CVEs. I wasn’t smashing every endpoint with a scanner.</p><p>I was <strong>trying to understand the app</strong>, its flows, its intentions — and that’s how I won.</p><h3>🧪 Tools, Tactics, and Caffeine</h3><p>Here’s my actual stack:</p><ul><li>🔧 Burp Suite</li><li>🔁 ffuf (for endpoint fuzzing)</li><li>🔎 waybackurls, gau, and Wayback Machine</li><li>🤖 URLDecoder (for decoding tricky stuff)</li><li>👨‍🏫 ChatGPT for reviewing/report writing/perspective</li><li>☕ A concerning amount of coffee</li></ul><h3>💌 The Unexpected Email</h3><p>Weeks later, I had honestly moved on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*hrf7C2jtqNJxZ9ck" /></figure><p>Then — a notification from “that not-to-be-named platform” hit my inbox like a truck 🛻</p><blockquote>“Thanks for your contribution to [redacted]! You’ve been added to their Hall of Fame.”</blockquote><p>Wait. What?</p><p>I went to check and yep — there I was, chilling at <strong>33rd place</strong> 🥹</p><p>Not gonna lie — after two rejections and barely holding onto hope, it felt like justice. Like revenge. Like… redemption 😤</p><h3>✍️ Final Takeaways</h3><p>🧠 If there’s one thing I learned, it’s this:</p><blockquote>Don’t be a tool junkie. Be a <strong>thinker</strong>. Be a <strong>strategist</strong>.<br> Tools don’t find bugs — <strong>you</strong> do.</blockquote><p>Here’s what I’d tell any new bug hunter:</p><p>✅ Read flows like stories — they tell you what devs thought<br>✅ Always check old endpoints (hello Wayback 👋)<br>✅ Try tampering with parameters even if they seem “harmless”<br>✅ Don’t give up after one dupe. Or two. Or five.<br>✅ Use ChatGPT — but only if you’re not scared of getting good 😉</p><p>That’s it from me — till the next target 👻</p><blockquote>P.S.: If you read this far, you now owe me a GIF reaction and maybe a coffee emoji. Deal? ☕</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a91a269ab77" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/%EF%B8%8F-how-i-broke-into-a-fintech-giants-core-and-landed-in-their-hall-of-fame-after-rejections-1a91a269ab77">☠️ How I Broke into a Fintech Giant’s Core — And Landed in Their Hall of Fame 💥 (after rejections…</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[Mastering AWS WAF: Because Your Website Deserves a Cyber Bodyguard ]]></title>
            <link>https://osintteam.blog/mastering-aws-waf-because-your-website-deserves-a-cyber-bodyguard-e4b54684f273?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4b54684f273</guid>
            <category><![CDATA[data-protection]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[firewall]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 18:57:17 GMT</pubDate>
            <atom:updated>2025-01-13T14:32:34.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gk7S5YSgntQziraw6Cf-RQ.jpeg" /><figcaption>Guarding the future of the internet, one block at a time.</figcaption></figure><p>Let’s face it — your website is like that fancy house on the hill with all the nosy neighbours (aka hackers) peering in through the windows. Without a sturdy firewall, you’re practically leaving the door wide open with a “Welcome” mat. But don’t worry, AWS WAF is here to save the day. Grab a coffee ☕ (or something stronger, we’re not judging), and let’s dive into how to arm your website like it’s going to war — because, spoiler alert, it is. 💣</p><h3>AWS WAF: The Internet’s Bouncer Extraordinaire 🕶️</h3><p>Imagine your website is a VIP party, complete with a velvet rope. You want your cool guests (real users) to get in and enjoy the ambience. But you also want to keep out the gate-crashers: SQL injection bots, brute force attackers, and that one guy who always ruins the vibe (looking at you, DDoS attacks). AWS WAF is that intimidating, no-nonsense bouncer who knows who’s cool and who’s not. 🎤🎉</p><h3>Why Should You Care About AWS WAF? 🤷‍♀️</h3><p>Here’s a tough-love moment: If your website isn’t protected, you’re basically inviting cybercriminals to have a field day with your data. You might think, <em>“Oh, I’m too small to be targeted.”</em> Wrong. Hackers love low-hanging fruit. 🍎</p><ul><li><strong>Scenario A:</strong> Your small e-commerce store gets hit with a DDoS attack right before Black Friday. Now your “50% Off” sale is just a memory because your website is down. 😡</li><li><strong>Scenario B:</strong> A bot sneaks into your WordPress blog and starts injecting spammy ads for “miracle weight loss pills.” Yikes.</li></ul><p>Still think AWS WAF is optional? Yeah, didn’t think so. 🤔</p><h3>AWS WAF Architecture: How the Magic Happens ✨</h3><p>Alright, let’s lift the hood and see what’s powering this beast:</p><ol><li><strong>CloudFront (CDN):</strong> This is like Santa delivering your website’s goodies (images, CSS) to users worldwide, fast. 🎅</li><li><strong>Application Load Balancer (ALB):</strong> Think of it as traffic police, directing users to your server without causing a pileup. 🚦</li><li><strong>EC2 Instances:</strong> Your hardworking servers hosting your web app. 🖥️</li><li><strong>AWS WAF:</strong> Sitting at the front gate like a guard dog, sniffing out anything shady. 🐕</li></ol><blockquote><strong><em>Pro Tip:</em></strong><em> Always put AWS WAF in front of your CloudFront or ALB. Why? Because security should be proactive, not reactive. 🔒</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/482/1*fx-2lYVfNlEHlIU_dAJdfA.gif" /></figure><h3>How to Get Started: AWS WAF 101 🎓</h3><p><strong>Step 1:</strong> Log in to<a href="https://aws.amazon.com/console/"> AWS Console</a>.<br>Start by navigating to the “WAF and Shield” section. Don’t let the word “Shield” fool you — it’s not as intense as Captain America’s.</p><p><strong>Step 2:</strong> Select Your Region.<br>AWS WAF is regional, so pick wisely. If you’re using global resources (like CloudFront), select the global scope to rule them all. 🌍</p><p><strong>Step 3:</strong> Create a Web ACL.<br>This is where the fun begins. Define the scope (CloudFront, ALB, API Gateway) and add rules.</p><p><strong>Step 4:</strong> Add Some Killer Rules.</p><ul><li><strong>Managed Rules:</strong> Pre-made by AWS for those who love a shortcut.</li><li><strong>Custom Rules:</strong> Perfect for control freaks who like to micromanage every bit of traffic.</li></ul><p><strong>Step 5:</strong> Turn On Logging.<br><em>Logs = insights. Insights = power. Power = happiness. Don’t skip this. 💡</em></p><h3>AWS WAF Features That’ll Make You Go “Wow!” 🤩</h3><h4>1. Bot Control 🦾</h4><p>Say goodbye to those pesky bots scraping your data. AWS WAF knows a good bot (Google) from a bad bot (random scrapers).</p><h4>2. Account Creation Protection 🔐</h4><p>No more spam sign-ups using disposable emails. AWS WAF sniffs out fake registrations like a pro.</p><h4>3. Account Takeover Prevention 🔑</h4><p>Protects your users’ logins from brute force and credential stuffing. It’s like having a password bouncer.</p><h4>4. Customization Galore 🎨</h4><ul><li>Block specific countries? ✅</li><li>Throttle traffic if someone’s spamming your site? ✅</li><li>Inspect query strings, headers, or even body content? ✅</li></ul><p>AWS WAF isn’t just a tool — it’s a Swiss Army knife for web security. 🛡️</p><h3>The Cost Conundrum 💰</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*PXjSCZASzn9WztlZrvC5ug.gif" /></figure><p>Yes, AWS WAF isn’t free. But is it worth it? 100%. Here’s how to keep your bill in check:</p><ol><li>Use managed rules wisely. They’re efficient and cost-effective.</li><li>Monitor traffic patterns to avoid over-configuring rules.</li><li>Keep your logging precise. Too many logs can equal too many dollars.</li></ol><h3>Real-Life Scenarios: AWS WAF Saves the Day 🎥</h3><ul><li><strong>E-Commerce Heroics:</strong> An online store thwarts a SQL injection attack targeting their product database. The hacker sulks; your customers shop. Win-win. 🛍️</li><li><strong>Streaming Service Savior:</strong> Bots trying to binge-watch for free? Blocked. Real viewers? Happy. 🍿</li><li><strong>Education Superpower:</strong> A university’s portal stays online even during peak exam result day traffic. 🎓</li></ul><h3>The Verdict: Is AWS WAF Worth It? 🤔</h3><p>Absolutely. Whether you’re running a small blog or a high-traffic application, AWS WAF ensures the good guys get in, and the bad guys are left outside, glaring through the window. 😏</p><p>And remember: cybersecurity isn’t a luxury — it’s a necessity. So, secure your website, enjoy peace of mind, and maybe even get a good night’s sleep for a change. 🛌</p><p><em>Did this hit the spot? Share it, comment, or just send me a virtual high-five. Together, we’ll keep the internet safe, one website at a time!</em> ✨</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4b54684f273" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/mastering-aws-waf-because-your-website-deserves-a-cyber-bodyguard-e4b54684f273">Mastering AWS WAF: Because Your Website Deserves a Cyber Bodyguard 🚀</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[Stopping Email Spoofing in Its Tracks: A DMARC, SPF, and DKIM Guide ]]></title>
            <link>https://osintteam.blog/stopping-email-spoofing-in-its-tracks-a-dmarc-spf-and-dkim-guide-f77aba94b240?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77aba94b240</guid>
            <category><![CDATA[email-security]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[phishing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Tue, 31 Dec 2024 11:02:10 GMT</pubDate>
            <atom:updated>2025-01-07T21:09:28.694Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever received an email that looked like it came from your boss, a friend, or even a giant company, but deep down, you knew something was fishy? 🐟 Welcome to the wild world of <strong>email spoofing</strong>, where hackers and scammers impersonate others to wreak havoc. But don’t worry — today, we’re diving into how to secure your email domain with <strong>DMARC, SPF, and DKIM</strong>. Let’s turn that 0/10 security rating into a perfect 10/10! 💯</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XCxPSJgWG2MfneOd1BMxjA.jpeg" /></figure><h3>What’s the Deal with Email Spoofing? 🤔</h3><p>Imagine getting an email from <em>yourself</em> or a trusted organization like a bank, only to realize it’s fake. That’s email spoofing — a trick scammers use to send fraudulent emails that look legit. It’s like someone forging your signature and saying, “Yep, that’s me!”</p><blockquote>Example:</blockquote><blockquote><strong>Legitimate Email:</strong> support@yourcompany.com</blockquote><blockquote><strong>Spoofed Email:</strong> supp0rt@yourcompany.com or even support@yourcompany.com (spoofed).</blockquote><p>Take this example: using an online tool, someone could send a fake email from a well-known brand to your inbox, complete with a convincing subject line like <em>“Must Read: Important Update.”</em> And guess what? Without proper email authentication, these emails land straight in your inbox. Scary, right? 😱</p><h3>Meet the Heroes: DMARC, SPF, and DKIM 🛡️</h3><p>To protect against spoofing, we use these three amigos:</p><ol><li><strong>SPF (Sender Policy Framework):</strong> This specifies which mail servers are allowed to send emails on behalf of your domain. Think of it as a bouncer checking IDs at the door. 🚪</li><li><strong>DKIM (Domain Keys Identified Mail):</strong> Adds a digital signature to your email, proving it hasn’t been tampered with. It’s like sealing a letter with wax — very official! 🕊️</li><li><strong>DMARC (Domain-based Message Authentication, Reporting, and Conformance):</strong> Ensures SPF and DKIM are working together to protect your domain. It also decides what happens to suspicious emails (deliver, quarantine, or reject).</li></ol><p>When configured correctly, these three create a robust defense system, making it nearly impossible for scammers to impersonate your domain🎯</p><h3>The Problem with Half-Baked Security 🍰</h3><p>Many domains have <strong>partial configurations</strong> — SPF and DKIM might be enabled, but DMARC policies are set to “none” (which means <em>do nothing</em>). That’s like locking your front door but leaving the key under the mat. 🗝️</p><p>Case in point: A well-known company had SPF and DKIM set up but a weak DMARC policy. The result? Their domain could still be spoofed, with emails successfully landing in inboxes. 🙈</p><h3>Turning the Tables with EasyDMARC 🔧</h3><p>Setting up email authentication manually can feel like solving a Rubik’s cube blindfolded. But tools like <a href="https://easydmarc.com/"><strong>EasyDMARC</strong></a> make it straightforward. Here’s how:</p><h3>Step-by-Step Setup: DMARC, SPF, and DKIM 🚀</h3><ol><li><strong>Analyze Your Domain</strong><br>Use EasyDMARC to scan your domain. It’ll give you a risk assessment and highlight vulnerabilities.</li><li><strong>Update DNS Records</strong><br>Configure SPF, DKIM, and DMARC by adding specific records to your domain’s DNS. EasyDMARC provides clear instructions for platforms like Bluehost and GoDaddy.</li><li><strong>Set DMARC Policy to “Reject”</strong></li></ol><ul><li><strong>p=none:</strong> Monitors emails but doesn’t block spoofed ones.</li><li><strong>p=quarantine:</strong> Sends suspicious emails to spam.</li><li><strong>p=reject:</strong> Blocks spoofed emails entirely.</li></ul><p>4.<strong> Monitor Reports</strong><br>DMARC generates reports showing how emails from your domain are handled. Tools like EasyDMARC make these reports readable (no more headache-inducing spreadsheets!). 🧾</p><p>5.<strong> Test and Verify</strong><br>Send test emails to confirm everything is working. If you see “10/10” on your EasyDMARC dashboard, you’re golden! 🌟</p><h3>Why This Matters 🧐</h3><p>Email spoofing isn’t just a nuisance — it’s the gateway for phishing attacks, scams, and identity theft. By securing your domain, you’re not only protecting yourself but also your clients, colleagues, and anyone else interacting with your emails. It’s a win-win. 🏆</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*NlzPk8E47JYggO9kCmk2OA.gif" /></figure><h3>Pro Tips for Staying Secure 💡</h3><ol><li><strong>Use Strong Passwords</strong>: Protect your email accounts with long, unique passwords.</li><li><strong>Enable Two-Factor Authentication (2FA):</strong> Add an extra layer of security.</li><li><strong>Educate Your Team:</strong> Ensure everyone knows how to spot phishing attempts.</li><li><strong>Regularly Update Policies:</strong> Security isn’t a one-and-done deal; stay proactive.</li></ol><h3>Final Thoughts 🤓</h3><p>Email security might seem daunting, but with tools like EasyDMARC and a bit of patience, you can lock down your domain like a pro. So, are you ready to stop spoofers in their tracks and get that 10/10 security score? Let’s make the internet a safer place, one domain at a time. 🌐✨</p><p><em>Have questions or want more tips? Drop them in the comments below! 👇</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77aba94b240" width="1" height="1" alt=""><hr><p><a href="https://osintteam.blog/stopping-email-spoofing-in-its-tracks-a-dmarc-spf-and-dkim-guide-f77aba94b240">Stopping Email Spoofing in Its Tracks: A DMARC, SPF, and DKIM Guide 💌</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[Mastering DNS Security: Everything You Need to Know! ]]></title>
            <link>https://vold3mort.medium.com/mastering-dns-security-everything-you-need-to-know-509bafd00655?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/509bafd00655</guid>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[network-security]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Wed, 25 Sep 2024 09:14:33 GMT</pubDate>
            <atom:updated>2024-09-25T09:14:35.134Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Unsecured DNS: The silent doorway for online threats" src="https://cdn-images-1.medium.com/max/1024/1*D8RDHEiSnndytkd8F6SQVA.jpeg" /><figcaption>Unsecured DNS: The silent doorway for online threats</figcaption></figure><p>Ah, the <strong>Domain Name System (DNS)</strong> — the unsung hero of the internet. You probably interact with it dozens of times a day without even realizing it. But hey, who’s counting? Without DNS, you’d have to memorize IP addresses like “192.168.1.1” instead of friendly names like google.com. Sounds like a nightmare, right? 😱</p><p>So what’s the big deal about DNS, and more importantly, why should you care about securing it? Stick with me, and by the end of this blog, you’ll be as fluent in DNS security as your IT department (or maybe even better)! Let’s dive in. 🚀</p><h3>What is DNS and How Does It Work?</h3><p>Imagine DNS as the internet’s phonebook. When you type a website’s name — say, google.com—DNS translates that human-readable name into an IP address that computers use to communicate. 🧠💻 Simple, right?</p><p>Let’s break it down further:</p><ol><li><strong>You type a domain</strong> (like www.example.com) into your browser.</li><li><strong>Your device contacts a DNS server</strong>, asking it to resolve the domain to an IP address.</li><li><strong>The DNS server responds</strong> with the correct IP address.</li><li><strong>Your device connects</strong> to the website.</li></ol><p>Boom! You’re on the site. 🎉 (And now you can brag about knowing how the internet works. No big deal. 😏)</p><h3>But, Is DNS Secure? ⚠️</h3><p>Well, no. DNS wasn’t designed with security in mind. I know, shocking, right? In fact, attackers have gotten pretty cozy with DNS vulnerabilities. They use them to hijack traffic, steal sensitive info, or crash entire systems. Scary stuff. 😬</p><p>Let’s take a closer look at the usual suspects in DNS attacks:</p><h4>1. DDoS Attacks on DNS 🌪️</h4><p>A <strong>Distributed Denial of Service (DDoS)</strong> attack is when cyber villains flood a DNS server with so many requests that it can’t handle the load. The server basically says, “I can’t even” and shuts down, leaving websites unreachable. It’s like trying to get through a jam-packed fast food line. You’ll be waiting for ages just to place an order. 🍔❌</p><h4>2. DNS Spoofing (Cache Poisoning) 🕵️‍♂️</h4><p>This trick is all about deception. Attackers “poison” a DNS cache, making it serve up a fake site instead of the real one. Imagine typing google.com and ending up on a website that looks legit but is actually designed to steal your info. Yep, it’s as sneaky as it sounds. 👻</p><h4>3. DNS Tunneling 🚇</h4><p>This is when attackers use DNS queries to sneak data in or out of a network without anyone noticing. It’s like smuggling contraband in broad daylight — only here, the contraband is sensitive information. If DNS isn’t locked down, attackers could pull off this data heist undetected! 👀💨</p><h3>How to Secure Your DNS (Without Losing Your Sanity) 😌</h3><p>You’re probably wondering how you can protect your DNS from these cyber shenanigans. Fear not! I’ve got your back with a step-by-step guide on how to defend your DNS like a true security pro. 🛡️</p><h4>1. Use DNSSEC (Domain Name System Security Extensions) 🔐</h4><p>DNSSEC is like adding a tamper-proof lock to your DNS records. It ensures that DNS queries and responses aren’t manipulated by digitally signing them. It’s your digital watchdog. If someone messes with the DNS records, you’ll know right away. 💪 Want to test if a domain uses DNSSEC? You can try out this handy <a href="https://www.internetsociety.org/deploy360/dnssec/tools/">DNSSEC Toolkit</a>.</p><h4>2. Keep Your DNS Software Updated 🔄</h4><p>Look, I get it — those constant software update reminders are annoying. But in the world of cybersecurity, they’re your best friend. Keeping DNS software updated patches vulnerabilities and keeps the bad guys out. <strong>Pro tip:</strong> Automate the updates to avoid any forgetfulness!</p><h4>3. Rate-Limit DNS Queries 🧮</h4><p>A solid strategy to prevent DDoS attacks is to rate-limit DNS queries. Think of it like a nightclub — only a certain number of people (or queries) are allowed in at a time. No room for gate-crashers here! You can set these limits using a firewall or specialized DNS tools.</p><h4>4. Monitor DNS Traffic for Anomalies 👀</h4><p>If you’re serious about DNS security, you’ll want to keep an eye on your DNS traffic for any weird behavior. Any unexpected spikes or unusual query patterns could be red flags for an attack. Use tools like <strong>Wireshark</strong> (<a href="https://www.wireshark.org/">link here</a>) or <strong>Zeek</strong> (<a href="https://zeek.org/">link here</a>) to monitor network traffic in real time.</p><h4>5. Implement DNS over HTTPS (DoH) 🌐</h4><p>DNS over HTTPS (DoH) encrypts your DNS queries, keeping them safe from prying eyes. It’s like having a private conversation in a room full of eavesdroppers — they can see you’re talking, but they can’t understand a word of it. DoH ensures your DNS traffic is secure from end to end. You can read more about it here.</p><h3>Final Thoughts (And a Sprinkle of Humor) 😎</h3><p>So, yeah — DNS is the backbone of the internet, but it’s also one of the most overlooked areas when it comes to security. Without proper protection, it can become a playground for cybercriminals. But don’t panic — just by reading this, you’re already one step ahead of them! 🎯</p><p><strong>To Recap</strong>:</p><ul><li>Use <strong>DNSSEC</strong> to prevent tampering.</li><li>Keep your DNS software <strong>up-to-date</strong> (don’t hit snooze on those updates).</li><li>Set up <strong>rate limits</strong> on DNS queries.</li><li><strong>Monitor</strong> traffic for anything weird.</li><li>And finally, implement <strong>DNS over HTTPS</strong> to keep things private.</li></ul><p>Think of DNS security like locking the front door to your house. Sure, everything looks fine from the outside, but if the door’s unlocked, you’re inviting trouble. So let’s go ahead and lock that door — and maybe install some security cameras while we’re at it! 🔒📹</p><h4>Resources to Geek Out On 📚</h4><ul><li><a href="https://www.internetsociety.org/deploy360/dnssec/tools/">DNSSEC Toolkit</a>: Check if a domain has DNSSEC enabled.</li><li><a href="https://www.wireshark.org/">Wireshark</a>: Monitor and analyze your DNS traffic.</li><li><a href="https://zeek.org/">Zeek</a>: Another great tool for network monitoring and analysis.</li><li><a href="https://datatracker.ietf.org/doc/html/rfc8484">DNS over HTTPS (RFC 8484)</a>: A deep dive into DoH and how it works.</li></ul><p>Now that you’re armed with knowledge, go forth and secure your DNS like a pro! 😎👨‍💻 Feel free to drop an emoji in the comments or just flex about how much you’ve learned. (We all know you want to!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=509bafd00655" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Unveiling the Dark Side of Bluetooth: How Thieves Exploit Technology ]]></title>
            <link>https://vold3mort.medium.com/unveiling-the-dark-side-of-bluetooth-how-thieves-exploit-technology-3429d968f8b8?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/3429d968f8b8</guid>
            <category><![CDATA[wireless-hacking]]></category>
            <category><![CDATA[digital-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[bluetooth]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Tue, 27 Aug 2024 04:31:41 GMT</pubDate>
            <atom:updated>2024-08-31T13:31:32.642Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pRLFx_gzBSy-ShZcyylHzA.png" /></figure><h3>Introduction 🤔</h3><p>Bluetooth technology has revolutionized the way we connect our devices. From streaming your favorite playlists to your wireless headphones to syncing data with your smartwatch, Bluetooth makes our lives easier and more connected. But behind this convenience lies a potential risk — Bluetooth can be a playground for tech-savvy thieves. 😱 Let’s explore how Bluetooth can be exploited, what tools are used, and how you can keep your devices safe. Ready for a deep dive? Let’s go! 🚀</p><h3>Bluetooth Basics: What’s the Buzz? 🔍</h3><p>Bluetooth operates at a 2.4 GHz frequency band. Imagine it as a digital conversation highway where your devices exchange data. Bluetooth comes in two main flavors:</p><ul><li><strong>Bluetooth Classic</strong>: Perfect for continuous data streaming, like with wireless headphones or speakers. It’s the go-to for high-bandwidth applications.</li><li><strong>Bluetooth Low Energy (BLE)</strong>: Designed for devices that need to conserve power, such as fitness trackers and smart home sensors. It’s great for intermittent communication and lower energy consumption.</li></ul><p>While this technology is fantastic for everyday use, it’s very convenience makes it a target for hackers. 📡</p><h3>Understanding Bluetooth Security 🧐</h3><p>Bluetooth was designed for convenience, not security. It’s a short-range communication technology that connects devices like your phone and smartwatch. But here’s the kicker: it’s always searching for other Bluetooth devices to connect with. This “always-on” nature can make it a prime target for cybercriminals. Understanding the basics of Bluetooth security is the first step toward protecting yourself.</p><h3>Common Bluetooth Attacks 🔓</h3><ul><li><strong>Bluejacking</strong>: Think of it as the Bluetooth equivalent of spam. Cybercriminals send unsolicited messages to your device via Bluetooth, often containing links to malicious websites. Annoying, right? But it can also be a gateway to more serious threats.</li><li><strong>Bluesnarfing</strong>: This is where things get serious. Bluesnarfing allows attackers to gain unauthorized access to your device’s data. Once inside, they can steal personal information, photos, contacts, and more. It’s like a digital break-in!</li><li><strong>Bluebugging</strong>: This attack is the sneakiest of them all. Bluebugging gives hackers complete control over your device. They can listen to your calls, send texts, and even access your phone’s data without you knowing. Yikes!</li></ul><h3>How Thieves Exploit Bluetooth: A Peek Behind the Curtain 🕵️‍♂️</h3><p>Here’s a step-by-step look at how thieves might exploit Bluetooth:</p><ol><li><strong>Bluetooth Scanning</strong>: Thieves use tools like HCI Tool to detect discoverable Bluetooth devices around them. This is done by sending out a scan request and receiving responses from devices that are in discoverable mode. They might run commands similar to:</li></ol><pre>hcitool scan</pre><p>This will list all nearby devices and their MAC addresses, which can be used to identify potential targets. 📜</p><ol><li><strong>Device Pairing</strong>: If a device is set to be discoverable, a thief can attempt to pair with it. This involves sending pairing requests and possibly exploiting weak or default pairing codes. Many devices are shipped with default codes, which can be easily guessed or cracked. 🔓</li><li><strong>Data Extraction</strong>: Once paired, thieves might exploit known vulnerabilities to access data. For example, if the Bluetooth stack has a known flaw, it might allow unauthorized access to files or data. In some cases, malware could be delivered via Bluetooth, which then gives attackers a foothold into your device. 😱</li><li><strong>Bluetooth Sniffing</strong>: Using tools like Dragon OS, thieves can intercept Bluetooth traffic to capture data being transmitted between devices. This can include sensitive information like login credentials or personal messages. 📉</li></ol><h3>Protect Yourself: Tips &amp; Tricks 🛡️</h3><p>Here are some practical steps to protect your Bluetooth devices from being exploited:</p><ul><li><strong>Turn Off Bluetooth When Not in Use</strong>: If you’re not using Bluetooth, turn it off. This simple step reduces the risk of your device being discovered and attacked. 📴</li><li><strong>Regularly Update Your Devices</strong>: Firmware and software updates often include important security patches. Keeping your devices updated helps protect against newly discovered vulnerabilities. Check your device manufacturer’s website or settings menu for updates. 🔄</li><li><strong>Use Strong Pairing Codes</strong>: Avoid using default pairing codes. Create unique and complex codes to make it harder for unauthorized users to gain access. For example, instead of “1234,” use a code like “9x5F8#2L.” 🔑</li><li><strong>Monitor Connected Devices</strong>: Regularly review which devices are connected to your Bluetooth. If you notice anything suspicious or unfamiliar, disconnect immediately. This can often be done through your Bluetooth settings or management software. 👀</li><li><strong>Be Cautious with Public Wi-Fi</strong>: Avoid connecting to public Bluetooth networks, as they may be less secure. Instead, use trusted and secured networks whenever possible. 🌐</li><li><strong>Keep Your Devices Non-Discoverable</strong>: Ensure that your device is not set to be discoverable when you’re not pairing it with a new device. Go to your Bluetooth settings and make sure it’s hidden from others:</li><li>On iOS: Go to Settings &gt; Bluetooth and toggle off Bluetooth when you’re not using it.</li><li>On Android: Go to Settings &gt; Connected devices &gt; Bluetooth and toggle off Bluetooth.</li></ul><p>This prevents unauthorized users from detecting your device. 🚫</p><h3>Why It Matters 🎯</h3><p>Bluetooth security isn’t just a techy concern; it’s a real-world issue that affects everyone. Whether you’re listening to music on your morning run or working on a project in a coffee shop, your Bluetooth devices are at risk. By taking a few simple precautions, you can significantly reduce your chances of falling victim to a Bluetooth attack.</p><h3>Additional Resources 📚</h3><p>Want to dive deeper? Here are some great resources to explore:</p><ul><li><a href="https://www.bluetooth.com/bluetooth-resources/bluetooth-security-and-privacy-best-practices-guide/"><strong>Bluetooth SIG Security Resource</strong></a><strong>s</strong>: Official guidelines and updates from the Bluetooth Special Interest Group.</li><li><a href="https://staysafeonline.org/"><strong>StaySafeOnline.org</strong></a>: Tips and advice on staying secure in an increasingly connected world.</li><li><a href="https://csrc.nist.gov/publications/detail/sp/800-121/rev-2/final"><strong>NIST Bluetooth Security Guide</strong></a>: A comprehensive guide from the National Institute of Standards and Technology.</li></ul><h3>Final Thoughts 💭</h3><p>Bluetooth technology has made our lives incredibly convenient, enabling seamless connections between devices. But with that convenience comes responsibility. Understanding the risks and being proactive about your Bluetooth security can make a world of difference. Whether you’re a tech enthusiast or just someone who loves their wireless gadgets, these simple steps can help you enjoy the benefits of Bluetooth without worrying about the dangers lurking in the background. So, take control, stay informed, and keep your digital life secure. 😊🔐</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3429d968f8b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Dark Web Needs You: How to Set Up Your Own Onion Relay ]]></title>
            <link>https://vold3mort.medium.com/the-dark-web-needs-you-how-to-set-up-your-own-onion-relay-f88cc4c1b4f8?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/f88cc4c1b4f8</guid>
            <category><![CDATA[digital-security]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tor-network]]></category>
            <category><![CDATA[online-privacy]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Wed, 12 Jun 2024 19:56:44 GMT</pubDate>
            <atom:updated>2024-06-13T19:32:16.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WktIXdBj3qODjxsZH3JolQ.png" /></figure><p>Welcome aboard! Today, we’re diving into the intriguing world of the dark web, continuing our series exploring its mysteries. Don’t worry, it’s not just about clandestine dealings and covert operations. The dark web serves as a vital refuge for privacy and anonymity online. And guess what? You can contribute to its security and resilience! 🌟”</p><h3>Why the Dark Web?</h3><p>The dark web often gets a bad rap, but it’s a double-edged sword. Sure, it can be home to some sketchy activities, but it’s also a lifeline for millions of people around the world who need to stay safe and anonymous online. Think of journalists in oppressive regimes or whistleblowers. This is where you come in! By running an onion relay, you help keep this network robust and secure.</p><h3>What’s an Onion Relay? 🧅</h3><p>An onion relay is a server that helps form the backbone of the Tor network. Each time someone connects through Tor, their data passes through three of these relays, adding layers of encryption each step of the way — just like an onion! This keeps their data secure and identity anonymous.</p><h3>Your Mission, Should You Choose to Accept It…</h3><p>By running an onion relay, you’ll be joining a community of volunteers who keep the dark web operational. More relays mean better speeds and increased security for the network. Plus, you get to play a crucial part in protecting online privacy worldwide!</p><h3>Safety First! 🚨</h3><p>Now, you might be thinking, “Isn’t this risky?” Well, it depends. There are three types of relays: guard, middle, and exit. Avoid being the exit node; that’s where the police might come knocking. Stick to guard or middle nodes for now — much safer and still super helpful! 🛡️</p><h3>Ready to Roll? Let’s Set It Up! 🛠️</h3><p>Here’s the step-by-step guide to setting up your onion relay. We’re going to use a cloud server for this tutorial, but you can also do it at home if you prefer.</p><h3>Choose Your Cloud Provider ☁️</h3><p><a href="https://www.digitalocean.com/">DigitalOcean</a>, <a href="https://www.linode.com/">Linode</a>, and <a href="https://aws.amazon.com/">AWS</a> are good options. Make sure your provider allows Tor relays. Create a new server (we’re using Ubuntu here). Something with 1GB RAM should do.</p><h3>Connect to Your Server 🌐</h3><p>Once your server is up, grab its IP address and SSH into it:</p><pre>ssh root@your_server_ip</pre><p>This command allows you to remotely access your server from the command line. Replace your_server_ip with the actual IP address of your server.</p><h3>Install Unattended Upgrades 🛠️</h3><p>First, update your package lists to get the latest versions available:</p><pre>sudo apt update</pre><p>Then, install unattended-upgrades and apt-listchanges, which help keep your server automatically updated:</p><pre>sudo apt-get install unattended-upgrades apt-listchanges</pre><p>This command ensures your server stays updated without needing constant manual intervention. Handy, right? 🤓</p><h3>Configure Unattended Upgrades</h3><ol><li><strong>Open the Configuration File</strong></li></ol><pre>sudo nano /etc/apt/apt.conf.d/50unattended-upgrades</pre><p>This opens the configuration file in the Nano text editor, where you’ll make necessary changes.</p><p><strong>2. Modify the Configuration</strong></p><ul><li>Remove the existing configuration:</li></ul><pre>Unattended-Upgrade::Allowed-Origins {<br>  &quot;${distro_id}:${distro_codename}&quot;;<br>  &quot;${distro_id}:${distro_codename}-security&quot;;<br>  &quot;${distro_id}ESMApps:${distro_codename}-apps-security&quot;;<br>  &quot;${distro_id}ESM:${distro_codename}-infra-security&quot;;<br>  &quot;${distro_id}:${distro_codename}-updates&quot;;<br>  &quot;${distro_id}:${distro_codename}~proposed&quot;;<br>  &quot;${distro_id}:${distro_codename}-backports&quot;;<br>};</pre><p>This tells the system where to fetch updates from. We’re removing it to add our custom configuration.</p><ul><li>Add the new configuration:</li></ul><pre>Unattended-Upgrade::Allowed-Origins {<br>  &quot;${distro_id}:${distro_codename}-security&quot;;<br>  &quot;TorProject:${distro_codename}&quot;;<br>};<br>Unattended-Upgrade::Package-Blacklist {<br>};<br>Unattended-Upgrade::Automatic-Reboot &quot;true&quot;;</pre><p>Here, we’re specifying that the system should automatically update security patches and include updates from the Tor Project. The automatic reboot ensures your server applies updates promptly.</p><p><strong>3. Test Unattended Upgrades</strong></p><pre>unattended-upgrade --debug</pre><p>This command runs a test to make sure unattended upgrades are set up correctly. Debug mode gives you detailed output.</p><h3>Install Tor 🌐🧅</h3><ol><li><strong>Add Official Tor Repositories</strong></li></ol><ul><li>Install prerequisites:</li></ul><pre>sudo apt install apt-transport-https</pre><p>This package allows APT to use repositories accessed via the HTTP Secure protocol.</p><ul><li>Find your Debian version:</li></ul><pre>sudo cat /etc/debian_version</pre><p>This command outputs your Debian version, which you’ll need for the next step.</p><ul><li>Create a new sources file:</li></ul><pre>sudo nano /etc/apt/sources.list.d/tor.list</pre><p>This command opens a new file where you’ll add the Tor repository URLs.</p><ul><li>Add these repositories, replacing {yourdistro} with your Debian version:</li></ul><pre>sudo deb [signed-by=/usr/share/keyrings/tor-archive-keyring.gpg] https://deb.torproject.org/torproject.org {yourdistro} main<br>sudo deb-src [signed-by=/usr/share/keyrings/tor-archive-keyring.gpg] https://deb.torproject.org/torproject.org {yourdistro} main</pre><p>These lines tell APT where to find the Tor Project packages.</p><p><strong>2. Add the GPG Key</strong></p><pre>wget -qO- https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc | gpg --dearmor | tee /usr/share/keyrings/tor-archive-keyring.gpg &gt;/dev/null</pre><p>This command fetches the GPG key, which verifies the authenticity of the packages from the Tor Project. It’s like ensuring your email comes from a trusted source.</p><p><strong>3. Install Tor</strong></p><pre>sudo apt update<br>sudo apt install tor deb.torproject.org-keyring</pre><p>This updates your package list again to include the new Tor repository and installs Tor along with its keyring.</p><h3>Configure Tor ⚙️</h3><ol><li><strong>Open the Tor Configuration File</strong></li></ol><pre>sudo nano /etc/tor/torrc</pre><p>This opens the main configuration file for Tor.</p><p><strong>2. Add the Following Configuration</strong></p><ul><li>Base Configuration:</li></ul><pre>Nickname your_relay_name<br>ContactInfo your_email@domain.com<br>ORPort 443<br>ExitRelay 0<br>SocksPort 0</pre><p>Here, you set your relay’s nickname, contact info (in case the Tor project needs to reach you), and specify that it won’t act as an exit relay.</p><h3>Set Bandwidth Limits (Optional) 🚦</h3><ul><li>Bandwidth Limits:</li></ul><pre>AccountingMax 100 GB<br>AccountingStart month 1 00:00</pre><p>These settings help you control how much bandwidth your relay uses, so you don’t end up with a massive bill.</p><ul><li>Monitoring:</li></ul><pre>ControlPort 9051<br>CookieAuthentication 1</pre><p>This allows you to monitor and control your Tor relay with tools that support the Tor control protocol.</p><h3><strong>Enable and Restart Tor </strong>⏳</h3><pre>sudo systemctl enable tor<br>sudo systemctl restart tor</pre><p>These commands ensure Tor starts on boot and restarts Tor to apply the new configuration.</p><h3>Why Not Be an Exit Node? 🚫</h3><p>Running an exit node can attract legal trouble because any traffic exiting the Tor network will appear to come from your IP address. Stick to guard or middle nodes to avoid complications.</p><h3>Wrapping Up 🎁</h3><p>Congratulations! 🎉 You’ve just set up your very own onion relay, contributing to a safer, more secure internet. Pat yourself on the back and maybe enjoy some coffee and popcorn. ☕🍿</p><p>For more detailed steps and updates, check out the<a href="https://tb-manual.torproject.org/about/"> Tor Project’s official documentation</a>.</p><p>By following this guide, you’re not just learning new skills, but also making a meaningful contribution to global online privacy and freedom. Welcome to the community of Tor relay operators🌐🧅✨!</p><p><em>If you found this guide helpful, give it some appreciation and share it with your friends. Let’s make the internet a better place, one onion at a time!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f88cc4c1b4f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Putting Your Website on the Dark Web: A Fun and Secure Adventure]]></title>
            <link>https://vold3mort.medium.com/putting-your-website-on-the-dark-web-a-fun-and-secure-adventure-c37ce72ebac5?source=rss-19348ce5fa19------2</link>
            <guid isPermaLink="false">https://medium.com/p/c37ce72ebac5</guid>
            <category><![CDATA[internet-privacy]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[darkweb]]></category>
            <category><![CDATA[website-hosting]]></category>
            <dc:creator><![CDATA[Voldemort]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 08:48:13 GMT</pubDate>
            <atom:updated>2024-06-06T08:48:13.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*92OhJYWbHAZs11v0BFpdQQ.png" /><figcaption>Going dark, one server at a time.</figcaption></figure><p>Hey there, internet explorers! 🌍 Ever wondered how to put your website on the dark-web? In just a few minutes, you’ll learn not only how to set up your very own dark-web website but also how to create secret chat sessions and share files securely. Sounds wild, right? Well, it is, and it’s super fun too. So, grab your coffee ☕ and let’s dive in!</p><h3>Why Should You Do This? 🤔</h3><p>First off, it’s a cool way to learn about the dark-web and the Tor network. The dark-web is often misunderstood as a hub for illicit activities, but it also serves as a platform for privacy-conscious individuals, journalists, activists, and those seeking uncensored communication channels. Hosting your resume or portfolio on the dark-web is a geeky flex that potential employers might find intriguing. It shows you’re curious and tech-savvy-a win-win! Plus, who doesn’t want to be a part of the edgy dark-web club? 😉</p><h3>Tools You’ll Need 🛠️</h3><p>To embark on this dark-web journey, you’ll need a couple of tools:</p><ul><li><strong>OnionShare:</strong> This nifty tool allows you to host websites, chat anonymously, and share files on the dark-web. It leverages the Tor network, ensuring your activities remain private and secure. You can install it on various operating systems, including Windows, Mac, Linux, iOS, and Android. Check it out <a href="https://onionshare.org/">here</a>! 📁🔒</li><li><strong>Tor Browser:</strong> Essential for accessing your dark-web site. Tor Browser routes your internet traffic through the Tor network, concealing your IP address and making it difficult for anyone to trace your online activities. Download it from <a href="https://www.torproject.org/">Tor Project</a> and explore anonymously! 🕵️‍♂️🔍</li></ul><h3>Setting Up Your Dark Web Light 💡</h3><ol><li><strong>Install OnionShare:</strong> OnionShare simplifies the process of hosting a website on the dark-web. For Linux users, open your terminal and execute the following commands:</li></ol><pre>sudo apt update <br>sudo apt install snapd <br>sudo snap install onionshare</pre><p>Windows users can download OnionShare directly from the website and follow the installation prompts.</p><p><strong>2. Launch OnionShare and Connect to the Tor Network:</strong> Once OnionShare is installed, launch the application and connect to the Tor network. Tor ensures your internet traffic is encrypted and routed through multiple servers, enhancing your anonymity online.</p><p><strong>3. Start Hosting Your Site:</strong> Hosting your site on the dark-web is as easy as dragging and dropping your website files into OnionShare. OnionShare will generate a unique .onion address for your site, making it accessible via the Tor Browser. If you want your site to be public, simply uncheck the “Not Public” option before starting sharing.</p><p>Voila! Your site is now live on the dark-web, ready to be explored by users across the globe. 🌐</p><h3>Creating a Secret Chat Session 🗣️</h3><p>For those clandestine conversations:</p><ol><li><strong>In OnionShare CLI:</strong> If you prefer the command line interface, OnionShare CLI allows you to create secret chat sessions effortlessly. Open your terminal and execute the following command:</li></ol><pre>onionshare-cli chat --public</pre><p><strong>2. Access the Chat:</strong> Share the provided .onion address with your desired participants. They can use Tor Browser to access the chat session securely.</p><p>Now you have a super secure chat session that nobody can spy on. 🔐</p><h3>Sharing Files Securely 📁</h3><p>Want to share a file? Easy peasy 🍋.</p><ol><li><strong>In OnionShare GUI:</strong> OnionShare’s graphical user interface simplifies file sharing on the dark-web. Select the file you want to share, and OnionShare will generate a unique .onion link for it. Share this link with your intended recipient, and they can download the file securely via Tor Browser.</li></ol><h3>Going Dark Web Supreme 🥇</h3><p>Ready to take it up a notch? Here’s how to set up a permanent dark-web website with a custom onion domain.</p><ol><li><strong>Get a Linux Server:</strong> To host a permanent dark-web website, you’ll need a Linux server. You can opt for a cloud service provider like <a href="https://aws.amazon.com/">AWS</a>, <a href="https://www.digitalocean.com/">DigitalOcean</a>, or host it locally on your machine using software like <a href="https://www.virtualbox.org/">VirtualBox</a>.</li><li><strong>Install Nginx:</strong> Nginx is a high-performance web server that will serve as the backbone of your dark-web site. Install Nginx on your Linux server by executing the following commands:</li></ol><pre>sudo apt update <br>sudo apt install nginx</pre><p>After installation, ensure Nginx is running by executing:</p><pre>sudo systemctl status nginx</pre><p>If it’s not running, just yell at it. Kidding! You know what to do. 😉</p><p><strong>3. Clone Your Website Repository <em>(Skip If You Have Files Stored Locally)</em>:</strong> If you haven’t already, clone your website repository containing all your site’s files and assets onto your Linux server. Navigate to the desired directory and execute:</p><pre>git clone https://github.com/your_repo/darkweb-site.git <br>cd darkweb-site</pre><p><strong>4. Copying Your Website Files into Nginx Server Folder:</strong> After cloning your website repository, you need to copy the files into the Nginx server folder so that Nginx can serve them.</p><pre><br>cp -r /path/to/your-website /var/www/</pre><p><strong>5. Configure Nginx:</strong> Open the Nginx configuration file in a text editor. For example, using nano:</p><pre>sudo nano /etc/nginx/sites-available/default</pre><p>Within the configuration file, locate the root directive and modify it to point to your site’s folder. For example:</p><p>Default config is</p><pre>server {<br>    ...<br>    root /var/www/html; <br>    ...<br>}</pre><p>So change it to /var/www/<em>~your_dark_web_site_directory</em></p><pre>server {<br>    ...<br>    root /var/www/your_dark_web_site_directory; <br>    ...<br>}</pre><p>Save and close the file.</p><p>6.<strong> Install Tor: </strong>To make your site accessible on the dark-web, you need to install Tor and configure it to serve your hidden service. Install Tor:</p><pre>sudo apt update<br>sudo apt install tor</pre><p>7. <strong>Configure </strong><strong>torrc:</strong></p><p>Open the torrc file in a text editor:</p><pre>sudo nano /etc/tor/torrc</pre><p>Add the following lines to the end of the file to configure your hidden service:</p><pre>HiddenServiceDir /var/lib/tor/hidden_service/<br>HiddenServicePort 80 127.0.0.1:80</pre><p>This configuration tells Tor to create a hidden service that redirects traffic from port 80 of your .onion address to port 80 of your local server.</p><p>Restart the Tor service to apply the changes:</p><pre>sudo systemctl restart tor</pre><p>After restarting Tor, it will generate your .onion address and store it in the /var/lib/tor/hidden_service/ directory. You can find your new .onion address by looking at the hostname file in that directory:</p><pre>sudo cat /var/lib/tor/hidden_service/hostname</pre><p>Now, you can access your permanent dark-web website using the generated .onion address. 😎</p><h3>Bonus: Creating a Custom .onion Address 🎉</h3><p>Feeling adventurous? Let’s set up a custom .onion address for your dark-web site.</p><p>1. <strong>Install mkp224o:</strong> First, we need to install mkp224o, a tool for generating custom V3 onion addresses. Execute the following commands:</p><pre>sudo apt update<br>sudo apt install build-essential git libssl-dev<br>git clone https://github.com/cathugger/mkp224o.git<br>cd mkp224o<br>make</pre><p>2. <strong>Generate Custom .onion Address:</strong> Now, decide on your custom domain name and execute the following command, replacing YourName with your desired name:</p><pre>./mkp224o YourName -v -n 1 -d ~/your_custom_onion_directory -t 4</pre><p>Explanation of the flags used:</p><ul><li>-v: Verbose mode to see the process.</li><li>-n 1: Specify to generate only one address.</li><li>-d ~/your_custom_onion_directory: Specify the directory where the generated keys will be stored.</li><li>-t 4: Use four CPU threads for faster processing. You can adjust this based on your system&#39;s capabilities.</li></ul><p>Once generated, you will see your new .onion domain in the output, and it will be saved to the directory of your choice.</p><p>3. <strong>Replace Necessary Files:</strong> Copy the necessary files to the Tor hidden service directory to replace the existing ones:</p><pre>sudo cp -r ~/your_custom_onion_directory/* /var/lib/tor</pre><p><strong>4. Restart Tor:</strong> Finally, restart the Tor service to apply the changes:</p><pre>sudo systemctl restart tor</pre><p>Now, your dark-web site is accessible via your custom .onion domain. 🌐</p><h3>Conclusion</h3><p>And there you have it! You’ve just created your very own dark-web website, set up secret chat sessions, and learned how to share files securely. Whether you’re showcasing your portfolio or just experimenting, the dark-web can be a fascinating place to explore your tech skills. Don’t forget to like, share, and subscribe for more cool tech adventures. Until next time, stay curious and keep exploring! 🚀🔍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c37ce72ebac5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>