<?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 Red on Medium]]></title>
        <description><![CDATA[Stories by Red on Medium]]></description>
        <link>https://medium.com/@coderedblog?source=rss-6f6340d4b20d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XXy7fOdCVl3VV3_1r3wO9Q.png</url>
            <title>Stories by Red on Medium</title>
            <link>https://medium.com/@coderedblog?source=rss-6f6340d4b20d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:38:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@coderedblog/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[Linux Capture The Flag Bandit Level 23]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-23-e9e3022ecb1e?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9e3022ecb1e</guid>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Fri, 16 Oct 2026 23:04:32 GMT</pubDate>
            <atom:updated>2026-10-16T23:04:32.505Z</atom:updated>
            <content:encoded><![CDATA[<h4>Writing Your First Bash Script</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUz0DSaXMEDAS7nvc0F5GQ.jpeg" /></figure><p>Bandit Level 23 is a milestone. Every level up to this point has involved reading scripts, understanding cron jobs, and working with existing tools — but this is the first level where you have to write a script yourself. It’s a bigger step than it might sound, and once you crack it, you’ve crossed into territory that matters a lot in both offensive and defensive security work.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fm3-i-_m_hCM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dm3-i-_m_hCM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fm3-i-_m_hCM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d55fcb22e9649e6ef267952b86fa702e/href">https://medium.com/media/d55fcb22e9649e6ef267952b86fa702e/href</a></iframe><h3>The Challenge</h3><p>A cron job is running automatically every minute as user bandit24. Your job is to figure out what that script does, write your own bash script that takes advantage of it, place that script where the cron job will find it, and let it run — capturing the Level 24 password in the process.</p><p>One important note from the level description: <strong>your script is deleted after it executes</strong>, so if you want to keep a copy, save it somewhere before it gets picked up.</p><h3>Step 1: Find the Cron Job</h3><p>Navigate to the cron directory, list the cronjobs to see if there is one for bandit 24, and then list it to check what’s configured for bandit24:</p><pre>cd /etc/cron.d<br>ls<br>cat cronjob_bandit24</pre><p>The output confirms: the script runs every minute (* * * * *), it runs as bandit24, and it points to /usr/bin/cronjob_bandit24.sh.</p><h3>Step 2: Read the Script</h3><p>Open the script to understand what it does. I prefer to use nano as my text editor. You can also just use the cat command to print it on your terminal:</p><pre>nano /usr/bin/cronjob_bandit24.sh</pre><p>Using nano instead of cat gives you syntax highlighting, which makes bash scripts easier to read at a glance.</p><p>Here’s what the script does:</p><pre>#!/bin/bash<br>shopt -s nullglob<br>myname=$(whoami)<br>cd /var/spool/$myname/foo<br>echo &quot;Executing and deleting all scripts in /var/spool/$myname/foo:&quot;<br>for i in *; do<br>    if [ &quot;$i&quot; != &quot;.&quot; ] &amp;&amp; [ &quot;$i&quot; != &quot;..&quot; ]; then<br>        echo &quot;Handling $i&quot;<br>        owner=$(stat --format &quot;%U&quot; ./$i)<br>        if [ &quot;${owner}&quot; = &quot;bandit23&quot; ]; then<br>            timeout -s 9 60 ./$i<br>        fi<br>        rm -f ./$i<br>    fi<br>done</pre><p><strong>IF YOU DO NOT UNDERSTAND THIS, YOU CAN GOOGLE IT.</strong> You do not have to know everything about programming and how to write scripts. You can research what each thing means to understand it. I’ve broken it down for you below:</p><ul><li><strong>shopt -s nullglob</strong> — A shell option that prevents the for loop from choking on an empty directory. If no files match the pattern, the loop simply doesn&#39;t run rather than throwing an error.</li><li><strong>myname=$(whoami)</strong> — Since this runs as bandit24, myname equals bandit24. That’s an important thing to pay attention to. When the cronjob is listed, it says it is ran as a certain user, which is bandit24 as opposed to bandit23 even through we are logged in as that.</li><li><strong>cd /var/spool/$myname/foo</strong> — The script changes into /var/spool/bandit24/foo.</li><li><strong>The </strong><strong>for loop</strong> — Iterates over every file in that directory, checks whether it&#39;s owned by bandit23, and if so, executes it with a 60-second timeout. After execution, it deletes the file.</li></ul><p>The important thing is that <strong>the cron job will execute any script in </strong><strong>/var/spool/bandit24/foo that is owned by </strong><strong>bandit23</strong> — and since you&#39;re logged in as bandit23, any file you create there is owned by you. This is the exploit.</p><h3>Step 3: Set Up a Working Directory</h3><p>Create a temporary working directory and make sure the cron job can write results into it:</p><pre>mkdir -p /tmp/codered-work<br>chmod -R 777 /tmp/codered-work</pre><p>The 777 permission gives read, write, and execute access to all users — necessary because the cron job runs as bandit24, and it needs to be able to write the password file into your directory.</p><p>To be honest, 777 is more permissive than you&#39;d ever want in a real environment. For this challenge it&#39;s fine, but in production, you&#39;d use the minimum permissions required.</p><p>This temporary workspace in the /tmp directory gives us a spot to reference in the script we will write.</p><h3>Step 4: Write the Script</h3><p>Navigate into your working directory and create the script:</p><pre>cd /tmp/codered-work<br>nano dump.sh</pre><p>This is part is not as hard as you may think. Basically we want to make sure the script prints the password into a file it creates in our working directory, and then changes the permissions of that file so that any user can read and write to it. The script should have the following:</p><pre>#!/bin/bash<br>cat /etc/bandit_pass/bandit24 &gt; /tmp/codered-work/pass24.txt<br>chmod 777 /tmp/codered-work/pass24.txt</pre><p>What this does:</p><ol><li>Reads the Level 24 password from /etc/bandit_pass/bandit24</li><li>Writes it into pass24.txt in your working directory</li><li>Sets permissions on the output file so you can read it (since bandit24 created it, you need it to be world-readable)</li></ol><p>Save and exit nano.</p><h3>Step 5: Make the Script Executable</h3><p>The cron job needs to be able to execute your script, so set its permissions:</p><pre>chmod 777 dump.sh</pre><h3>Step 6: Copy the Script Into Place</h3><p>Copy your script into the directory the cron job monitors:</p><pre>cp /tmp/codered-work/dump.sh /var/spool/bandit24/foo/dump.sh</pre><p>The script is now sitting in /var/spool/bandit24/foo, owned by bandit23, with execute permissions. The cron job will pick it up within the next 60 seconds.</p><h3>Step 7: Wait and Read the Result</h3><p>Wait a full minute, then check your working directory:</p><pre>ls /tmp/codered-work</pre><p>You should see pass24.txt has appeared. Read it:</p><pre>cat /tmp/codered-work/pass24.txt</pre><p>That’s the password for Level 24. Copy it into your notes. BOOM!</p><h3>Key Concepts Covered</h3><ul><li>#!/bin/bash The “sh-bang” line — tells the system what interpreter to use for the script</li><li>shopt -s nullglob Prevents a for loop from breaking when the target directory is empty</li><li>for i in *; do ... done A for loop that iterates over every file in the current directory</li><li>stat --format &quot;%U&quot; &lt;file&gt; Returns the username of the file’s owner</li><li>chmod 777 &lt;file&gt; Grants read, write, and execute to owner, group, and all others</li><li>mkdir -p &lt;path&gt; Creates a directory and any necessary parent directories</li><li>cp &lt;source&gt; &lt;destination&gt; Copies a file from one location to another</li></ul><p>This level introduces a concept that shows up constantly in penetration testing: <strong>abusing automated processes</strong>. If a scheduled job runs as a privileged user and executes files from a directory you can write to, you can inject your own code and have it run with that user’s permissions. That’s a privilege escalation path.</p><p>Writing your own script to complete a challenge is also a genuine skill checkpoint. Bash scripting is foundational to Linux security work — from automation and tooling to writing custom exploits and recon programs.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9e3022ecb1e" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-23-e9e3022ecb1e">Linux Capture The Flag Bandit Level 23</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Capture The Flag Bandit Level 22]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-22-1ad57bb1ade2?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ad57bb1ade2</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 22:19:41 GMT</pubDate>
            <atom:updated>2026-10-09T22:19:41.568Z</atom:updated>
            <content:encoded><![CDATA[<h4>Reading and Reverse Engineering a Bash Script</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*njTeDp0r5A-UmLWGx4JPlA.jpeg" /></figure><p>Bandit Level 22 builds directly on the previous level’s cron job concept, but adds a twist: instead of just reading a file that cron writes, you have to understand what a bash script is doing and then replicate its logic yourself to figure out where the password is stored. It takes some patience, but it’s a genuinely useful exercise in reading code written by someone else.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzrfNHp3Qo8c%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzrfNHp3Qo8c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzrfNHp3Qo8c%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe2fbc88bc6367ea74f3ef00fb2344e0/href">https://medium.com/media/fe2fbc88bc6367ea74f3ef00fb2344e0/href</a></iframe><h3>The Challenge</h3><p>Just like Level 21, a cron job is running automatically at regular intervals. The task is to find the cron configuration, read the script it’s running, understand what it does, and use that understanding to locate the password for Level 23.</p><h3>Step 1: Find the Cron Job</h3><p>Navigate to the cron directory and look for the relevant configuration:</p><pre>cd /etc/cron.d<br>ls<br>cat cronjob_bandit23</pre><p>The output shows that a script at /usr/bin/cronjob_bandit23.sh is being executed automatically, running as user bandit23. Errors and output are redirected to /dev/null.</p><h3>Step 2: Read the Script</h3><p>Open the script to see what it’s doing:</p><pre>cat /usr/bin/cronjob_bandit23.sh</pre><p>Using a text editor like nano instead of cat is something I like to do— editors with syntax highlighting color-code variables, commands, and strings makes bash scripts easier to read at a glance.</p><p>The script is written in bash. This is typical in Linux environments. Understanding how to read and write bash scripts is a useful for almost anyone in cybersecurity.</p><p>The script does the following:</p><pre>myname=$(whoami)<br>mytarget=$(echo I am user $myname | md5sum | cut -d &#39; &#39; -f 1)<br>echo &quot;Copying passwordfile /etc/bandit_pass/$myname to /tmp/$mytarget&quot;<br>cat /etc/bandit_pass/$myname &gt; /tmp/$mytarget</pre><p>Breaking this down step by step:</p><ul><li>myname=$(whoami)— Sets a variable called myname to the result of whoami. When the cron job runs as bandit22, this variable equals bandit22.</li><li>mytarget=$(echo I am user $myname | md5sum | cut -d ‘ ‘ -f 1)— This creates a second variable called mytarget. It takes the string &quot;I am user bandit22&quot;, pipes it through md5sum to generate an MD5 hash, then uses cut to strip the trailing space and keep only the hash string.</li><li>echo “Copying passwordfile /etc/bandit_pass/$myname to /tmp/$mytarget”— This reads the password for bandit22 and writes it into a file in /tmp whose name is the MD5 hash generated in step 2.</li></ul><p>In short: the script is running as bandit22, generating a predictable filename based on an MD5 hash of the string &quot;I am user bandit22&quot;, and writing the Level 22 password to that file.</p><h3>Step 3: Reproduce the Logic to Find the File</h3><p>The script runs as bandit22 since you&#39;re logged in as bandit22, you can&#39;t just run it and have whoami return bandit23. Instead, you replicate the relevant part of the script manually, substituting bandit23 for the username:</p><pre>echo I am user bandit23 | md5sum | cut -d &#39; &#39; -f 1</pre><p>This gives you the MD5 hash that the cron job uses as the filename. Copy that hash.</p><h3>Step 4: Read the Password File</h3><p>The cron job has already been running automatically, so the file already exists in /tmp. Read it:</p><pre>cat /tmp/&lt;hash from previous step&gt;</pre><p>That’s the password for Level 23. Copy it into your notes.</p><h3>Key Concepts Covered</h3><ul><li>$(command) Command substitution — stores the output of a command in a variable</li><li>variable=$value Bash variable assignment</li><li>$variable Calling a variable’s value in bash</li><li>md5sum Generates an MD5 hash of input</li><li>cut -d &#39; &#39; -f 1 Splits on a space delimiter and returns the first field</li><li>/dev/null Discards all output sent to it</li></ul><p>This level is a great introduction to reading bash scripts written by others — a skill that comes up constantly in security work. Whether you’re reviewing a cron job on a server you’re assessing, analyzing a suspicious script, or understanding what automation is doing in a Linux environment, being able to read and reason through bash code is invaluable.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ad57bb1ade2" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-22-1ad57bb1ade2">Linux Capture The Flag Bandit Level 22</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Capture The Flag Bandit Level 21]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-21-4688b8280261?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4688b8280261</guid>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 21:45:22 GMT</pubDate>
            <atom:updated>2026-10-07T21:45:22.419Z</atom:updated>
            <content:encoded><![CDATA[<h4>Understanding Cron Jobs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQHB4wlOKewcgUZqy1lhgQ.jpeg" /></figure><p>Bandit Level 21 introduces <strong>cron</strong> — one of the most useful and widely used tools in Linux system administration. The challenge asks you to look at what a cron job is doing and use that knowledge to find the password. It’s a great example of how understanding your environment is often all you need to move forward.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyI3RvUTqT5c%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyI3RvUTqT5c&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyI3RvUTqT5c%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4b9d6b6f9a665c1fccdeb386623ed24e/href">https://medium.com/media/4b9d6b6f9a665c1fccdeb386623ed24e/href</a></iframe><h3>The Challenge</h3><p>The level description says a program is running automatically at regular intervals via cron. The task is to look in /etc/cron.d to find the configuration and figure out what command is being executed.</p><h3>What Is Cron?</h3><p>Cron is a Linux utility that lets you schedule scripts or commands to run automatically at specified intervals. You define the schedule and the command, and cron handles the execution.</p><p>What cron can be used for in the real world:</p><ul><li>Automated backups that run every Friday night</li><li>Security log audits that run hourly and email results to an admin</li><li>Database cleanups that run on the first of every month</li></ul><p>It’s one of those tools that makes Linux administration genuinely powerful.</p><h3>Step 1: Examine the Cron Configuration</h3><p>Navigate to the cron directory and list its contents:</p><pre>cd /etc/cron.d<br>ls</pre><p>You’ll see a file called cronjob_bandit22. Open it to see what it contains:</p><pre>cat cronjob_bandit22</pre><p>The file shows a cron entry that looks something like this:</p><pre>* * * * * bandit22 /usr/bin/cronjob_bandit22.sh &amp;&gt;/dev/null</pre><p>Breaking this down:</p><ul><li>The five * symbols represent the schedule fields in cron syntax: minute, hour, day of month, month, and day of week. Five stars means this job runs <strong>every minute</strong>.</li><li>bandit22 is the user the job runs as</li><li>/usr/bin/cronjob_bandit22.sh is the script being executed</li><li>&amp;&gt;/dev/null redirects any output or errors to /dev/null — Linux&#39;s version of a void where data disappears</li></ul><h3>Step 2: Read the Script</h3><p>Now look at what the script itself is doing:</p><pre>cat /usr/bin/cronjob_bandit22.sh</pre><p>The script does two things:</p><ol><li>Changes the permissions of a file in /tmp to 644 — which means everyone on the system can read it</li><li>Prints the contents of /etc/bandit_pass/bandit22 (the Level 22 password) into that same file</li></ol><p>In other words, every single minute, this cron job is automatically writing the Level 22 password into a readable file in the /tmp directory.</p><h3>Step 3: Read the Password File</h3><p>The script writes the password to a file with a long random-looking name in /tmp. You can see the exact filename in the script.</p><pre>cat /tmp/&lt;filename from script&gt;</pre><p>That’s the Level 22 password. Copy it into your notes, log in as bandit22 to confirm it works, and you&#39;re done.</p><h3>Key Commands Covered</h3><ul><li>ls /etc/cron.d List scheduled cron jobs</li><li>cat &lt;cron file&gt; View a cron job’s schedule and command</li><li>cat &lt;script&gt; Read the script the cron job executes</li><li>* * * * * Cron syntax meaning “run every minute”</li><li>/dev/null Linux’s void — output sent here is discarded</li></ul><p>This level is a good introduction to why cron jobs matter in security. Scheduled tasks running automatically in the background are easy to forget about, and if they’re misconfigured — like writing sensitive data to a world-readable file — they can become a significant vulnerability. During a penetration test on a Linux machine, reviewing cron jobs is a standard step. You never know what a scheduled script might be doing, or what permissions it’s running with.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4688b8280261" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-21-4688b8280261">Linux Capture The Flag Bandit Level 21</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Not To Get Hacked Part 3]]></title>
            <link>https://meetcyber.net/how-not-to-get-hacked-part-3-4ef31990ee72?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ef31990ee72</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[microsoft]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 05:15:24 GMT</pubDate>
            <atom:updated>2026-10-06T05:15:24.879Z</atom:updated>
            <content:encoded><![CDATA[<h4>Computer, Finally Secured</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vkjKetH-k6fqVEZRWD3Nig.jpeg" /></figure><p>Welcome to part three of the Windows security checklist series. Parts <a href="https://medium.com/meetcyber/how-not-to-get-hacked-aaf2c8d48bae">one</a> and <a href="https://meetcyber.net/how-not-to-get-hacked-part-2-1c795a7b5c1e">two </a>focused on hardening things within the Windows operating system itself — patches, encryption, unused apps, open ports, Wi-Fi, VPNs, and user permissions. This time we’re going a level deeper, looking at the hardware layer and a few final critical steps to round out your security posture.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FlXC2ConkGaA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DlXC2ConkGaA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FlXC2ConkGaA%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/cad7c158ee53d6155ca480bca7496e92/href">https://medium.com/media/cad7c158ee53d6155ca480bca7496e92/href</a></iframe><h3>1. Update Your BIOS</h3><p>Most people know to update Windows, but the BIOS often gets overlooked. The BIOS (or more accurately, UEFI on modern systems) is the base-level firmware that lives on your computer’s hardware and runs before the operating system even loads. Keeping it updated is just as important as keeping Windows updated — BIOS updates can include security patches that close vulnerabilities at the hardware level.</p><p>Most major computer manufacturers — Lenovo, HP, Dell, and others — have their own software utilities that make checking for BIOS updates straightforward. Build this into the same routine as your Windows updates. Pick one day a week — Friday works well — and make it the day you check for updates across the board: Windows, BIOS, and your applications.</p><h3>2. Enable Secure Boot</h3><p>While you’re thinking about the BIOS, make sure <strong>Secure Boot</strong> is enabled. This setting is found in the BIOS/UEFI interface, which you access by pressing a specific key as your computer starts up — the key varies by manufacturer, so search your computer model to find out which one it is (often F2, F12, or Escape).</p><p>Here’s why Secure Boot matters: attackers can plant <strong>kernel-level rootkits</strong> on a computer — malware that loads before the operating system does. Because it loads first, Windows can’t detect it after it’s up and running. Secure Boot prevents this by verifying that only trusted, signed software is allowed to load during the boot process. It checks that the operating system itself is legitimate and blocks anything unauthorized from running before Windows loads.</p><h3>3. Run Vulnerability Scans Regularly</h3><p>Updating your system reduces known vulnerabilities, but running a vulnerability scan confirms it. Do this at least once a month. Here’s why the frequency matters: a new Windows update might patch one vulnerability but inadvertently re-enable a Windows feature you had turned off, or introduce a new issue you weren’t expecting. A regular scan catches these things.</p><p>Two tools worth using:</p><p><strong>Nessus by Tenable</strong> — one of the most widely used vulnerability scanners in the industry, and free for personal use. It provides a detailed breakdown of what it finds and guidance on how to remediate issues.</p><p><strong>Zenmap</strong> — the graphical interface version of Nmap, which runs on Windows. To run a vulnerability scan against your own machine, set the target to localhost and use the following flags:</p><pre>nmap -sC -T4 localhost</pre><ul><li>-sC activates the Nmap scripting engine, which runs a set of scripts specifically designed to detect vulnerabilities</li><li>-T4 sets the scan speed to a reasonable level</li></ul><p>Hit scan and review the results. Anything flagged as a vulnerability is worth researching and addressing.</p><h3>4. Make Sure Your Firewall Is On</h3><p>There’s a common misconception that a firewall on your router is all you need. It isn’t. Your router’s firewall protects the network perimeter — what comes in from the internet. Your computer’s firewall protects the device itself from traffic that’s already on the network. You need both, and they serve different purposes.</p><p>Windows has a built-in firewall called <strong>Windows Defender Firewall</strong>. To check it, type “firewall” in the search bar and open <strong>Windows Defender Firewall with Advanced Security</strong>.</p><p>You’ll see three profiles:</p><ul><li><strong>Public</strong> — for networks like coffee shops, airports, or anywhere with unknown users</li><li><strong>Private</strong> — for your home or trusted office network</li><li><strong>Domain</strong> — for environments connected to a Windows Active Directory domain</li></ul><p>Make sure the firewall is <strong>on for all three profiles</strong>. This comes up surprisingly often during security assessments — it’s not unusual to find one or more profiles disabled, sometimes without the user even knowing it happened. Go check right now. If any profile shows the firewall as off, click Properties for that profile and turn it on.</p><h3>5. Keep Your Browser Updated</h3><p>Windows Update handles the operating system, but it doesn’t necessarily update all the software installed on your computer — including your browser. Browsers are a major attack surface. They’re your primary interface with the internet, and there is an entire discipline within security dedicated to web application vulnerabilities and browser-based attacks.</p><p>Whatever browser you use — Chrome, Brave, Firefox, Edge — check for updates regularly and keep it current. Make browser updates part of the same weekly routine as your other updates. It takes less than a minute and closes vulnerabilities that attackers actively exploit.</p><p>None of these steps require advanced technical knowledge. They’re base-level actions that anyone can take to meaningfully reduce their attack surface and make it significantly harder for attackers to get into their stuff. Do them, keep doing them, and stay ahead of it.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ef31990ee72" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/how-not-to-get-hacked-part-3-4ef31990ee72">How Not To Get Hacked Part 3</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Capture The Flag Bandit Level 20]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-20-4428e9ca231c?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4428e9ca231c</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 18:14:42 GMT</pubDate>
            <atom:updated>2026-10-02T18:43:21.061Z</atom:updated>
            <content:encoded><![CDATA[<h4>Netcat Listeners, Background Processes, and SetUID Binaries</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0CcAWmlF8-oM8waw-3Y01w.jpeg" /></figure><p>Bandit Level 20 builds on two concepts from previous levels — SetUID binaries and Netcat — and combines them into a challenge that requires two things to happen simultaneously on the same machine. It’s a great exercise in understanding how processes and network connections work together in Linux.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJ6fhZyMfD1w%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJ6fhZyMfD1w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJ6fhZyMfD1w%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/22c1eff27c50e8246c3d9dcbe3637a30/href">https://medium.com/media/22c1eff27c50e8246c3d9dcbe3637a30/href</a></iframe><h3>The Challenge</h3><p>There’s another SetUID binary in the home directory called suconnect. Here&#39;s what it does:</p><ol><li>It connects to localhost on a port you specify</li><li>It reads a line of text from that connection</li><li>It compares that text to the Level 20 password</li><li>If it matches, it sends back the Level 21 password</li></ol><p>In other words, you need to set up a listener on a port that has the Level 20 password ready to send, and then point suconnect at that port. The binary does the rest.</p><h3>The Tools: Netcat and the &amp; Operator</h3><h4>Netcat as a Listener</h4><p>You’ve used Netcat before to connect to ports. This time you’re using it in <strong>server mode</strong> — having it listen for an incoming connection rather than initiate one. Two flags make this work:</p><ul><li>-l — listen for an incoming connection</li><li>-p — specify the port to listen on</li></ul><p>This is exactly how Netcat is used in real penetration testing. When exploiting a vulnerable machine, a common technique is to set up a Netcat listener on your attack box, trigger an exploit on the target that sends a connection back to you, and catch a reverse shell when it arrives. The concept here is the same — just on localhost.</p><h4>The &amp; Operator</h4><p>Running two things at once from a single terminal requires one of them to run in the <strong>background</strong>. In Linux, appending &amp; to a command does exactly that — it starts the process and returns control of the terminal immediately, letting you run another command while the first one continues running behind the scenes.</p><h4>The echo -n Command</h4><p>The -n flag on echo suppresses the trailing newline that echo normally appends. This is important here because you want to send exactly the password and nothing extra — an unexpected newline could cause the comparison to fail.</p><h3>Solving the Challenge</h3><p>First, confirm suconnect is in the home directory:</p><pre>ls -l</pre><p>Running it without arguments shows the usage: suconnect &lt;port&gt;. It will connect to localhost on that port and handle the rest.</p><p>Now set up the Netcat listener with the Level 20 password piped in, running in the background. Choose any available port — 1234 works fine:</p><pre>echo -n &#39;&lt;Level 20 password&gt;&#39; | nc -l -p 1234 &amp;</pre><p>Breaking this down:</p><ul><li>echo -n &#39;&lt;password&gt;&#39; outputs the password without a trailing newline</li><li>| pipes that output into Netcat</li><li>nc -l -p 1234 sets Netcat to listen on port 1234, ready to send the password to whatever connects</li><li>&amp; runs the whole thing in the background</li></ul><p>With the listener running, connect to it using suconnect:</p><pre>./suconnect 1234</pre><p>suconnect connects to localhost on port 1234, receives the password from Netcat, compares it to the stored Level 20 password, finds a match, and prints the Level 21 password back to the terminal.</p><h3>Key Commands Covered</h3><ul><li>nc -l -p &lt;port&gt; Start Netcat in listener mode on a specific port</li><li>echo -n &#39;&lt;text&gt;&#39; Output text without a trailing newline</li><li>command &amp; Run a command in the background</li><li>./suconnect &lt;port&gt; Connect the SetUID binary to the listener on a given port</li></ul><p>This level reinforces a few important ideas. First, Netcat is incredibly versatile — it can initiate connections, listen for them, and pipe data in either direction. Second, the &amp; operator is a fundamental part of working in Linux, particularly when you need processes to run concurrently. Third, understanding networking at the local level — not just across machines, but on your own system — is essential for both system administration and security work.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4428e9ca231c" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-20-4428e9ca231c">Linux Capture The Flag Bandit Level 20</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Capture The Flag Bandit Level 19]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-19-36ed3700ff25?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/36ed3700ff25</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 20:06:49 GMT</pubDate>
            <atom:updated>2026-09-21T20:06:49.043Z</atom:updated>
            <content:encoded><![CDATA[<h4>SetUID Binaries and Running Commands as Another User</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VHRH5oHPXXD0_5tBcO1pmQ.jpeg" /></figure><p>Bandit Level 19 is a short one, but it introduces an important Linux concept: <strong>SetUID binaries</strong>. Understanding what they are and how they work is genuinely useful knowledge, both for CTF challenges and for real-world security work.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_PXAR1bqRKw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_PXAR1bqRKw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_PXAR1bqRKw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dfeb437f1d2d2d3098acb6b11884b7b9/href">https://medium.com/media/dfeb437f1d2d2d3098acb6b11884b7b9/href</a></iframe><h3>The Challenge</h3><p>The goal is to use a SetUID binary located in the home directory to read the password stored in /etc/bandit_pass/bandit20. The challenge hints that running the binary without any arguments will explain how to use it.</p><h3>What Is a SetUID Binary?</h3><p>In Linux, file permissions control what a user can do with a file. But there’s a special permission flag called <strong>SetUID</strong> (Set User ID) that changes how a binary executes. When a binary has the SetUID bit set, it runs with the permissions of the file’s <strong>owner</strong> rather than the permissions of the user who executes it.</p><p>This is useful in legitimate contexts — for example, the passwd command needs to modify /etc/shadow (a root-owned file) even when run by a regular user. SetUID makes that possible. It&#39;s also a common target in privilege escalation during penetration tests, because a misconfigured SetUID binary can let an attacker run commands as a more privileged user.</p><p>You can spot a SetUID binary with ls -l. Instead of the usual rwxr-xr-x permission string, you&#39;ll see an s in the owner&#39;s execute position — something like rwsr-xr-x. That s is the SetUID flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/627/1*UxAf8w3Kgz7UIH571jrtFg.png" /></figure><h3>Solving the Challenge</h3><p>After logging in as bandit19, run a directory listing:</p><pre>ls -l</pre><p>You’ll see a file called bandit20-do. The permissions show it&#39;s owned by bandit20 and has the SetUID bit set, meaning it will execute with bandit20&#39;s privileges regardless of who runs it.</p><p>Run it without arguments to see how it works:</p><pre>./bandit20-do</pre><p>The output confirms it: this binary lets you run a command as bandit20. Test it quickly:</p><pre>./bandit20-do whoami</pre><p>The response is bandit20 — you&#39;re effectively acting as that user for any command you pass to the binary.</p><p>From there, it’s straightforward. Use the binary to read the password file directly:</p><pre>./bandit20-do cat /etc/bandit_pass/bandit20</pre><p>That prints the password for Level 20. Copy it into your notes and you’re done.</p><h3>Key Commands Covered</h3><ul><li>ls -l List files with permissions, showing the SetUID bit</li><li>./bandit20-do &lt;command&gt; Run a command with bandit20’s privileges via the SetUID binary</li><li>cat /etc/bandit_pass/bandit20 Read the password file</li></ul><p>SetUID binaries are a fundamental concept in Linux privilege management — and a well-known area of interest in security research. In a legitimate system, SetUID is used carefully and sparingly. In a poorly configured system, a SetUID binary owned by root can be the difference between a regular user account and full root access. When doing a penetration test or a security audit on a Linux machine, finding SetUID binaries and understanding what they do is always a priority.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36ed3700ff25" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-19-36ed3700ff25">Linux Capture The Flag Bandit Level 19</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Not To Get Hacked Part 2]]></title>
            <link>https://meetcyber.net/how-not-to-get-hacked-part-2-1c795a7b5c1e?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c795a7b5c1e</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 17:22:22 GMT</pubDate>
            <atom:updated>2026-09-08T17:22:22.095Z</atom:updated>
            <content:encoded><![CDATA[<h4>Still Securing Your Computer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SEKUROxh0hNfxr1GzQ_E7g.jpeg" /></figure><p>Welcome back to the Windows security checklist series. In part one, we covered patches and updates, encryption, unused applications, and closing open ports. In this installment, we’re continuing to work through the attack surface — the goal being to reduce the number of entry points an attacker could exploit to get onto your computer.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrfceT9TItOo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrfceT9TItOo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrfceT9TItOo%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0ee21d21d9cd0127bdbf08c1d893215f/href">https://medium.com/media/0ee21d21d9cd0127bdbf08c1d893215f/href</a></iframe><h3>1. Wi-Fi and Bluetooth</h3><p>Wi-Fi and Bluetooth are built for convenience. That’s great when you need them — but when you don’t, they’re open attack surfaces that should be turned off.</p><p>Both wireless protocols can be exploited by threat actors to gain access to your device. It doesn’t require physical access and it doesn’t always require sophisticated tools. So the rule is simple: <strong>if you’re not using them, turn them off.</strong></p><p>Here’s a practical approach:</p><ul><li><strong>Out and about with no Bluetooth devices connected?</strong> Turn Bluetooth off.</li><li><strong>Working from home or a trusted office?</strong> Turn Wi-Fi off too and plug directly into your router with an Ethernet cable.</li></ul><p>A wired Ethernet connection is more secure than Wi-Fi because wireless frequencies can be intercepted — a physical cable can’t be remotely sniffed the same way. Most modern laptops don’t have an Ethernet port built in, but USB-to-Ethernet adapters are inexpensive and easy to find online. It’s worth having one.</p><p>To toggle Wi-Fi and Bluetooth on Windows 11, go to <strong>Settings → Bluetooth &amp; Devices</strong> to manage Bluetooth, and <strong>Settings → Network &amp; Internet</strong> for Wi-Fi. You can also use the quick settings panel in the bottom-right corner of your taskbar.</p><h3>2. VPNs</h3><p>There are two common types of VPNs worth understanding.</p><p>The first is an <strong>enterprise VPN</strong> — the kind used in corporate environments to securely connect remote workers to a company’s internal network and resources. If you work remotely and need access to a company server, this is the type you’re using.</p><p>The second — and the one most relevant for personal security — is a <strong>consumer VPN</strong>. This type encrypts your internet traffic and routes it through a VPN server, protecting you from people who might be watching your connection. It’s especially important when you’re on <strong>public Wi-Fi</strong>, like at a coffee shop, airport, or hotel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aGzNkTGYSltTAo3DSdyTog.png" /><figcaption>Understanding VPN</figcaption></figure><p>Here’s something to keep in mind: not every Wi-Fi network you see is legitimate. Attackers will sometimes set up fake wireless networks with names similar to the real one — “CoffeeShop_Guest” instead of “CoffeeShop_WiFi” — hoping people will connect without thinking. Once you’re on a fake network, they can intercept your traffic. Always verify the network name with staff before connecting to public Wi-Fi, and use a VPN when you do.</p><p>There are a lot of VPN services out there that promise privacy and security but don’t actually deliver it. Make sure to find one that you can verify offers both encryption and privacy. Make sure to research how they store and transmit your data, along with what forms of encryption they use.</p><h3>3. Unused Windows Features</h3><p>Windows comes with a variety of built-in features that may or may not be turned on depending on your system. Some of these — like SMB, Hyper-V, or Active Directory Lightweight Services — are powerful tools that also represent attack surface if they’re enabled and not actively used.</p><p>To review what’s enabled on your machine, go to the search bar and type <strong>“Windows features”</strong>, then select <strong>Turn Windows features on or off</strong> from the Control Panel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/607/1*vwaXIipAKiBWop6S7T01uA.png" /><figcaption>Windows Features</figcaption></figure><p>You’ll see a list of features with checkboxes. Go through it carefully. If something is checked that you don’t use, research it first — some features are necessary for your system to function properly and shouldn’t be disabled. But if you find features that are enabled and genuinely not needed, uncheck them and click OK.</p><p>The logic here is the same as with open ports and unused applications: every enabled feature that you’re not using is a potential entry point you’re leaving open for no reason. And remember, GOOGLE IS YOUR FRIEND. Always research what you find.</p><h3>4. User Permissions</h3><p>User permissions in Windows operate at two levels: <strong>file and folder permissions</strong>, and <strong>user account types</strong>.</p><h4>File and Folder Permissions</h4><p>Right-click any file or folder, select <strong>Properties</strong>, and go to the <strong>Security</strong> tab. From here you can see which users and groups have access to that item and what they’re allowed to do — read, write, modify, execute, or full control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*a9qXR_NG_aYWwuz0au3dug.png" /><figcaption>User Permissions for a File in Windows</figcaption></figure><p>If you have shared computers at home or at work, this matters. There’s no reason the front desk employee should have access to the folder containing financial records. Set permissions accordingly. You can click <strong>Edit</strong> to add, remove, or adjust access for specific users.</p><h4>User Account Types</h4><p>Go to <strong>Settings → Accounts → Other Users</strong> to see all user accounts on the machine. A couple of things to do here:</p><p>First, make sure every account listed is one you recognize and authorized. If there’s an account you didn’t create and your household or colleagues didn’t create either, that’s a red flag — it could indicate someone has already gained access to your machine and established a foothold. Get it removed.</p><p>Second, review the account type for each user. Accounts can be set as <strong>Administrator</strong> or <strong>Standard User</strong>. Administrators have broad ability to make changes to the system — installing software, modifying settings, changing other accounts. Standard users are restricted. Unless someone genuinely needs administrative access, set their account to Standard User. This limits the damage that can be done if that account gets compromised.</p><h3>5. User Account Control (UAC)</h3><p>User Account Control is the Windows feature responsible for those prompts where the screen dims and a window asks “Do you want to allow this app to make changes to your device?” Most people just click yes without reading it. Don’t do that.</p><p>That prompt exists for a reason. It tells you what software is requesting changes, who the publisher is, and whether it’s been signed and verified. If you see “Publisher: Unknown” or the software isn’t verified, that’s a signal to stop and investigate before proceeding. It’s possible you’re about to install something malicious.</p><p>To review and configure UAC settings, search for <strong>“User Account Control”</strong> in the Start menu and select <strong>Change User Account Control settings</strong> from the Control Panel.</p><p>The slider has four levels:</p><ul><li><strong>Always notify</strong> — the most secure option; prompts you any time an app or you make changes to Windows settings</li><li><strong>Notify me only when apps try to make changes</strong> — the default setting</li><li><strong>Notify me only when apps try to make changes (don’t dim desktop)</strong> — slightly less secure</li><li><strong>Never notify</strong> — not recommended</li></ul><p>If you regularly install new software, download tools from the internet, or visit unfamiliar websites, set UAC to <strong>Always notify</strong>. It adds a small amount of friction but significantly reduces the risk of something sneaking changes through without your knowledge.</p><p>The point of this checklist is to make your computer more secure. Always make sure to research everything you find before disabling it or turning it off. Limiting the accounts and the account permissions greatly reduces the potential for an advanced attack should your computer be compromised.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c795a7b5c1e" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/how-not-to-get-hacked-part-2-1c795a7b5c1e">How Not To Get Hacked Part 2</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Capture The Flag Bandit Level 18]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-18-5d29005cc5ab?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d29005cc5ab</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Wed, 26 Aug 2026 19:51:52 GMT</pubDate>
            <atom:updated>2026-08-26T19:51:52.601Z</atom:updated>
            <content:encoded><![CDATA[<h4>Bypassing a Modified .bashrc with SSH</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r1kdnqc3yrr8ynmvHbBlVg.jpeg" /></figure><p>Bandit Level 18 is a great example of how knowing your Linux environment pays off. The challenge isn’t about a complicated exploit or a long chain of tools — it’s about understanding how the shell works and using that knowledge to get around a deliberate roadblock.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FrqiikQirRm0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrqiikQirRm0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FrqiikQirRm0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/440a30fbf726d2458eb761c2cc9e0abc/href">https://medium.com/media/440a30fbf726d2458eb761c2cc9e0abc/href</a></iframe><h3>The Challenge</h3><p>The password for Level 18 is sitting in a file called readme in the home directory. Simple enough — except someone has modified the .bashrc file to automatically log you out the moment you log in via SSH. Every time you connect, you get booted before you can do anything.</p><h3>Understanding .bashrc</h3><p>The .bashrc file is a configuration file that runs automatically whenever a new bash shell session starts. It&#39;s used to set environment variables, define aliases, configure the prompt, and specify shell behavior. It&#39;s also where, in this case, a logout command has been planted to kick you out immediately on login.</p><p>There are multiple shell types in Linux — bash, sh, zsh, and others. The .bashrc file is specific to bash. If you log in using a different shell, the .bashrc doesn&#39;t execute, which means the logout command never fires.</p><p>That’s the key to solving this level.</p><h3>The Solution: Log In with a Different Shell</h3><p>SSH allows you to specify a command or shell to run immediately upon connecting, before any configuration files for the default shell are executed. Using the -t flag followed by the shell you want to use does exactly that:</p><pre>ssh bandit18@bandit.labs.overthewire.org -p 2220 -t &quot;sh&quot;</pre><p>Breaking this down:</p><ul><li>-t forces a pseudo-terminal allocation, allowing you to run an interactive shell</li><li>&quot;sh&quot; tells SSH to drop you into an sh shell instead of bash — bypassing .bashrc entirely</li></ul><p>Enter the Level 18 password when prompted. Instead of being kicked out, you’ll land at a shell prompt. From there, it’s straightforward:</p><pre>ls<br>cat readme</pre><p>The readme file contains the password for Level 19. Copy it into your notes and you&#39;re done.</p><h3>Key Commands Covered</h3><ul><li>ssh user@host -p &lt;port&gt; -t &quot;sh&quot; Log in via SSH using sh instead of bash, bypassing .bashrc</li><li>ls List files in the current directory</li><li>cat readme Print the contents of the readme file</li></ul><p>This level rewards breadth of Linux knowledge. The solution isn’t something you’d necessarily find by just grinding through CTF challenges — it comes from actually spending time in Linux environments, understanding how shells work, and knowing what configuration files do. Resources like <em>Linux for Hackers</em> by OccupyTheWeb are exactly the kind of material that builds this foundation. The second edition was recently released and is well worth picking up.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d29005cc5ab" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-18-5d29005cc5ab">Linux Capture The Flag Bandit Level 18</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Not To Get Hacked]]></title>
            <link>https://meetcyber.net/how-not-to-get-hacked-aaf2c8d48bae?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaf2c8d48bae</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Sun, 23 Aug 2026 07:15:51 GMT</pubDate>
            <atom:updated>2026-08-23T07:15:51.996Z</atom:updated>
            <content:encoded><![CDATA[<h4>Securing Your Computer Part 1</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bpf8ttXH7OF-HClGF74oqw.jpeg" /></figure><p>Whether you’re 80 years old, 30 years old, or a high school student, understanding how vulnerable your devices can be is the first step to actually protecting yourself. This isn’t just for tech people — this is for everyone. Every device you own is an attack point, and every device can have multiple attack points. In security, we call that an <strong>attack surface</strong>. The bigger your attack surface, the more opportunities a threat actor has to get into your stuff — your files, your passwords, your bank account, etc.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYQVNfXzCwWI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYQVNfXzCwWI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYQVNfXzCwWI%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8abe4610dd457a607f40f0e9abcab2c6/href">https://medium.com/media/8abe4610dd457a607f40f0e9abcab2c6/href</a></iframe><h3>1. Patches and Updates</h3><p>This one sounds boring but it’s one of the most important things you can do. Microsoft releases patches on a regular basis — typically every Tuesday. These updates include bug fixes, performance improvements, and most importantly, <strong>security updates</strong>.</p><p>Here’s why security updates matter: security researchers and professionals are constantly finding vulnerabilities in operating systems. When a vulnerability is discovered, Microsoft (or whoever makes the software) patches it as quickly as possible. If you haven’t installed that patch, that vulnerability is still wide open on your machine and attackers can exploit it.</p><p>To check for updates on Windows 11, just type “update” in the search bar at the bottom of your screen and select <strong>Check for Updates</strong>. If updates are available, install them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UKuthWEZyc3DaG1s55JaOw.png" /><figcaption>Updates in Windows 11</figcaption></figure><p>One important note: <strong>restarting is not the same as shutting down.</strong> Once updates are installed, you need to restart your computer to actually apply them. A shutdown doesn’t do that. Make it a habit — every Friday, for example, open Windows Update and click “Check For Updates”. It checks for Windows updates as well as hardware updates like BIOS patches.</p><h3>2. Encryption</h3><p>Encryption ensures that even if someone gets onto your computer and steals your files, they cannot read what’s in them. It protects your data at rest.</p><p>On Windows, you have a couple of options:</p><p><strong>Device Encryption</strong> — Go into Settings and search for “encryption.” You’ll see a Device Encryption option. Turn it on if it isn’t already.</p><p><strong>BitLocker</strong> — BitLocker is Microsoft’s full drive encryption tool and it’s the preferred option for whole-drive encryption. It runs natively on Windows, which means it’s optimized for the environment and won’t slow your machine down. The catch: BitLocker requires <strong>Windows 11 Professional</strong>. The Pro upgrade costs around $99-$100 — a one-time purchase that gets you BitLocker and a handful of other features worth having.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNjppqRN1BX7jiQz_MLSyw.png" /><figcaption>BitLocker Encryption on Windows 11</figcaption></figure><p><strong>VeraCrypt</strong> — If you don’t want to spend the money, VeraCrypt is a free, open-source encryption tool that can encrypt your entire hard drive or create encrypted volumes for storing sensitive data. It works, but in practice it tends to slow performance down more than BitLocker does. If budget is the constraint, it’s a solid option. Just know the trade-off.</p><p>The bottom line: get your device encrypted. If someone physically steals your computer, pulls out your hard drive, or exfiltrates files, encryption is what stops them from reading everything on it.</p><h3>3. Unused Applications</h3><p>Open Settings, go to <strong>Apps</strong>, and click <strong>Installed Apps</strong>. You’ll see everything that’s installed on your machine — including things that came pre-installed that you’ve never touched.</p><p>Go through that list. If there’s an application you don’t recognize or don’t use, look it up before you do anything. Search the application name and the publisher in Google to find out what it does. <strong>GOOGLE IS YOUR BEST FRIEND!</strong> Some things that look unfamiliar are actually important system components. Others might genuinely be unnecessary and can be safely removed. And occasionally — this has happened — you might find an application from a company you’ve never heard of that has no business being on your machine. That can be a sign of malware or a pre-installed application that’s doing things you don’t want it to do.</p><p>The rule is: <strong>research before you delete.</strong></p><h3>4. Open Ports</h3><p>Your computer has ports — over 65,000 of them — that listen for network connections. Services and applications run on specific ports, and sometimes ports get left open that you don’t need open. An open port is a potential entry point for an attacker.</p><p>To see what’s open on your machine, use <strong>Zenmap</strong> — the graphical version of Nmap that runs on Windows and Mac. Nmap is one of the most widely used network scanning tools in security. Zenmap makes it accessible without needing a terminal. You can checkout the video below to learn more about Zenmap.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FijbiizlBri0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DijbiizlBri0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FijbiizlBri0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/ae9917e2b1068b0704918181bf4059d0/href">https://medium.com/media/ae9917e2b1068b0704918181bf4059d0/href</a></iframe><p>Open Zenmap, set the target to localhost (your own computer), and use the following flags:</p><pre>-T4 -sV -p-</pre><ul><li>-T4 sets the scan speed (4 is faster)</li><li>-sV detects the service and version running on each open port</li><li>-p- scans all 65,000+ ports, not just the default top 1,000</li></ul><p>This scan will take a while. When it’s done, you’ll have a full list of every open port on your machine along with what’s running on each one.</p><p>Before closing anything, <strong>research each port</strong>. Look up the port number and the service name to understand what it does. Some open ports are necessary for your system to function. Closing the wrong one can break things. <strong>GOOGLE IS YOUR FRIEND HERE.</strong></p><p>If you do find a port you want to close, you can do it through the Windows Command Prompt (run as Administrator). First, find the process ID associated with that port:</p><pre>netstat -o | findstr &lt;port number&gt;</pre><p>Then kill the process:</p><pre>taskkill /PID &lt;process ID&gt; /F</pre><p>This closes the port by stopping the process running on it. Again — don’t just start doing this on every open port. Research first, act second. <strong>GOOGLE IS YOUR FRIEND HERE.</strong></p><p>Going through this checklist will make your computer more secure. But don’t rush through it and start changing things without understanding what you’re changing. Did I mention Google is your friend? Research the services running on your machine. Research the applications you find. Understand what a patch does before you install it.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaf2c8d48bae" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/how-not-to-get-hacked-aaf2c8d48bae">How Not To Get Hacked</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Capture The Flag Bandit Level 17]]></title>
            <link>https://meetcyber.net/linux-capture-the-flag-bandit-level-17-5e684fdaa0cc?source=rss-6f6340d4b20d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e684fdaa0cc</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[linux]]></category>
            <dc:creator><![CDATA[Red]]></dc:creator>
            <pubDate>Tue, 18 Aug 2026 17:27:48 GMT</pubDate>
            <atom:updated>2026-08-18T17:42:45.119Z</atom:updated>
            <content:encoded><![CDATA[<h4>Comparing Files with Diff</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S44eL4z4FZ1tjKhECkTRmw.jpeg" /></figure><p>Bandit Level 17 is one of the more straightforward levels in the series, but it introduces a genuinely useful command: diff. The challenge is simple — find the one line that changed between two files — and the solution is elegant.</p><p>If you’d like to follow what I did via video, feel free to check it out on YouTube below:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZ7knBBV4uyM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZ7knBBV4uyM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZ7knBBV4uyM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/086dff770954ab828e587e4e19dd8943/href">https://medium.com/media/086dff770954ab828e587e4e19dd8943/href</a></iframe><h3>The Challenge</h3><p>Inside the home directory are two files: passwords.old and passwords.new. Both contain a long list of passwords. The password for Level 18 is the one line that was changed between the two files — specifically, the new line in passwords.new.</p><p>You could try to cat both files and compare them manually, but with a list that long, that&#39;s not realistic. This is exactly what the diff command is for.</p><h3>Logging In with the SSH Key</h3><p>Since Level 16 returned an SSH private key rather than a password, logging in works the same way as it did in Level 13. From your working directory:</p><pre>ssh -i sshkey17.private bandit17@bandit.labs.overthewire.org -p 2220</pre><p>No password needed — the key handles authentication.</p><h3>Solving It with diff</h3><p>diff compares two files line by line and reports any differences between them. The syntax is simple:</p><pre>diff passwords.new passwords.old</pre><p>The output shows two lines — the line that exists in one file and the line that replaced it in the other. The arrow direction tells you which file each line belongs to: arrows pointing left (&lt;) refer to the first file, arrows pointing right (&gt;) refer to the second.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*F5jAcfOfYPUVCWy1lHSkRg.png" /></figure><p>The new line in passwords.new is the password for Level 18. Copy it and move on.</p><h3>Logging Into Level 18 — and the “Bye-bye” Message</h3><p>Attempt to SSH into bandit18 with the new password:</p><pre>ssh bandit18@bandit.labs.overthewire.org -p 2220</pre><p>Something slightly unexpected happens: the connection opens, displays “Welcome to OverTheWire,” and then immediately closes with a “Bye-bye” message. No shell access.</p><p>This isn’t a mistake. The challenge page for Level 17 specifically warns that if you see “bye-bye” when logging into bandit18, it’s intentional and related to the next challenge — Level 18 to 19. The logout is being triggered deliberately, likely by a modified shell configuration file. Getting past it is the puzzle for the next level.</p><p>For now, the password has been found and Level 17 is solved.</p><h3>Key Commands Covered</h3><ul><li>ssh -i &lt;keyfile&gt; user@host -p &lt;port&gt; Log in using an SSH private key</li><li>diff &lt;file1&gt; &lt;file2&gt; Compare two files line by line and show differences</li><li>cat &lt;file&gt; Print the contents of a file</li></ul><p>The diff command is a simple but powerful tool that shows up in a lot of real-world contexts — comparing configuration files before and after a change, reviewing log files, checking whether two versions of a document differ. In a security context, it&#39;s useful any time you need to quickly identify what changed between two states of a system or file.</p><p>The “bye-bye” behavior at the end is also a good lesson: when something unexpected happens, read the documentation before assuming something went wrong. The challenge told you it would happen — and it did exactly what it said it would.</p><p>Feel free to check out my blog: <a href="https://coderedblog.io/">coderedblog.io</a></p><p>Checkout my <a href="https://www.youtube.com/@Red-2876">YouTube</a></p><p><a href="https://buymeacoffee.com/coderedblog">Buy me a coffee!</a></p><p>Feel free to follow me on here and keep learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e684fdaa0cc" width="1" height="1" alt=""><hr><p><a href="https://meetcyber.net/linux-capture-the-flag-bandit-level-17-5e684fdaa0cc">Linux Capture The Flag Bandit Level 17</a> was originally published in <a href="https://meetcyber.net/">MeetCyber</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>