<?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 codeword Chronicles on Medium]]></title>
        <description><![CDATA[Stories by codeword Chronicles on Medium]]></description>
        <link>https://medium.com/@yashaswikankarla?source=rss-65e9ba554b6b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3kQFV8i5L2KSb1HYv8Sbag.png</url>
            <title>Stories by codeword Chronicles on Medium</title>
            <link>https://medium.com/@yashaswikankarla?source=rss-65e9ba554b6b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:54:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yashaswikankarla/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[Recovering Speech from Noise: An Audio Denoising and Transcription Case Study]]></title>
            <link>https://medium.com/@yashaswikankarla/recovering-speech-from-noise-an-audio-denoising-and-transcription-case-study-06264b98668e?source=rss-65e9ba554b6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/06264b98668e</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[audio-processing]]></category>
            <category><![CDATA[cybercrime]]></category>
            <category><![CDATA[voice-recognition]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[codeword Chronicles]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 16:15:10 GMT</pubDate>
            <atom:updated>2026-11-17T16:15:10.422Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Not all investigations begin with clean and structured data. In many real-world scenarios, valuable information is hidden behind noise, distortion, and incomplete signals. Extracting meaningful intelligence often requires a combination of preprocessing, analysis, and validation.</p><p>In this case study, I worked with a heavily degraded audio recording where speech was obscured by background interference. The objective was to recover intelligible speech and produce a usable transcript from the recording.</p><p>Using a combination of source separation, audio enhancement, and automated transcription techniques, I developed a workflow that transformed noisy audio into readable text.</p><h3>Objectives</h3><p>The primary goals of this project were:</p><ul><li>Improve speech clarity in a noisy recording.</li><li>Reduce background interference and distortion.</li><li>Isolate speech from non-speech audio.</li><li>Prepare the audio for transcription.</li><li>Generate an accurate text transcript.</li><li>Evaluate the effectiveness of the recovery workflow.</li></ul><h3>Tools and Technologies</h3><p>The project utilized:</p><ul><li>Demucs</li><li>FFmpeg</li><li>Whisper</li><li>Python</li><li>WAV Audio Processing Tools</li></ul><p>Each tool contributed to a different stage of the workflow, from speech isolation to transcription generation.</p><h3>Understanding the Challenge</h3><p>The source recording contained speech that was difficult to understand due to multiple forms of interference.</p><p>Some of the challenges included:</p><ul><li>Background noise</li><li>Audio distortion</li><li>Competing sound sources</li><li>Reduced speech intelligibility</li><li>Poor transcription performance on raw audio</li></ul><p>Direct transcription of the original recording produced unreliable results, making preprocessing a necessary step.</p><h3>Investigation Methodology</h3><h3>1. Initial Audio Assessment</h3><p>The first step was understanding the quality and characteristics of the recording.</p><p>Before applying any processing techniques, I evaluated:</p><ul><li>Audio format</li><li>Signal quality</li><li>Types of noise present</li><li>Overall intelligibility</li></ul><p>This assessment helped determine the most appropriate enhancement strategy.</p><h3>2. Speech Isolation Using Source Separation</h3><p>To improve clarity, I used Demucs to separate the vocal component from the rest of the audio signal.</p><p>Source separation works by isolating meaningful speech while reducing interference from background sounds.</p><p>This stage significantly improved the readability of the recording and created a dedicated speech-focused track.</p><h3>3. Audio Standardization</h3><p>After isolating speech, the audio was converted into a format optimized for automated transcription.</p><p>Using FFmpeg, the vocal track was standardized into a transcription-friendly format, ensuring compatibility and consistent processing.</p><p>This step also helped improve transcription performance by reducing format-related issues.</p><h3>4. Automated Speech Recognition</h3><p>The processed audio was then analyzed using Whisper.</p><p>Whisper generated a text-based transcript of the recovered speech, converting spoken language into searchable and readable content.</p><p>Compared to direct transcription of the original recording, the enhanced version produced significantly better results.</p><h3>5. Validation and Review</h3><p>The final transcript was reviewed to evaluate:</p><ul><li>Speech intelligibility</li><li>Accuracy of recovered content</li><li>Remaining transcription errors</li><li>Limitations introduced by residual noise</li></ul><p>This final stage helped assess the effectiveness of the complete workflow.</p><h3>Key Findings</h3><p>Several important observations emerged during the project.</p><h3>Audio Preprocessing Matters</h3><p>The quality of transcription output is heavily influenced by audio quality.</p><p>Significant improvements were achieved before transcription even began simply by improving the source signal.</p><h3>Source Separation Improved Clarity</h3><p>Separating speech from interference made a noticeable difference in intelligibility.</p><p>Audio that was previously difficult to interpret became much easier to understand after vocal isolation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*BuI4aYmg5r9IPFt2p7PB8Q.png" /></figure><h3>Automated Transcription Benefits from Clean Inputs</h3><p>Whisper performed considerably better on the processed audio than on the original recording.</p><p>This highlighted the importance of signal enhancement in speech-to-text workflows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Ado8fosp3k7YF-fU9K_TJw.png" /></figure><h3>Some Limitations Remained</h3><p>Although the workflow significantly improved results, some sections remained difficult to recover due to residual noise and distortion.</p><p>Perfect reconstruction is not always possible, especially when parts of the original signal are heavily degraded.</p><h3>Lessons Learned</h3><h3>Information Recovery Is an Iterative Process</h3><p>Useful information is often extracted through multiple stages of refinement rather than a single tool or technique.</p><h3>Signal Quality Drives Analytical Quality</h3><p>The quality of downstream analysis is directly related to the quality of incoming data.</p><p>Improving the signal often improves every subsequent stage of the workflow.</p><h3>Tool Selection Matters</h3><p>Different tools solved different parts of the problem:</p><ul><li>Demucs improved speech isolation.</li><li>FFmpeg standardized the audio.</li><li>Whisper converted speech into text.</li></ul><p>The effectiveness of the final result depended on how these tools worked together.</p><h3>Documentation Is Essential</h3><p>Documenting each stage of the workflow made the process reproducible and easier to evaluate.</p><p>Repeatable workflows are just as important as successful outcomes.</p><h3>Conclusion</h3><p>This project demonstrated how audio processing and automated transcription can be combined to recover useful information from degraded recordings.</p><p>By applying source separation, audio enhancement, and speech recognition techniques, it was possible to significantly improve speech intelligibility and generate a usable transcript from a noisy recording.</p><p>Beyond the technical outcome, the project reinforced a broader lesson: valuable information is often present in imperfect data, and a structured analytical approach can help uncover it.</p><p>The complete technical report and workflow are available in my GitHub cybersecurity case study repository.</p><h3>Explore the Full Workflow</h3><p>The complete processing pipeline, methodology, and technical report are available on GitHub:</p><p>🔗 <a href="https://github.com/Yashaswi-kankarla/cybersecurity-case-studies/tree/audio-denoising-transcription">https://github.com/Yashaswi-kankarla/cybersecurity-case-studies/tree/audio-denoising-transcription</a></p><p>If you found this case study interesting, feel free to connect with me on LinkedIn and explore the complete investigation on GitHub.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=06264b98668e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uncovering Persistence and Command-and-Control Behavior: A Malware Analysis Case Study]]></title>
            <link>https://medium.com/@yashaswikankarla/uncovering-persistence-and-command-and-control-behavior-a-malware-analysis-case-study-9feceb61e69a?source=rss-65e9ba554b6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9feceb61e69a</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[codeword Chronicles]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 16:11:16 GMT</pubDate>
            <atom:updated>2026-11-17T16:11:16.186Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Malware analysis is rarely about finding a single malicious indicator. Modern malware often combines persistence, defense evasion, and command-and-control communication to maintain access while avoiding detection.</p><p>In this case study, I investigated a suspicious Windows executable and its associated DLL using a combination of static and dynamic analysis techniques. The goal was to understand the malware’s behavior, identify indicators of compromise, and determine how it maintained persistence and communicated with external systems.</p><h3>Objectives</h3><p>The primary objectives of the investigation were:</p><ul><li>Verify execution of the suspicious sample.</li><li>Identify malicious artifacts and indicators of compromise.</li><li>Analyze persistence mechanisms.</li><li>Observe runtime process and registry activity.</li><li>Monitor network behavior and command-and-control attempts.</li><li>Map observed techniques to the MITRE ATT&amp;CK framework.</li></ul><h3>Analysis Environment</h3><p>The analysis was conducted in an isolated virtual environment to safely observe malware behavior without affecting production systems.</p><p>The investigation utilized:</p><ul><li>PEStudio</li><li>PECmd</li><li>Procmon</li><li>Regshot</li><li>Wireshark</li><li>Certutil</li><li>Windows 10 Virtual Machine</li></ul><p>This combination of tools allowed examination of both the malware’s structure and its behavior during execution.</p><h3>Investigation Methodology</h3><h3>1. Execution Verification</h3><p>The first step was to confirm that the suspicious executable had actually been run.</p><p>Execution artifacts provided valuable forensic evidence regarding launch activity and established a foundation for further analysis.</p><h3>2. Static Analysis</h3><p>Static analysis focused on examining the executable and DLL without running them.</p><p>Key areas of interest included:</p><ul><li>Imported functions</li><li>Embedded strings</li><li>Metadata</li><li>Resources</li><li>Potential signs of packing or obfuscation</li></ul><p>Static analysis provides early indicators of malicious intent and helps identify areas requiring deeper investigation during runtime analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*8QHnO4Aeu3GanH7SnPNX_Q.png" /></figure><h3>3. Dynamic Analysis</h3><p>The samples were executed within an isolated environment while monitoring:</p><ul><li>Process creation</li><li>File activity</li><li>Registry modifications</li><li>DLL loading behavior</li><li>System interactions</li></ul><p>Dynamic analysis often reveals behavior that is intentionally hidden during static inspection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*7m2KcAqvgUtx4h8pbjXmww.png" /></figure><h3>4. Registry Analysis</h3><p>Registry snapshots were collected before and after execution.</p><p>Comparing the two states helped identify persistence mechanisms and other system modifications introduced by the malware.</p><h3>5. Network Analysis</h3><p>Network traffic generated during execution was captured and inspected.</p><p>The goal was to determine:</p><ul><li>Whether the malware attempted outbound communication</li><li>Potential command-and-control infrastructure</li><li>Indicators of beaconing behavior</li><li>Evidence of encrypted communication channels</li></ul><h3>6. Evidence Correlation</h3><p>Findings from process monitoring, registry analysis, and network captures were correlated to develop a complete understanding of the malware’s behavior.</p><p>This approach reduces the risk of drawing conclusions from isolated observations.</p><h3>Key Findings</h3><p>The investigation revealed several behaviors commonly associated with modern Trojan malware.</p><h3>Persistence Mechanisms</h3><p>Analysis identified modifications designed to maintain execution after system restart.</p><p>Registry-based persistence was observed, indicating an attempt to establish long-term presence on the host system.</p><h3>Suspicious DLL Activity</h3><p>The malware loaded an associated DLL that exhibited characteristics commonly linked to malicious functionality.</p><p>The DLL contained artifacts associated with file manipulation, process interaction, and stealth-oriented behavior.</p><h3>Process Abuse</h3><p>Runtime monitoring revealed suspicious process activity and interaction with legitimate Windows components.</p><p>This behavior suggested attempts to blend malicious actions with normal operating system processes.</p><h3>Network Communication</h3><p>Network captures revealed outbound communication attempts and encrypted traffic patterns.</p><p>Several connections appeared consistent with command-and-control style behavior, indicating efforts to communicate with external infrastructure.</p><h3>Defense Evasion Techniques</h3><p>Evidence suggested the use of anti-analysis and evasion-oriented functionality, including techniques designed to complicate debugging and behavioral inspection.</p><h3>MITRE ATT&amp;CK Alignment</h3><p>Many of the observed behaviors aligned with common ATT&amp;CK tactics and techniques, including:</p><ul><li>Persistence</li><li>Defense Evasion</li><li>Command and Control</li><li>Execution</li></ul><p>Mapping findings to ATT&amp;CK helped place individual indicators into a broader adversary-behavior context.</p><h3>Lessons Learned</h3><h3>Static and Dynamic Analysis Complement Each Other</h3><p>Static analysis provided visibility into suspicious imports, strings, and artifacts, while dynamic analysis confirmed how those components behaved during execution.</p><p>Neither approach alone would have provided a complete picture.</p><h3>Persistence Is a Strong Indicator</h3><p>Registry modifications often provide critical evidence regarding malware intent and operational objectives.</p><p>Persistence mechanisms frequently reveal how malware intends to survive system restarts and maintain access.</p><h3>Network Activity Adds Context</h3><p>Network analysis helped explain behaviors that were not immediately obvious from process and registry observations alone.</p><p>Outbound communications often reveal the broader purpose of a malware family.</p><h3>Correlation Strengthens Conclusions</h3><p>Strong conclusions emerged only after combining findings from multiple sources.</p><p>Process activity, registry changes, and network communication together provided a clearer understanding of the malware’s overall behavior.</p><h3>Conclusion</h3><p>This investigation demonstrated the importance of a structured malware analysis workflow. By combining static inspection, runtime monitoring, registry analysis, and network traffic investigation, it was possible to identify persistence mechanisms, suspicious process behavior, command-and-control communication attempts, and defense-evasion techniques.</p><p>The experience reinforced the value of evidence-driven analysis and highlighted how multiple investigative perspectives combine to reveal the true capabilities of a malicious sample.</p><p>The complete technical report and supporting findings are available in my GitHub cybersecurity case study repository.</p><h3>Explore the Full Investigation</h3><p>The complete technical report, screenshots, MITRE ATT&amp;CK mapping, and supporting analysis are available on GitHub:</p><p>🔗 <a href="https://github.com/Yashaswi-kankarla/cybersecurity-case-studies/tree/malware-analysis">https://github.com/Yashaswi-kankarla/cybersecurity-case-studies/tree/malware-analysis</a></p><p>If you found this case study interesting, feel free to connect with me on LinkedIn and explore the complete investigation on GitHub.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9feceb61e69a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Investigating a Multi-Endpoint Security Incident Using Splunk: A Log Analysis Case Study]]></title>
            <link>https://medium.com/@yashaswikankarla/investigating-a-multi-endpoint-security-incident-using-splunk-a-log-analysis-case-study-7ba0c5b4c107?source=rss-65e9ba554b6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ba0c5b4c107</guid>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[splunk]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[log-analysis]]></category>
            <dc:creator><![CDATA[codeword Chronicles]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 16:05:10 GMT</pubDate>
            <atom:updated>2026-11-17T16:05:10.505Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Security analysts rarely encounter incidents where the entire attack path is immediately visible. More often, investigations begin with scattered security events that must be correlated across multiple sources to reconstruct what actually happened.</p><p>In this case study, I performed a forensic investigation of endpoint and security logs to identify compromised hosts, determine the initial infection vector, establish the attack timeline, and identify the most likely patient zero.</p><h3>Objectives</h3><p>The primary goals of the investigation were:</p><ul><li>Identify compromised endpoints</li><li>Reconstruct the attack timeline</li><li>Determine the initial compromise vector</li><li>Identify patient zero</li><li>Assess attack progression</li><li>Recommend remediation actions</li></ul><h3>Environment and Tools</h3><p>The investigation was performed using:</p><ul><li>Splunk Enterprise</li><li>Endpoint Security Logs</li><li>Web Activity Logs</li><li>PowerShell Hash Verification</li></ul><p>Splunk served as the primary platform for log ingestion, correlation, and timeline analysis.</p><h3>Investigation Methodology</h3><h3>1. Data Validation</h3><p>Before beginning the investigation, log integrity was verified to ensure analysis was being performed on trustworthy data.</p><p>Data validation is often overlooked but remains an essential step in forensic workflows.</p><h3>2. Log Ingestion and Normalization</h3><p>Multiple log sources were imported into Splunk and validated for proper parsing.</p><p>The objective was to ensure all relevant security events could be correlated from a single analysis platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/937/1*ZjPsWeUx-_BqaGEHhfyi3Q.png" /></figure><h3>3. Suspicious Event Identification</h3><p>To reduce noise, only security-relevant events were isolated for investigation.</p><p>These included:</p><ul><li>Antivirus detections</li><li>Quarantine events</li><li>Web-block activities</li><li>Endpoint security alerts</li></ul><p>Filtering significantly reduced the investigation scope and allowed focus on potentially malicious activity.</p><h3>4. Timeline Reconstruction</h3><p>One of the most valuable techniques in incident response is chronological reconstruction.</p><p>By identifying the earliest suspicious activity associated with each endpoint, it became possible to understand:</p><ul><li>Which systems were affected first</li><li>How the incident spread</li><li>Whether multiple systems were compromised simultaneously</li></ul><h3>5. Endpoint Correlation</h3><p>Events were correlated across endpoints to identify common indicators and attack patterns.</p><p>This step revealed relationships between detections, quarantines, and network activity that would not have been visible through isolated event review.</p><h3>6. Risk Scoring</h3><p>A severity-based scoring methodology was applied to prioritize affected systems.</p><p>Risk scoring helps investigators focus on systems that pose the greatest threat while maintaining visibility across the full attack surface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/943/1*0-68FjcgSxj-rJFa28MkBg.png" /></figure><h3>Key Findings</h3><p>The investigation uncovered several compromised systems showing evidence of malicious activity.</p><p>The analysis indicated:</p><ul><li>Malicious file execution as the likely initial compromise vector</li><li>Subsequent command-and-control style communication attempts</li><li>Progressive spread of suspicious activity across additional endpoints</li><li>Clear evidence allowing identification of the earliest affected system</li></ul><p>Timeline reconstruction proved particularly valuable in determining how the incident evolved over time.</p><h3>Lessons Learned</h3><p>Several important lessons emerged from this investigation:</p><h3>Correlation Beats Individual Alerts</h3><p>A single alert rarely tells the whole story.</p><p>Meaningful conclusions emerged only after correlating multiple sources of evidence.</p><h3>Timelines Matter</h3><p>Understanding when events occur is often just as important as understanding what occurred.</p><p>Timeline reconstruction provided critical context for identifying the infection sequence.</p><h3>Prioritization Improves Efficiency</h3><p>Risk scoring helped focus investigation efforts on the most significant systems first.</p><h3>Evidence Should Drive Conclusions</h3><p>The investigation relied on observable artifacts rather than assumptions, ensuring findings could be supported and reproduced.</p><h3>Conclusion</h3><p>This project reinforced the importance of structured investigations, event correlation, and timeline analysis in modern security operations.</p><p>By leveraging Splunk for centralized analysis, it was possible to identify compromised systems, reconstruct attack progression, and develop actionable remediation recommendations.</p><p>The complete technical report and supporting material are available in my GitHub portfolio repository.</p><h3>Explore the Full Investigation</h3><p>The complete Splunk workflow, queries, timeline analysis, and findings are available on GitHub:</p><p>🔗 <a href="https://github.com/Yashaswi-kankarla/cybersecurity-case-studies/tree/log-analysis">https://github.com/Yashaswi-kankarla/cybersecurity-case-studies/tree/log-analysis</a></p><p>If you found this case study interesting, feel free to connect with me on LinkedIn and explore the complete investigation on GitHub.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ba0c5b4c107" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Brochure]]></title>
            <link>https://medium.com/@yashaswikankarla/the-brochure-66d5cb38a741?source=rss-65e9ba554b6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/66d5cb38a741</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[hacker-holidays-2026]]></category>
            <dc:creator><![CDATA[codeword Chronicles]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 16:22:12 GMT</pubDate>
            <atom:updated>2026-08-04T16:22:12.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YjMMYu-BjT2QJbbrupZBjA.png" /></figure><p><strong>“The brochure</strong>” is a warm up room in the <strong>Hackers Holiday</strong> CTF event. This room has open on for-hand the event. The room gives an idea to participants, how the rooms and challenges may look.</p><p>This room has build on the concept of OSINT (Open Source INTelligence) Difficulty level is Easy.</p><p>The room contains of 2 tasks, where as first is as shown in below image . This says a lot about the resort “The Byte Lotus”. That shows how the resort has high rating, their brochure, the app and vera, the personal concierge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*enSTbYvkW99TaXg0vM105g.png" /><figcaption>Task 1</figcaption></figure><p>The second task shows the details and briefing of the task.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*7Dy-STB-id4KSScxmQE17Q.png" /><figcaption>Task 2</figcaption></figure><p>This task has the brochure in the room access section, a zip file is downloaded on clicking the <strong>Download task file </strong>button. Extrat the zip file and you will find the Brochure in the file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*FW9OeF8PNvPxlaxaMlp7cg.png" /><figcaption>The Brochure</figcaption></figure><p>The brochure says that “Some things aren’t posted. Some clues are. Find us on Instagram or not” suggesting to look for the clue on instagram(Because instagram is a open source platform and looking for information on public platform is OSINT).</p><p>open instagram search for the resort “<strong>T</strong>he Byte Lotus”, you will find an instagram account with 2 posts and lot of comments. You will find the flag in the comments of one of the posts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66d5cb38a741" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacker Holidays 2026]]></title>
            <link>https://medium.com/@yashaswikankarla/hacker-holidays-2026-265e22669e99?source=rss-65e9ba554b6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/265e22669e99</guid>
            <category><![CDATA[ctf-writeup]]></category>
            <category><![CDATA[ctf]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[codeword Chronicles]]></dc:creator>
            <pubDate>Thu, 30 Jul 2026 10:43:05 GMT</pubDate>
            <atom:updated>2026-07-30T10:43:05.437Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dmIByRyIomK9DSOZW3njJw.png" /></figure><p>Hey,</p><p>Those who have not heard of this “Hacker Holiday”, this is a CTF event organized by TryHackMe.</p><p>TryHackMe is a cybersecurity learning platform that teaches hacking and defense skills through hands‑on labs and gamified challenges. It’s widely used by beginners and professionals to practice real‑world scenarios in a safe environment.</p><p>Hacker Holiday is a CTF(Capture The Flag) event a beginner friendly , themed around a five-star resort named The Byte Lotus. This is a 14 day cyber security challenge running from July 27, 2026. Each day, one challenge will be unlocked at 4.00 pm UTC.</p><p>Every afternoon at 4PM UTC, a new room opens inside the hotel. Each one is a self-contained hacking challenge: <strong>OSINT</strong>, <strong>web exploitation</strong>,<strong> cloud security</strong>, <strong>forensics</strong>, <strong>AI prompt attacks</strong>. The difficulty starts at beginner and works its way up. You don’t need experience, just curiosity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NsCkvZa1LpXzB0Z_0fS42g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*ZXizO2UnQVioELRYHJEnKQ.png" /></figure><h3>🏨 Event Overview</h3><ul><li><strong>Name:</strong> Hacker Holidays 2026</li><li><strong>Duration:</strong> 14 days (July 27 — August 9, 2026)</li><li><strong>Format:</strong> One new challenge room opens daily at <strong>4 PM UTC</strong>.</li><li><strong>Theme:</strong> The Byte Lotus resort (five‑star hotel, zero‑star security).</li><li><strong>Difficulty:</strong> Starts beginner‑friendly, gradually increases.</li><li><strong>Prize Pool:</strong> Over <strong>$50,000</strong> in rewards for participants.</li><li><strong>Eligibility:</strong> Free and open to all; beginners especially welcome.</li></ul><p>Above is the Hacker Holidays roadmap, 14 days — 14 CTFs each unique challenge, each new concept.</p><h3>🧩 Challenge Types</h3><p>Each day’s room focuses on a different area of cybersecurity:</p><ul><li><strong>OSINT</strong> (Open Source Intelligence)</li><li><strong>Web Hacking</strong></li><li><strong>Cloud Security</strong></li><li><strong>Forensics</strong></li><li><strong>AI Prompt Attacks</strong></li><li><strong>Boot2Root</strong></li></ul><h3>✨ <strong>Call to Action</strong></h3><p>I’ll be blogging my journey through all 14 days of Hacker Holidays — sharing tools, lessons, and takeaways. If you’re curious about cybersecurity or want to test your skills, <strong>join the event on TryHackMe and hack along with me</strong>. It’s free, beginner‑friendly, and a great way to learn by doing.</p><p>Stay tuned here for daily updates, and connect with me on LinkedIn, YouTube, or GitHub to follow the full journey. Let’s learn, hack, and grow together!</p><h3>🌐 Connect With Me</h3><ul><li><strong>YouTube</strong> → <a href="http://twitter.com/codewordTECH">@codewordTECH</a></li><li><strong>LinkedIn</strong> → <a href="http://www.linkedin.com/in/kankarla-yashaswi">www.linkedin.com/in/kankarla-yashaswi</a></li><li><strong>Twitter/X</strong> → @codewordTechh</li><li><strong>GitHub</strong> → <a href="http://www.github.com/yashaswi-kankarla">www.github.com/yashaswi-kankarla</a></li><li><strong>Instagram</strong> → www.<a href="https://www.instagram.com/codewordtech/">instagram.com/codewordtech/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=265e22669e99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to Codeword Chronicles]]></title>
            <link>https://medium.com/@yashaswikankarla/welcome-to-codeword-chronicles-6f5bb59d3733?source=rss-65e9ba554b6b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f5bb59d3733</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[introduction]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[art]]></category>
            <dc:creator><![CDATA[codeword Chronicles]]></dc:creator>
            <pubDate>Thu, 30 Jul 2026 05:55:06 GMT</pubDate>
            <atom:updated>2026-07-30T08:40:32.180Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello, I’m Yash. I’m a cybersecurity fresher, creator, and someone who loves exploring the intersections of <strong>technology, art, philosophy, and history</strong> with a hopeful heart and a bright vision for the future.</p><p>This blog is my personal space to share fragments of my journey — whether it’s lessons from my tech career, reflections on the philosophy of machines, creative experiments in art, or stories from history that still shape our digital world today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*3kQFV8i5L2KSb1HYv8Sbag.png" /></figure><h3>What you’ll find here:</h3><ul><li><strong>Cybersecurity &amp; Tech</strong> → insights from my career path, learning experiences, and evolving industry trends.</li><li><strong>Art &amp; Creativity</strong> → explorations that blend imagination with technology.</li><li><strong>Philosophy &amp; History</strong> → reflections on how ideas and events shape the way we think about tech today.</li></ul><p>I believe knowledge grows when it’s shared. This blog is my way of sparking conversations, connecting ideas, and leaving behind a trail of thoughts — like fragments of tomorrow waiting to be pieced together.</p><p>Thanks for joining me on this journey. Together, we can explore, question, and create a future full of promise and possibility. I’m excited about what lies ahead and hopeful that through sharing and learning, we can build something meaningful and inspiring.</p><p>This blog is a place where I’ll explore different sides of myself — my journey in cybersecurity and technology, my reflections on philosophy and history, and my creative experiments in art. Each theme stands on its own, but together they form the bigger picture of who I am and what I’m learning.</p><p>My hope is that these writings spark curiosity, invite reflection, and connect with readers who share an interest in any of these paths. Whether you come here for tech insights, philosophical questions, historical lessons, or creative expression, you’ll find something worth exploring.</p><p>Thanks for being here at the start. Let’s grow this space into a collection of ideas, stories, and perspectives worth revisiting.</p><h3>🌐 Connect With Me</h3><ul><li><strong>YouTube</strong> → <a href="http://twitter.com/codewordTECH">@codewordTECH</a></li><li><strong>LinkedIn</strong> → www.<a href="https://#">linkedin.com/in/</a>kankarla-yashaswi</li><li><strong>Twitter/X</strong> → @codewordTechh</li><li><strong>GitHub</strong> → www.<a href="https://#">github.com/yash</a>aswi-kankarla</li><li><strong>Instagram</strong> → www.<a href="https://www.instagram.com/codewordtech/">instagram.com/codewordtech/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f5bb59d3733" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>