<?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 Snkth on Medium]]></title>
        <description><![CDATA[Stories by Snkth on Medium]]></description>
        <link>https://medium.com/@snkth123?source=rss-a8199217ddcc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vGAoyGKcX3ytSZXKgrhvNA.png</url>
            <title>Stories by Snkth on Medium</title>
            <link>https://medium.com/@snkth123?source=rss-a8199217ddcc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:03:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@snkth123/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[NetRecon Pro: The Story of Building a Cybersecurity Tool from Scratch— -]]></title>
            <link>https://medium.com/@snkth123/netrecon-pro-from-soc-analyst-to-python-developer-building-a-professional-network-fa16780d53ac?source=rss-a8199217ddcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa16780d53ac</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[nmap-command]]></category>
            <category><![CDATA[nmap-scan]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[nmap]]></category>
            <dc:creator><![CDATA[Snkth]]></dc:creator>
            <pubDate>Mon, 27 Jul 2026 07:23:06 GMT</pubDate>
            <atom:updated>2026-07-27T08:26:36.862Z</atom:updated>
            <content:encoded><![CDATA[<p>## 1. 🌟 INTRODUCTION</p><p>### The Beginning:</p><p>It was a quiet Sunday evening when I decided to combine my passion for cybersecurity with Python development. As a SOC Analyst, I was always looking for tools that could make my work easier and more efficient. That’s when the idea for NetRecon Pro was born.</p><p>### What is NetRecon Pro?</p><p>NetRecon Pro is a professional-grade network reconnaissance tool built with Python that:</p><p>- 🔍 Scans any IP address or domain<br>- 🛡️ Detects open ports and running services<br>- 💻 Identifies operating systems<br>- 🚨 Finds vulnerabilities automatically<br>- 📊 Generates professional reports (HTML, TXT, CSV, JSON)<br>- 🎨 Provides a beautiful terminal interface</p><p>— -</p><p>## 2. 🎯 WHY I BUILT IT</p><p>### As a SOC Analyst:<br>- Needed a reliable tool for quick network assessments<br>- Wanted to automate repetitive scanning tasks<br>- Required professional reports for security audits<br>- Needed a tool that could detect vulnerabilities quickly</p><p>### As a Developer:<br>- Wanted to master Python OOP (Object-Oriented Programming)<br>- Needed a strong portfolio project for job applications<br>- Wanted to contribute to the open-source community<br>- Passionate about building tools that help others</p><p>### For the Community:<br>- Provide a free, open-source tool for security professionals<br>- Help beginners learn network security concepts<br>- Build a community around cybersecurity tools<br>- Demonstrate practical Python applications</p><p>— -</p><p>## 3. ✨ KEY FEATURES</p><p>| Feature | Description |<br>| — — — — -| — — — — — — -|<br>| Comprehensive Scanning | Full port scan with OS and version detection |<br>| Quick Scanning | Fast top ports scan for rapid results |<br>| OS Detection | Identify operating systems with accuracy |<br>| Service Version Detection | Enumerate service versions and products |<br>| UDP Scanning | Scan UDP ports for hidden services |<br>| SYN Stealth | SYN stealth scan (requires admin/root) |<br>| Multi-Target | Scan multiple IPs at once |<br>| Vulnerability Scanner | Check for known CVEs |<br>| Multiple Reports | HTML, TXT, CSV, JSON |<br>| Scan History | Track all your scans |<br>| Skip Ping (-Pn) | Scan hosts that block ICMP |<br>| Beautiful UI | Rich terminal interface with colors and progress bars |</p><p>— -</p><p>## 4. 🛠️ TECHNICAL ARCHITECTURE</p><p>### Tech Stack:</p><p>| Category | Technology | Purpose |<br>| — — — — — | — — — — — — | — — — — -|<br>| Language | Python 3.7+ | Main programming language |<br>| Scanning | Nmap | Network scanning engine |<br>| UI | Rich Library | Beautiful terminal interface |<br>| Templating | Jinja2 | HTML report generation |<br>| Parsing | XML/JSON | Data extraction and export |<br>| Version Control | Git/GitHub | Code management |<br>| Editor | VS Code | Development environment |</p><p>### Project Structure:</p><p>```<br>NetRecon-Pro/<br>│<br>├── 📁 Core Modules<br>│ ├── netrecon.py # Main entry point — The brain<br>│ ├── scanner.py # Nmap scanner logic — The engine<br>│ ├── parser.py # XML parsing — The translator<br>│ ├── report.py # Report generation — The storyteller<br>│ ├── ui.py # User interface — The face<br>│ ├── config.py # Configuration — The settings<br>│ └── utils.py # Utilities — The helpers<br>│<br>├── 📁 Output Directories<br>│ ├── Reports/ # Generated reports<br>│ ├── logs/ # Application logs<br>│ └── templates/ # HTML templates<br>│<br>├── 📁 Supporting Files<br>│ ├── requirements.txt # Dependencies<br>│ ├── README.md # Documentation<br>│ └── LICENSE # MIT License<br>```</p><p>— -</p><p>## 5. 💻 HOW IT WORKS — FLOW DIAGRAM</p><p>```<br>1. User launches NetRecon Pro<br> ↓<br>2. Shows beautiful banner and menu with colors<br> ↓<br>3. User selects scan option (1–8)<br> ↓<br>4. User enters target IP/domain (e.g., 8.8.8.8)<br> ↓<br>5. scanner.py builds Nmap command dynamically<br> ↓<br>6. Nmap scans target and saves XML/TXT<br> ↓<br>7. parser.py parses XML output<br> ↓<br>8. Displays results in beautiful tables<br> ↓<br>9. Vulnerabilities auto-detected<br> ↓<br>10. report.py generates HTML/TXT/CSV/JSON<br> ↓<br>11. Saves to Reports/ folder<br> ↓<br>12. User can view reports or scan again<br>```</p><p>— -</p><p>## 6. 📊 DETAILED MODULE EXPLANATION</p><p>### scanner.py — The Scanning Engine</p><p>```python<br>class NmapScanner:<br> “””<br> The heart of NetRecon Pro — handles all Nmap scanning operations<br> “””<br> — Builds Nmap commands dynamically<br> — Handles 7 different scan types<br> — Shows real-time progress with progress bars<br> — Saves XML and TXT output<br> — Handles errors gracefully<br> — Supports -Pn option for firewalled hosts<br>```</p><p>**Key Methods:**<br>- `scan()`: Main scanning function<br>- `build_command()`: Constructs Nmap command<br>- `execute_scan()`: Runs Nmap and captures output<br>- `save_results()`: Saves XML and TXT files</p><p>— -</p><p>### parser.py — The Data Translator</p><p>```python<br>class NmapParser:<br> “””<br> Parses Nmap XML output and extracts meaningful information<br> “””<br> — Parses Nmap XML output<br> — Extracts host information (IP, status, hostname)<br> — Identifies open ports and services<br> — Detects OS and service versions<br> — Checks for vulnerabilities (CVE detection)<br> — Calculates statistics<br>```</p><p>**Key Methods:**<br>- `parse()`: Parses XML file<br>- `get_summary()`: Returns scan summary<br>- `display_results()`: Shows results in tables<br>- `get_vulnerabilities()`: Checks for CVEs</p><p>— -</p><p>### report.py — The Storyteller</p><p>```python<br>class ReportGenerator:<br> “””<br> Generates professional reports in multiple formats<br> “””<br> — Generates HTML reports (beautiful, shareable)<br> — Creates TXT summaries (plain text)<br> — Exports CSV data (Excel compatible)<br> — Produces JSON output (API ready)<br> — Uses Jinja2 templates<br>```</p><p>**Key Methods:**<br>- `generate_html()`: Creates HTML report<br>- `generate_txt()`: Creates text report<br>- `generate_csv()`: Creates CSV report<br>- `generate_json()`: Creates JSON export</p><p>— -</p><p>### ui.py — The Face</p><p>```python<br>def show_banner():<br> “””Displays professional banner with ASCII art”””<br> <br>def show_menu():<br> “””Shows main menu with options”””<br> <br>def get_scan_options():<br> “””Collects user input for scanning”””<br> <br>def show_results():<br> “””Displays results in beautiful tables”””<br>```</p><p>**Key Features:**<br>- Rich colors (cyan, green, yellow, red)<br>- Tables with borders<br>- Progress tracking<br>- Emoji support (🔍, ✅, ❌, ⚠️, 🔥)<br>- Professional look</p><p>— -</p><p>## 7. 🔒 VULNERABILITY DETECTION SYSTEM</p><p>### How It Works:</p><p>```<br>1. Scans all open ports<br>2. Identifies services running on each port<br>3. Checks against built-in CVE database<br>4. Displays potential vulnerabilities with severity<br>```</p><p>### Detected CVEs:</p><p>| Service | CVE | Severity | Description |<br>| — — — — -| — — -| — — — — — | — — — — — — -|<br>| SMB | CVE-2017–0143 | 🔴 HIGH | EternalBlue — RCE |<br>| RDP | CVE-2019–0708 | 🔴 HIGH | BlueKeep — RCE |<br>| HTTP | CVE-2021–44228 | 🔴 HIGH | Log4j — RCE |<br>| MySQL | CVE-2012–2122 | 🟡 MEDIUM | Authentication Bypass |<br>| SSH | CVE-2018–15473 | 🟡 MEDIUM | Username Enumeration |<br>| FTP | CVE-2019–5418 | 🟡 MEDIUM | Directory Traversal |<br>| SMTP | CVE-2020–1241 | 🟡 MEDIUM | Heap Overflow |<br>| DNS | CVE-2020–1350 | 🔴 HIGH | SIGRed — RCE |</p><p>— -</p><p>## 8. 📸 SAMPLE OUTPUT</p><p>### Terminal Output:</p><p>```<br>╔══════════════════════════════════════════════════════════════════╗<br>║ 📊 SCAN RESULTS SUMMARY<br>╚══════════════════════════════════════════════════════════════════╝<br> 📡 Total Hosts: 1 ⬆️ Up: 1 🔓 Open Ports: 7</p><p>🎯 Host Discovery Results<br>┌───┬─────────────────┬────────┬────────────┬──────────────────────────┐<br>│ # │ IP Address │ Status │ Open Ports │ OS │<br>├───┼─────────────────┼────────┼────────────┼──────────────────────────┤<br>│ 1 │ 127.0.0.1 │ up │ 7 │ Windows 11 24H2 │<br>└───┴─────────────────┴────────┴────────────┴──────────────────────────┘</p><p>🔓 Open Ports on 127.0.0.1<br>┌──────┬──────────┬──────────────┬────────────────────────┐<br>│ Port │ Protocol │ Service │ Version │<br>├──────┼──────────┼──────────────┼────────────────────────┤<br>│ 135 │ tcp │ msrpc │ Microsoft Windows RPC │<br>│ 445 │ tcp │ microsoft-ds │ SMB/CIFS │<br>│ 3306 │ tcp │ mysql │ 8.0.44 │<br>│ 5432 │ tcp │ postgresql │ PostgreSQL DB │<br>│ 8000 │ tcp │ http │ Splunkd httpd │<br>│ 8089 │ tcp │ http │ Splunkd httpd │<br>│ 8194 │ tcp │ http │ Golang net/http server │<br>└──────┴──────────┴──────────────┴────────────────────────┘<br>```</p><p>### HTML Report Preview:</p><p>```<br>┌─────────────────────────────────────────────────────────────────┐<br>│ 🔍 NetRecon Pro Scan Report │<br>│ Generated: 2026–07–26 14:49:50 │<br>│ │<br>│ ┌──────────┬─────────┬───────────┐ │<br>│ │ Total │ Up │ Open │ │<br>│ │ Hosts: 1 │ Hosts: 1│ Ports: 7 │ │<br>│ └──────────┴─────────┴───────────┘ │<br>│ │<br>│ 🎯 Host Details │<br>│ ┌─────────────────────────────────────────────────────────┐ │<br>│ │ IP: 127.0.0.1 │ Hostname: localhost │ Status: UP │ │<br>│ │ OS: Windows 11 │ Open Ports: 7 │ │ │<br>│ └─────────────────────────────────────────────────────────┘ │<br>│ │<br>│ 🔓 Open Ports │<br>│ ┌──────┬──────────┬──────────────┬────────────────────────┐ │<br>│ │ Port │ Protocol │ Service │ Version │ │<br>│ ├──────┼──────────┼──────────────┼────────────────────────┤ │<br>│ │ 135 │ tcp │ msrpc │ Microsoft Windows RPC │ │<br>│ │ 445 │ tcp │ microsoft-ds │ SMB/CIFS │ │<br>│ │ 3306 │ tcp │ mysql │ 8.0.44 │ │<br>│ └──────┴──────────┴──────────────┴────────────────────────┘ │<br>│ │<br>│ ⚠️ Vulnerabilities Found │<br>│ • CVE-2017–0143 (EternalBlue) — HIGH │<br>│ • CVE-2019–0708 (BlueKeep) — HIGH │<br>│ │<br>│ Generated by NetRecon Pro v2.0 │<br>└─────────────────────────────────────────────────────────────────┘<br>```</p><p>— -</p><p>## 9. 🚀 INSTALLATION &amp; USAGE</p><p>### Step 1: Clone Repository<br>```bash<br>git clone <a href="https://github.com/likith-raj/NetRecon-Pro.git">https://github.com/likith-raj/NetRecon-Pro.git</a><br>cd NetRecon-Pro<br>```</p><p>### Step 2: Install Dependencies<br>```bash<br>pip install -r requirements.txt<br>```</p><p>### Step 3: Install Nmap<br>- **Windows:** Download from nmap.org<br>- **Linux:** `sudo apt-get install nmap`<br>- **Mac:** `brew install nmap`</p><p>### Step 4: Run<br>```bash<br>python netrecon.py<br>```</p><p>— -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SJucRIQJmIc1iWUt7Cl0UQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nj3wn3Dozqrrr6nmCMj8hQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5VDTQcC8MzA08wBnIhL4qQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-ZlDQGpvuqTMfCxsDxGwg.png" /></figure><p>## 10. 💡 USE CASES</p><p>| User | How They Use It |<br>| — — — | — — — — — — — — -|<br>| SOC Analyst | Quick network assessments, vulnerability checks |<br>| Network Admin | Monitor network security, find open ports |<br>| Security Researcher | Research vulnerabilities, test security |<br>| Penetration Tester | Initial reconnaissance, service enumeration |<br>| Student | Learn networking, practice Python |<br>| Developer | Build security tools, portfolio projects |</p><p>— -</p><p>## 11. 🎓 WHAT I LEARNED</p><p>### Technical Skills:<br>- Python OOP (Classes, Objects, Inheritance)<br>- File I/O operations<br>- XML parsing<br>- JSON export<br>- HTML templating (Jinja2)<br>- Subprocess management<br>- Error handling</p><p>### Network Security:<br>- IP addressing<br>- Port scanning techniques<br>- OS fingerprinting<br>- Service version detection<br>- Vulnerability identification<br>- CVE tracking<br>- Firewall concepts</p><p>### Soft Skills:<br>- Problem-solving<br>- Project management<br>- Documentation writing<br>- Community engagement<br>- Open-source contribution</p><p>— -</p><p>## 12. 🚧 CHALLENGES &amp; SOLUTIONS</p><p>| Challenge | Solution |<br>| — — — — — -| — — — — — |<br>| Firewall blocking ICMP | Added -Pn option to skip ping |<br>| Complex XML parsing | Used Python’s built-in XML library |<br>| UI being boring | Used Rich library for beautiful terminal |<br>| Multiple report formats | Created separate generator functions |<br>| Error handling | Comprehensive try-except blocks |<br>| Multi-target support | Loop through target list |</p><p>— -</p><p>## 13. 🔮 FUTURE PLANS</p><p>| Feature | Priority | Description |<br>| — — — — -| — — — — — | — — — — — — -|<br>| Email Reports | 🔥 High | Auto-send reports to team |<br>| Database Storage | 🔥 High | Store scans in SQLite |<br>| Web Interface | 🔥 High | Browser-based dashboard |<br>| Real-time Alerts | 🟡 Medium | Notification system |<br>| Scheduled Scans | 🟡 Medium | Automatic periodic scans |<br>| Mobile App | 🟢 Low | Android/iOS companion |<br>| AI Integration | 🟢 Low | Smart analysis |</p><p>— -</p><p>## 14. 🛡️ SECURITY BEST PRACTICES</p><p>- Only scan authorized targets<br>- Use -Pn for firewalled hosts<br>- Don’t use aggressive on production<br>- Check local laws before scanning<br>- Use for educational purposes only</p><p>— -</p><p>## 15. 🤝 CONTRIBUTING</p><p>Want to contribute? Here’s how:<br>1. Fork the repository<br>2. Create a feature branch<br>3. Make your changes<br>4. Test thoroughly<br>5. Submit a pull request</p><p>— -</p><p>## 16. 📫 CONNECT WITH ME</p><p>- **GitHub:** [likith-raj](<a href="https://github.com/likith-raj">https://github.com/likith-raj</a>)<br>- **LinkedIn:** [likith-sunny](<a href="https://linkedin.com/in/likith-sunny">https://linkedin.com/in/likith-sunny</a>)<br>- **Email:** <a href="/service/mailto:snkth123@gmail.com">snkth123@gmail.com</a></p><p>— -</p><p>## 17. ⭐ SUPPORT</p><p>If you find this project useful:<br>- ⭐ Star on GitHub<br>- 🍴 Fork and contribute<br>- 📢 Share with others<br>- 💬 Give feedback</p><p>— -</p><p>## 18. 📝 LICENSE</p><p>MIT License — Free to use, modify, and distribute.</p><p>— -</p><p>## 19. ⚠️ DISCLAIMER</p><p>This tool is for **educational and authorized testing purposes only**. Do not use on systems without permission.</p><p>— -</p><p>## 20. 💭 FINAL WORDS</p><p>Building NetRecon Pro has been an incredible journey of growth and learning. It helped me:</p><p>- Master Python OOP<br>- Understand network security deeply<br>- Build a professional, production-ready tool<br>- Contribute to the open-source community<br>- Create a strong portfolio project</p><p>If you’re a SOC Analyst, network administrator, or security enthusiast, I encourage you to:<br>- Try NetRecon Pro — Use it for your daily work<br>- Contribute — Add new features<br>- Learn — Explore the code<br>- Build — Create your own tools<br>- Share — Help others learn</p><ul><li>*Remember:** Security is not a product, but a process. Tools like N</li><li>```bash<br>git clone <a href="https://github.com/likith-raj/NetRecon-Pro.git">https://github.com/likith-raj/NetRecon-Pro.git</a><br>cd NetRecon-Pro<br>pip install -r requirements.txt<br>python netrecon.py</li></ul><p>**#Cybersecurity #python #NetworkSecurity #SOC #Splunk #InfoSec #Development #OpenSource #NetReconPro**</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa16780d53ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inside Emotet: A Step-by-Step Dynamic Malware Analysis Using ANY.RUN]]></title>
            <link>https://medium.com/@snkth123/inside-emotet-a-step-by-step-dynamic-malware-analysis-using-any-run-abeb2377cfdf?source=rss-a8199217ddcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/abeb2377cfdf</guid>
            <category><![CDATA[emotet]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <dc:creator><![CDATA[Snkth]]></dc:creator>
            <pubDate>Wed, 15 Jul 2026 10:16:59 GMT</pubDate>
            <atom:updated>2026-07-15T10:16:59.215Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>As a SOC Analyst, one of the most valuable skills is understanding how malware behaves after it infects a system. Reading about malware is helpful, but actually watching it execute inside a safe sandbox provides a much deeper understanding of attacker techniques.</p><p>For this analysis, I chose an <strong>Emotet</strong> malware sample from <strong>MalwareBazaar</strong> and executed it inside an isolated <strong>Windows 10 (64-bit)</strong> environment provided by <strong>ANY.RUN</strong>. My objective was not simply to identify the malware, but to understand its behavior from the moment it was launched until it attempted to communicate with external infrastructure.</p><p>This article documents the investigation process, explains the terminology encountered during analysis, and highlights the Indicators of Compromise (IOCs) that a SOC analyst would typically investigate.</p><h3>What is Emotet?</h3><p>Emotet is one of the most well-known malware families in cybersecurity history. It initially appeared as a banking Trojan designed to steal financial information. Over time, it evolved into a highly sophisticated malware loader capable of downloading additional malicious payloads such as ransomware, credential stealers, and Remote Access Trojans (RATs).</p><p>Unlike many simple malware samples, Emotet focuses heavily on reconnaissance before carrying out its malicious objectives. It collects information about the infected system, determines whether it is running in a virtual environment, identifies the victim’s network configuration, and establishes communication with command-and-control (C2) servers.</p><h3>Lab Environment</h3><p>To safely analyze the malware, I used the following environment:</p><p><strong>Operating System</strong></p><p>Windows 10 (64-bit)</p><p><strong>Sandbox Platform</strong></p><p>ANY.RUN Interactive Sandbox</p><p><strong>Malware Source</strong></p><p>MalwareBazaar</p><p><strong>Execution Method</strong></p><p>ZIP archive extracted using WinRAR</p><p>Executable launched inside the sandbox</p><p>Because the analysis was performed inside an isolated cloud sandbox, the malware could execute safely without affecting a real computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bqv8ViTcWb2O1aK7_SWjmQ.png" /></figure><h3>Investigation Workflow</h3><p>The investigation followed the sequence below:</p><pre>Download Sample<br>        │<br>        ▼<br>Extract ZIP Archive<br>        │<br>        ▼<br>Execute Malware<br>        │<br>        ▼<br>Process Creation<br>        │<br>        ▼<br>System Discovery<br>        │<br>        ▼<br>DNS Requests<br>        │<br>        ▼<br>Network Connections<br>        │<br>        ▼<br>External IP Lookup<br>        │<br>        ▼<br>C2 Communication<br>        │<br>        ▼<br>IOC Collection</pre><h3>Step 1 — Malware Execution</h3><p>The sample was downloaded as a password-protected ZIP archive.</p><p>Password:</p><pre>infected</pre><p>After extraction, the executable was launched.</p><p>ANY.RUN immediately generated a detection identifying the sample as <strong>Emotet</strong>.</p><p>The first actions recorded were:</p><ul><li>Archive extraction</li><li>Executable launch</li><li>Process creation</li></ul><p>At this stage, the malware had not yet performed any malicious activity. It had only started executing.</p><h3>Step 2 — Process Analysis</h3><p>The process tree provides one of the clearest views of malware execution.</p><p>The following processes were observed:</p><pre>WinRAR.exe<br>        │<br>        ▼<br>251037ce....exe<br>        │<br>        ▼<br>rundll32.exe</pre><h3>What happened?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oYQFsThFbiAhVkshuBib7A.png" /></figure><p>WinRAR extracted the executable from the archive.</p><p>The malware executable then started running.</p><p>Shortly afterward, it launched <strong>rundll32.exe</strong>.</p><h3>Why is rundll32.exe important?</h3><p>Windows uses <strong>rundll32.exe</strong> to execute functions stored inside DLL files.</p><p>Many malware families abuse this legitimate Windows utility because security products often trust Windows system binaries.</p><p>Instead of creating an obviously suspicious process, malware hides behind trusted Windows components.</p><p>This technique is commonly referred to as <strong>Living Off the Land (LOLBins)</strong>.</p><h3>Step 3 — System Discovery</h3><p>Before contacting its operators, the malware gathered information about the victim system.</p><p>ANY.RUN detected several MITRE ATT&amp;CK techniques including:</p><ul><li>System Information Discovery</li><li>Registry Query</li><li>System Network Configuration Discovery</li><li>Time Zone Discovery</li></ul><p>The malware collected information such as:</p><ul><li>Computer name</li><li>CPU information</li><li>Windows installation date</li><li>Machine GUID</li><li>Operating system version</li><li>Environment variables</li><li>Installed language</li><li>Time zone</li></ul><h3>Why does malware do this?</h3><p>Attackers want to understand where the malware is running.</p><p>For example, they may want to know:</p><ul><li>Is this a real employee computer?</li><li>Is this a virtual machine?</li><li>Which country is the victim located in?</li><li>What Windows version is installed?</li></ul><p>This information helps malware decide whether to continue execution or terminate itself to avoid detection.</p><h3>Step 4 — DNS Requests</h3><p>One of the most interesting stages was observing the DNS requests.</p><p>The malware contacted several domains, including:</p><ul><li>ipinfo.io</li><li>ipapi.co</li><li>ip-api.com</li></ul><p>At first glance, these domains appear legitimate.</p><p>So why would malware contact them?</p><p>The answer is simple.</p><p>The malware wanted to discover the public IP address of the infected system.</p><p>Imagine introducing yourself to someone over the phone.</p><p>Before continuing the conversation, they first ask,</p><p><em>“Who are you and where are you calling from?”</em></p><p>The malware behaves similarly.</p><p>It first identifies its victim before contacting its command-and-control server.</p><p>This behavior is commonly known as <strong>External IP Discovery</strong>.</p><h3>Step 5 — Network Connections</h3><p>After learning the victim’s public IP address, the malware initiated outbound network connections.</p><p>One connection immediately stood out.</p><pre>IP Address:<br>62.60.226.113</pre><pre>Port:<br>6673</pre><p>Unlike Microsoft update servers or Windows services, this IP was unknown and suspicious.</p><p>The malware repeatedly attempted communication with this server.</p><p>For a SOC analyst, repeated outbound communication to an unfamiliar external server is a significant Indicator of Compromise.</p><h3>Verifying the Suspicious IP</h3><p>Simply observing an IP address is not enough.</p><p>A SOC analyst should always verify suspicious indicators using threat intelligence.</p><p>I checked the IP address using:</p><ul><li>VirusTotal</li><li>AbuseIPDB</li></ul><p>Interestingly, the results differed.</p><h3>AbuseIPDB</h3><p>The IP had only a small number of abuse reports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z79B0xe28ORWyHq5EAhZqg.png" /></figure><p>Its confidence score was low.</p><p>This does <strong>not</strong> necessarily mean the IP is safe.</p><p>AbuseIPDB relies on user-submitted reports, so newer infrastructure may not yet have accumulated many reports.</p><h3>VirusTotal</h3><p>VirusTotal showed that numerous security vendors identified the IP as malicious or associated with malware activity.</p><p>This demonstrates an important lesson for SOC analysts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*InCzeRsrGGkGuPAFf-TGiA.png" /></figure><blockquote><em>Never rely on a single threat intelligence source.</em></blockquote><p>Always validate indicators using multiple platforms before making conclusions.</p><h3>Step 6 — Network Threats</h3><p>ANY.RUN also detected several network-related behaviors.</p><p>Examples included:</p><ul><li>External IP lookup</li><li>Suspicious User-Agent</li><li>SSL certificate observation</li><li>Spamhaus-listed traffic</li><li>Connections to external infrastructure</li></ul><p>Although each event alone may appear harmless, together they form a much stronger picture of malicious behavior.</p><p>This is exactly how modern SIEM platforms detect attacks.</p><p>Instead of relying on one alert, they correlate multiple events into a single incident.</p><h3>Step 7 — Indicators of Compromise (IOCs)</h3><p>The following IOCs were identified during the analysis.</p><p>TypeIndicatorMalware FamilyEmotetFile TypeWindows PE ExecutableMD5e465b7c8de966b096e33dc7ab054b4d0External IP62.60.226.113Port6673Domainsipinfo.ioDomainsipapi.coDomainsip-api.comTechniqueExternal IP DiscoveryTechniqueRegistry QueryTechniqueSystem DiscoveryTechniqueCommand and Control Communication</p><h3>MITRE ATT&amp;CK Techniques Observed</h3><p>During execution, ANY.RUN mapped the malware to several MITRE ATT&amp;CK techniques.</p><p>TechniqueDescriptionT1016System Network Configuration DiscoveryT1012Query RegistryT1082System Information DiscoveryT1124System Time DiscoveryT1218.011Rundll32 ExecutionT1546.015Component Object Model Hijacking</p><p>MITRE ATT&amp;CK mapping helps SOC analysts understand attacker behavior using a standardized framework.</p><h3>Lessons Learned</h3><p>This investigation taught me several valuable concepts about malware behavior.</p><p>The malware did not immediately steal data or encrypt files.</p><p>Instead, it first collected information about the victim’s environment.</p><p>It queried Windows registry values, identified system details, determined the victim’s external IP address, and only then established communication with external infrastructure.</p><p>I also learned the importance of validating Indicators of Compromise using multiple threat intelligence sources. Different platforms may produce different results, so relying on only one source can lead to incorrect conclusions.</p><p>Perhaps the biggest takeaway was understanding that malware analysis is not about finding a single suspicious event. It is about connecting multiple observations — process creation, registry access, DNS lookups, network connections, and threat intelligence — to build a complete picture of the attack.</p><h3>Conclusion</h3><p>Dynamic malware analysis provides valuable insight into how malware behaves in a real environment. By analyzing this Emotet sample inside ANY.RUN, I observed each stage of the execution process — from launching the executable and collecting system information to performing DNS lookups, contacting external servers, and generating Indicators of Compromise.</p><p>This investigation also reinforced the importance of thinking like a SOC analyst. Rather than relying solely on automated detections, understanding the sequence of events and validating evidence through multiple sources is essential for effective threat detection and incident response.</p><p>For future research, I plan to explore static malware analysis using tools such as PEStudio, Detect It Easy (DIE), FLOSS, and Ghidra to better understand the malware’s internal structure and capabilities before execution.</p><p>note:this all investigation and procedure has been conudcted in a well structuredn isolated cloud sandbox for educational and defensive cybersecurity purposes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abeb2377cfdf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a SOC Log Analysis Tool Using Linux and Bash Scripting]]></title>
            <link>https://medium.com/@snkth123/building-a-soc-log-analysis-tool-using-linux-and-bash-scripting-b04a779e2b7e?source=rss-a8199217ddcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/b04a779e2b7e</guid>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[bash-script]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[log-analysis]]></category>
            <dc:creator><![CDATA[Snkth]]></dc:creator>
            <pubDate>Fri, 10 Jul 2026 10:31:25 GMT</pubDate>
            <atom:updated>2026-07-10T10:31:25.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>As an aspiring Security Operations Center (SOC) Analyst, I believe that hands-on practice is one of the best ways to build real cybersecurity skills. Rather than only studying theory, I wanted to create a practical project that simulates how a Tier-1 SOC analyst investigates security logs and identifies suspicious activities.</p><p>In this project, I built a SOC Log Analysis tool using Kali Linux and Bash scripting. The project analyzes simulated security logs, counts different event types, detects failed login attempts, identifies suspicious IP addresses, and automatically generates a security analysis report.</p><p>Throughout this project, I strengthened my understanding of Linux commands, Bash scripting, log analysis, and basic incident detection. It also gave me practical experience with the type of tasks performed by SOC analysts during daily security monitoring.</p><p>Whether you’re a cybersecurity student, a Linux enthusiast, or someone beginning a SOC career, I hope this project provides a useful introduction to automating security log analysis using simple but powerful Linux tools.</p><h3>Why I Built This Project</h3><p>Security analysts rely heavily on log analysis to detect suspicious activities before they become security incidents. Instead of only reading about SOC operations, I wanted to build a small project that simulates a real SOC analyst’s daily workflow.</p><p>The objective was to understand how Linux log analysis works, how Bash scripting can automate repetitive tasks, and how basic command-line tools can quickly extract valuable information from security logs.</p><h3>Project Objective</h3><p>The main objectives of this project were:</p><ul><li>Learn Linux file handling.</li><li>Practice Bash scripting.</li><li>Analyze simulated security logs.</li><li>Detect failed login attempts.</li><li>Identify suspicious IP addresses.</li><li>Generate an automated SOC analysis report.</li><li>Improve practical SOC analyst skills.</li></ul><h3>Project Structure</h3><pre>Soc-Log_Analysis/<br>│<br>├── security_logs.txt<br>├── analyze_logs.sh<br>├── report.txt<br>├── README.md<br>└── screenshots/</pre><p>Each file serves a specific purpose:</p><ul><li><strong>security_logs.txt</strong> — Contains simulated security log entries.</li><li><strong>analyze_logs.sh</strong> — Bash script that automates log analysis.</li><li><strong>report.txt</strong> — Stores the generated analysis report.</li><li><strong>README.md</strong> — Project documentation.</li><li><strong>screenshots/</strong> — Contains screenshots demonstrating the project.</li></ul><h3>Creating Simulated Security Logs</h3><p>The first step was creating a log file named security_logs.txt. It contains different types of events that commonly appear during system monitoring.</p><p>Example log entries:</p><pre>2026-07-10 09:00:15 INFO User likithraj logged in from 192.168.1.10<br>2026-07-10 09:25:17 WARNING Failed login for user admin from 192.168.1.20<br>2026-07-10 09:40:11 ERROR Unauthorized sudo attempt by user sunny</pre><p>The log file includes:</p><ul><li>INFO events</li><li>WARNING events</li><li>ERROR events</li><li>Failed login attempts</li><li>SSH activity</li><li>Administrator activity</li><li>Malware detection</li><li>Suspicious IP addresses</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DW7Y2-qyN7utgx-i0Ghafg.png" /></figure><h3>Linux Commands Used</h3><p>To manually analyze the logs, I used several Linux commands.</p><p>Count total log entries:</p><pre>wc -l security_logs.txt</pre><p>Count INFO logs:</p><pre>grep &quot;INFO&quot; security_logs.txt | wc -l</pre><p>Count WARNING logs:</p><pre>grep &quot;WARNING&quot; security_logs.txt | wc -l</pre><p>Count ERROR logs:</p><pre>grep &quot;ERROR&quot; security_logs.txt | wc -l</pre><p>Count failed login attempts:</p><pre>grep &quot;Failed login&quot; security_logs.txt | wc -l</pre><p>Extract all IP addresses:</p><pre>grep -oE &#39;([0-9]{1,3}\.){3}[0-9]{1,3}&#39; security_logs.txt</pre><p>Display the most frequent IP addresses:</p><pre>grep -oE &#39;([0-9]{1,3}\.){3}[0-9]{1,3}&#39; security_logs.txt | sort | uniq -c | sort -nr</pre><p>These commands demonstrate how Linux utilities can quickly extract meaningful information from log files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DW7Y2-qyN7utgx-i0Ghafg.png" /></figure><h3>Automating the Analysis with Bash</h3><p>Instead of running each command manually, I automated the process by writing a Bash script called analyze_logs.sh.</p><p>The script performs the following tasks:</p><ul><li>Counts total log entries.</li><li>Counts INFO, WARNING, and ERROR events.</li><li>Detects failed login attempts.</li><li>Identifies frequently occurring IP addresses.</li><li>Generates a formatted SOC analysis report.</li><li>Saves the report to report.txt.</li></ul><p>Automation reduces repetitive work and improves efficiency, making it easier to analyze logs consistently.</p><h3>Running the Script</h3><p>After making the script executable:</p><pre>chmod +x analyze_logs.sh</pre><p>I executed it using:</p><pre>./analyze_logs.sh</pre><p>The script automatically analyzed the logs and generated a security report in the terminal while also saving it to report.txt.</p><h3>Sample Output</h3><pre>=======================================<br>SOC LOG ANALYSIS REPORT<br>=======================================</pre><pre>Total Logs: 15<br>INFO Logs: 7<br>WARNING Logs: 5<br>ERROR Logs: 3<br>Failed Login Attempts: 3</pre><pre>Top Suspicious IP Addresses:<br>4 192.168.1.20<br>2 192.168.1.10</pre><pre>=======================================<br>Analysis Completed Successfully<br>=======================================</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNFVV4sh9qsvOSYza1LyzA.png" /></figure><h3>Skills Demonstrated</h3><p>This project helped me strengthen the following skills:</p><ul><li>Linux Administration</li><li>Bash Scripting</li><li>Security Log Analysis</li><li>Threat Detection</li><li>Incident Detection</li><li>IOC Identification</li><li>Log Correlation</li><li>SOC Monitoring Fundamentals</li><li>Command-Line Automation</li></ul><h3>Challenges Faced</h3><p>While working on this project, I encountered several practical challenges:</p><ul><li>Understanding how to parse log files efficiently.</li><li>Learning Bash scripting syntax.</li><li>Formatting command output into a readable report.</li><li>Extracting IP addresses using regular expressions.</li><li>Automating repetitive log analysis tasks.</li></ul><p>Overcoming these challenges improved both my Linux and cybersecurity knowledge.</p><h3>Future Improvements</h3><p>This project can be enhanced further by adding:</p><ul><li>Real-time log monitoring.</li><li>Email alert notifications.</li><li>CSV and PDF report generation.</li><li>Severity-based event classification.</li><li>Splunk integration.</li><li>ELK Stack integration.</li><li>Wazuh integration.</li><li>Threat intelligence integration.</li></ul><h3>GitHub Repository</h3><p>The complete source code, Bash script, security logs, report, and project screenshots are available in my GitHub repository.</p><p>GitHub:<br><a href="https://github.com/likith-raj/Soc-Log_Analysis">https://github.com/likith-raj/Soc-Log_Analysis</a></p><h3>Conclusion</h3><p>Building this SOC Log Analysis project gave me valuable hands-on experience with Linux, Bash scripting, and security log analysis. It demonstrated how simple command-line tools can automate repetitive SOC tasks and quickly identify potential security events.</p><p>This project represents an important milestone in my cybersecurity learning journey. I look forward to building more advanced projects involving SIEM platforms, threat hunting, malware analysis, and incident response as I continue working toward a career as a SOC Analyst.</p><p>Thank you for reading! If you have any suggestions or feedback, feel free to connect with me on GitHub or LinkedIn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b04a779e2b7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>