<?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 TanmayDhanula on Medium]]></title>
        <description><![CDATA[Stories by TanmayDhanula on Medium]]></description>
        <link>https://medium.com/@tanmaydhanula1234?source=rss-4addcfc91375------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8caXXGNrN3-WRAa9_aMCmA.png</url>
            <title>Stories by TanmayDhanula on Medium</title>
            <link>https://medium.com/@tanmaydhanula1234?source=rss-4addcfc91375------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:42:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tanmaydhanula1234/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[SOC145 — Ransomware Detected — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc145-ransomware-detected-letsdefend-dc04e5c96d17?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc04e5c96d17</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[ransomeware]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[alert-investigation]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Sat, 21 Nov 2026 11:06:06 GMT</pubDate>
            <atom:updated>2026-11-21T11:06:06.414Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Management</h3><p>I started by reviewing the case details and identifying the affected machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IGYhphM357IqrVMLB_o1ow.png" /></figure><ul><li><strong>Hostname:</strong> MarkPRD</li><li><strong>IP Address:</strong> 172.16.17.88</li></ul><p>These details helped me identify the system involved in the alert and establish the starting point for the investigation.</p><h3>Log Management</h3><p>Next, I moved to the <strong>Log Management</strong> tab to filter and review the available network traffic. While examining the logs, I noticed that the recorded activity was from a date much earlier than the alert trigger date. This date mismatch was important to consider before correlating the logs with the current alert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0aJh_7SKz0RLLCPBE-TbjA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*g-mgRWXTolpy_HGpuAQKvA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/1*I5Fad92S3NjbwTWibK12cw.png" /></figure><h3>Containment</h3><p>Since the investigation confirmed that the machine was infected with ransomware, immediate containment was necessary. I proceeded with isolating the affected machine to prevent the ransomware from spreading across the network and causing further damage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S32lq7Qy4hnn1bstIsvyMw.png" /></figure><h3>Process History</h3><p>I also reviewed the <strong>Process History</strong> to identify any unusual or suspicious process activity on the affected machine. During the analysis, I noticed processes that appeared suspicious and required further investigation. This helped provide additional context about the activity taking place on the infected system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/452/1*jTTXk36efEI91_wPnxH03Q.png" /></figure><h3>Playbook Guide</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*fae7sX3j03_zvzfe7upRVQ.png" /></figure><p>After reviewing the logs and process history, I found that the suspicious service was configured to launch automatically whenever the system boots. This indicates a possible persistence mechanism used by the ransomware to maintain its presence on the infected machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*HRpoqZBW_bzmyKvEdzsVGQ.png" /></figure><p>The suspicious service was not quarantined. Based on the log and process history analysis, I found that it was configured to start automatically during system boot, indicating a possible persistence mechanism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/987/1*63fp0gZZgPdnlVP6j-87Jg.png" /></figure><h4>VirusTotal Analysis</h4><p>Next, I used <strong>VirusTotal</strong> to check the ransomware file hash and review its detection results. This helped me verify whether the file was recognized as malicious by multiple security vendors and gather additional threat intelligence for the investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZcU_7edqrkzVa_eAfU9uLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/990/1*rbmI_exbuNihuS6jRC72xg.png" /></figure><p>It is not accessed.</p><h3><strong>Add Artifacts:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*nRHY1Ah3ygnXutduFi2g4A.png" /></figure><p>We add ransomware hash as artifact.</p><h3><strong>Analyst Note:</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*I3W2f83yDMvqiZ9sXfPTSQ.png" /></figure><h3>Final Verdict &amp; Alert Closure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZsJJXrm9Jed8u2J6Lf4_Q.png" /></figure><p>After completing the investigation, I documented all the findings and added the necessary analysis comments. Based on the evidence collected, I classified the incident as a <strong>True Positive</strong>. With the investigation notes completed and the verdict recorded, I proceeded to close the alert.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc04e5c96d17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC105 — Requested T.I. URL address-LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc105-requested-t-i-url-address-letsdefend-1958496a28f3?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/1958496a28f3</guid>
            <category><![CDATA[investigation]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 11:15:28 GMT</pubDate>
            <atom:updated>2026-11-20T11:15:28.607Z</atom:updated>
            <content:encoded><![CDATA[<h3>SOC105 — Requested T.I. URL address</h3><p>Alert Details:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0lkpo_k0JyPtX8zVtADDA.png" /></figure><ul><li><strong>Alert Meaning</strong>: The alert was triggered by a rule related to <strong>Threat Intelligence URL request</strong> (SOC105). It specifically involves a request to the URL <a href="https://bit.ly/TAPSCAN">https://bit.ly/TAPSCAN</a> by a user named <strong>Mark</strong> from <strong>MarksPhone</strong> with source address: 10.15.15.12 which was allowed through the network.</li><li><strong>Interesting Fields </strong>:</li><li><strong>Source Address</strong>: 10.15.15.12 (internal IP)</li><li><strong>Destination Address</strong>: 67.199.248.10 (bit.ly IP)</li><li><strong>Request URL</strong>: <a href="https://bit.ly/TAPSCAN">https://bit.ly/TAPSCAN</a></li><li><strong>User Agent</strong>: Windows NT 5.1, Chrome.</li></ul><p>With that out of the way we can start with the playbook investigations.</p><h3>Phase 1 — Analyze Threat Intel Data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*1nc1TkVsgf702FXL-dXpmA.png" /></figure><p>We need to first check the destination IP address against some threat intel dbs:</p><p><strong>VirusTotal :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFE11zuNwzEIVCiQnBTEIw.png" /></figure><p>Several security vendors have already marked the IP address as malicious. To strengthen this finding, I decided to cross-check it using additional threat intelligence sources. Checking multiple platforms helps build a clearer picture of the IP’s reputation and any suspicious activity associated with it. For this, I used another threat intelligence tool to investigate 67.199.248.10.</p><p><strong>AbuseIPDB :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*OdRuspSO9ITGUqCYblCpJw.png" /></figure><p>The threat score is relatively low, so it doesn’t indicate a major threat. However, the reported abuse suggests that the IP address may have been involved in some suspicious activity. To get a better understanding of the situation, I decided to move on and investigate the associated URL.</p><p><strong>VirusTotal :</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IlZE4mYoaeC_ny1f0DN9w.png" /></figure><p><strong>URLSCAN:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DpVZwD43vQad8av6CuZOIw.png" /></figure><p>We could see screenshots of where the link redirected to :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tV7gdHYLqLDIvImaTcKcOA.png" /></figure><p>After reviewing the available ratings, user feedback, and download statistics, I found no strong indicators of malicious activity. Based on these findings, the IP address and associated URL do not appear to be malicious.</p><h3>Phase 2 — Add Artifacts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*5jlfJK-fpyIjh8a7eVc-1A.png" /></figure><h3>Phase 3 — Analyst Note</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*AuW6yRPjAw0OJy4v7LfBVw.png" /></figure><p>Reviewed the source IP 67.199.248.10 and associated URL using multiple threat intelligence sources. Although minor abuse reports were found, the URL and destination website showed no malicious indicators. No additional IOCs were identified. <strong>Final Verdict: False Positive.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*a8TJM28BlnrY674j7DI-cQ.png" /></figure><p>The investigation is complete. After reviewing the IP reputation, associated URL, and available threat intelligence reports, no evidence of malicious activity was found. All observations were documented, and the alert was closed as a <strong>False Positive</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1958496a28f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC120 — Phishing Mail Detected — Internal to Internal — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc120-phishing-mail-detected-internal-to-internal-letsdefend-07e737853478?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/07e737853478</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[log-analysis]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[phishing-email]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 17:36:16 GMT</pubDate>
            <atom:updated>2026-11-17T17:36:16.353Z</atom:updated>
            <content:encoded><![CDATA[<h3>Step 1 — Creating a Case &amp; Initial Email Analysis</h3><p>Since the email was marked as <strong>Allowed</strong>, I decided to create a case and investigate it further to determine whether it contained any suspicious activity.</p><p>I started by reviewing the email details and answering the initial playbook questions.</p><h3>Email Details</h3><ul><li><strong>When Was It Sent?</strong> February 7, 2021, at 04:24 AM</li><li><strong>SMTP Address:</strong> 172.16.20.3</li><li><strong>Sender Address:</strong> john@letsdefend.io</li><li><strong>Recipient Address:</strong> susie@letsdefend.io</li><li><strong>Is the Email Content Suspicious?</strong> No</li><li><strong>Are There Any Attachments?</strong> No</li></ul><p>Based on the initial review, the email content did not appear suspicious, and there were no attachments. However, since the email was allowed through the security system, I continued the investigation to verify its legitimacy.</p><h3>Step 2 — Inspecting the Email</h3><p>Next, I opened the email to examine its actual content. I found that it contained only plain text, with no suspicious message content or attachments.</p><p>Based on this initial inspection, there were no obvious signs of malicious activity in the email. However, I continued with the investigation to verify whether it was legitimate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4LjbRurVWWnXMAWlnIWcpQ.png" /></figure><h3>Step 3 — Log Management Analysis</h3><p>As a final check, I moved to the <strong>Log Management</strong> tab and searched using the SMTP IP address 172.16.20.3. I also correlated the search results with the email date (<strong>February 7, 2021</strong>) to find the related log entries.</p><p>This helped me verify the email activity in the logs and correlate it with the details collected during the initial investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NVLoHQ76JkNTMn6wKpbXNA.png" /></figure><h3>Step 4 — Checking Source IP Communications</h3><p>To make the investigation more thorough, I also searched the source IP address 172.16.17.82 in the <strong>Log Management</strong> tab to check whether it had initiated any suspicious communications.</p><p>After reviewing the available logs, I found no suspicious communication or unusual activity associated with this IP address. This provided additional evidence supporting the initial assessment of the email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fzzy-nYarX3cdaL9J-yVFQ.png" /></figure><h3>Final Verdict — False Positive</h3><p>After completing the investigation, I concluded that the alert was a <strong>False Positive</strong>. The email contained only plain text, had no attachments, and showed no suspicious content. I also reviewed the related log entries and checked communications from the source IP 172.16.17.82, but found no suspicious activity.</p><p>Based on the available evidence, there were no indicators of malicious activity.</p><h3>Case Closure</h3><ul><li><strong>Create a Case:</strong> Completed.</li><li><strong>Start the Playbook:</strong> Completed.</li><li><strong>Investigation Observations:</strong> Documented all findings, including email details and log analysis.</li><li><strong>Final Verdict:</strong> False Positive.</li><li><strong>Case Status:</strong> Closed.</li></ul><p><strong>Investigation completed. Alert closed as False Positive!</strong></p><h3>Conclusion</h3><p>After completing the investigation, I concluded that the alert was a <strong>False Positive</strong>. The email contained only plain text, with no suspicious content or attachments. I also reviewed the related log entries and checked communications from the source IP 172.16.17.82, but found no signs of suspicious activity.</p><p>Based on the available evidence, there was no indication of malicious communication or compromise. I documented my observations in the case, completed the playbook, and closed the alert as a <strong>False Positive</strong>.</p><p><strong>Alert Closed — False Positive!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07e737853478" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC114 — Malicious Attachment Detected — Phishing Alert — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc114-malicious-attachment-detected-phishing-alert-letsdefend-92053c6c24a0?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/92053c6c24a0</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[letsdefend-writeup]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[phishing-attacks]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 17:13:00 GMT</pubDate>
            <atom:updated>2026-11-17T17:13:00.276Z</atom:updated>
            <content:encoded><![CDATA[<h3>Executive Summary</h3><p>A high-severity phishing alert was triggered on January 31, 2021, at 03:48 PM. After investigating the alert, I confirmed it as a <strong>True Positive</strong>.</p><p>The investigation revealed that a malicious PowerPoint attachment was delivered to an internal user and executed, resulting in a Command and Control (C2) connection. Immediate action was required to contain the victim’s machine, delete the malicious email, and escalate the incident to the Tier 2 team for further investigation.</p><h3>Alert Details</h3><ul><li><strong>Event ID:</strong> 45</li><li><strong>Rule:</strong> SOC114 — Malicious Attachment Detected — Phishing Alert</li><li><strong>SMTP Address:</strong> 49.234.43.39</li><li><strong>Source Address:</strong> accounting@cmail.carleton.ca</li><li><strong>Destination Address:</strong> richard@letsdefend.io</li><li><strong>Email Subject:</strong> Invoice</li><li><strong>Device Action:</strong> Allowed</li></ul><h3>Step 1 — Taking Ownership &amp; Initial Triage</h3><p>After receiving the alert, I took ownership of the incident and started by reviewing the key details. I noticed that the email came from an external sender using an address that appeared to represent Carleton University’s accounting department. The email was sent to an internal user with the subject <strong>“Invoice”</strong>, which can be a common social engineering tactic used to make recipients open malicious attachments.</p><p>I also noticed that the email delivery status was marked as <strong>Allowed</strong>, meaning the email was delivered without being blocked by the security system. This made further investigation necessary to determine whether the attachment was malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*63XB6O5noO6I-OjJcW9Wvg.png" /></figure><h3>Step 2 — Email Security Analysis</h3><p>I moved to the <strong>Email Security</strong> tab and searched for the recipient address richard@letsdefend.io. I was able to locate the email associated with this alert. Since the email date matched the alert date, I confirmed that it was the relevant email and proceeded with the investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eJy8cwih9qiJf8CS4AdC9Q.png" /></figure><h3>Step 3 — Examining the Email</h3><p>After opening the email, I reviewed its content and noticed a generic message:</p><p><em>“Dear customer, Your invoice for the shopping you have done is attached.”</em></p><p>The message had no personalization or recognizable company branding. This was a suspicious sign and suggested a possible social engineering attempt to encourage the recipient to open the attachment.</p><p>I also identified the following attachment details:</p><ul><li><strong>Filename Hash (MD5):</strong> c9ad9506bcccfaa987ff9fc11b91698d</li><li><strong>Password:</strong> infected</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*im5fgWGQdd0Rmgt06s38XA.png" /></figure><h3>Step 4 — VirusTotal Analysis</h3><p>To check the reputation of the attachment, I submitted its MD5 hash to <strong>VirusTotal</strong>. The results showed that the file was flagged as malicious by <strong>35 out of 61 security vendors</strong>.</p><p>I also reviewed the file details and found the following:</p><ul><li><strong>Detection:</strong> 38/61 security vendors</li><li><strong>Threat Label:</strong> Trojan</li><li><strong>File Type:</strong> MS PowerPoint Presentation (PPT)</li></ul><p><strong>Notable Tags:</strong></p><ul><li>exploit</li><li>cve-2017-11882</li><li>executes-dropped-file</li></ul><p>These results strongly indicated that the PowerPoint attachment was malicious. The tags also suggested a possible connection to the CVE-2017–11882 exploit and the execution of a dropped file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GRk0XBg1RyOWGkq0AJ74eg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X_c-j7uEh1FEsXQUXiq-oQ.png" /></figure><h3>Step 5 — Log Management Analysis</h3><p>After completing the VirusTotal analysis, I moved to the <strong>Log Management</strong> tab and searched for the SMTP source IP address 49.234.43.39.</p><p>The search returned one event, which showed that the email reached the Exchange Server at 172.16.20.3. This confirmed that the email was successfully delivered to the organization&#39;s internal email infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*84tOxmgT_2WWqXIH7p_MPA.png" /></figure><h3>Step 6 — Endpoint Analysis</h3><p>Next, I moved to the <strong>Endpoint Security</strong> tab and searched for the destination IP address 172.16.20.3. The results identified the machine as the <strong>Exchange Server</strong>, running Windows Server 2012.</p><p>Since the investigation confirmed that a C2 connection had been established, this indicated that the incident required immediate attention. The affected machine needed to be contained to prevent further malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LsEWkVG1Z7Ay1ZdsEd5WSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*42FVZTsKKUXkUx4eZPv8Bg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6VpMUIhE8LMWAjo0oWu_ZA.png" /></figure><h3>Findings &amp; IOCs</h3><p>During the investigation, I identified the following indicators of compromise (IOCs):</p><ul><li><strong>Sender IP:</strong> 49[.]234[.]43[.]39 — Malicious</li><li><strong>Sender Email:</strong> accounting@cmail.carleton.ca</li><li><strong>Attachment MD5:</strong> c9ad9506bcccfaa987ff9fc11b91698d</li><li><strong>Associated Vulnerability:</strong> CVE-2017-11882</li><li><strong>Victim Machine:</strong> 172.16.20.3 (Exchange Server)</li></ul><h3>Final Verdict</h3><p><strong>Final Verdict: True Positive.</strong></p><p>The investigation confirmed that the phishing email containing a malicious PowerPoint attachment was successfully delivered and opened by the recipient. The attachment was associated with the CVE-2017-11882 vulnerability, and a Command and Control (C2) connection was established from the victim machine.</p><p>Based on these findings, the incident was treated as a genuine security threat. Immediate containment was performed, and the alert was escalated to the Tier 2 team along with the investigation findings.</p><h3>Recommendations</h3><ol><li><strong>Patch Management:</strong> Ensure that Microsoft Office installations are updated to address CVE-2017-11882. Systems running vulnerable versions should be patched immediately.</li><li><strong>Email Gateway Hardening:</strong> Apply additional security checks to password-protected attachments received from external senders. Suspicious attachments should be quarantined for further analysis.</li><li><strong>User Awareness:</strong> Conduct regular security awareness training and phishing simulations. Educate users about suspicious emails, especially generic messages with subjects like “Invoice” that include unexpected attachments.</li><li><strong>EDR Monitoring:</strong> Monitor unusual activity involving PowerPoint processes, especially when they spawn unexpected child processes. Configure alerts to detect potentially malicious behavior.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92053c6c24a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Event 119: “SOC169 — Possible IDOR Attack Detected” — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/event-119-soc169-possible-idor-attack-detected-letsdefend-8ed7f8ccf848?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ed7f8ccf848</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[lets-defend]]></category>
            <category><![CDATA[idor-vulnerability]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 17:14:12 GMT</pubDate>
            <atom:updated>2026-11-14T17:14:12.356Z</atom:updated>
            <content:encoded><![CDATA[<h3>“SOC169 — Possible IDOR Attack Detected”</h3><p>On February 28, 2022 at 10:48 PM, our monitoring system issued an alert for a possible IDOR attack. Let’s claim the ticket and investigate!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8yeq2XWfCFTX4pPVlVbJdw.png" /></figure><h3>Step 1: Understand Why the Alert Was Triggered</h3><p>According to the playbook, the first step of the investigation is to understand what happened and why the alert was generated. Before moving into a deeper analysis, we need to identify a few key details:</p><ul><li><strong>Detection Rule:</strong> Which detection rule triggered the alert?</li><li><strong>Trigger Reason:</strong> What activity caused the alert to fire?</li><li><strong>Devices Involved:</strong> Which source and destination devices were involved?</li><li><strong>Traffic Details:</strong> What type of communication occurred between these devices?</li></ul><p>To gather this initial information, I’ll start by reviewing the event summary generated by the monitoring system when the alert was triggered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8yeq2XWfCFTX4pPVlVbJdw.png" /></figure><h3>Initial Alert Findings</h3><p>After reviewing the event summary, I gathered the following information:</p><blockquote><strong><em>Detection Rule:</em></strong><em> SOC169 — Possible IDOR Attack Detected</em></blockquote><blockquote><strong><em>Alert Trigger Reason:</em></strong><em> Consecutive requests to the same page</em></blockquote><blockquote><strong><em>Source IP Address:</em></strong><em> </em><em>134.209.118.137</em></blockquote><blockquote><strong><em>Destination IP Address:</em></strong><em> </em><em>172.16.17.15</em></blockquote><p>The <strong>SOC169</strong> detection rule was triggered because the external IP address 134.209.118.137 sent multiple consecutive requests to the same web page on the internal server <strong>WebServer1005 (</strong><strong>172.16.17.15)</strong>.</p><p>The targeted URL was:</p><p><a href="https://172[.]16[.]17[.]15/get_user_info/">https://172.16.17.15/get_user_info/</a></p><p>This activity raised suspicion of a possible <strong>Insecure Direct Object Reference (IDOR)</strong> attack, where an attacker may attempt to access information belonging to other users by manipulating object references in web requests.</p><p>Now that I have a basic understanding of the alert and the devices involved, I can move on to the next step of the investigation and examine the available logs in more detail.</p><h3>Step 2: Collect Data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*sQtpitnRb2Vv84Endh3ETw.png" /></figure><p>Now that I have a basic understanding of the alert, the next step is to collect more information about the communication between the source IP address and the internal web server.</p><p>According to the playbook, I need to investigate the following details:</p><ul><li><strong>Traffic Direction:</strong> Determine whether the traffic originated from an external or internal network.</li><li><strong>IP Address Ownership:</strong> Identify the organization or network associated with the source and destination IP addresses.</li><li><strong>IP Reputation:</strong> Check whether the source IP address has been reported for suspicious or malicious activity.</li><li><strong>Device Ownership:</strong> Identify who is responsible for the destination device.</li><li><strong>Device Hostname:</strong> Find the hostname of the affected web server.</li><li><strong>Last User Logon Time:</strong> Check when the user last logged into the device.</li></ul><p>To gather this information, I’ll start by searching the available logs for all traffic originating from 134.209.118.137 on <strong>February 28, 2022</strong>. This should help me understand the communication pattern and collect the initial evidence needed for the investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iI41CYCmq_jTUN6kk0I85A.png" /></figure><p>This query returns five firewall logs, all of which cite WebServer1005 (172.16.17.15:443<em>)</em> as the destination.</p><p>By drilling down into the log for 10:48 PM (the time of alert), we can further confirm that the traffic flowed from the internet to the internal network:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/757/1*uuGQIomWjOVmDHYLHbrMOg.png" /></figure><p>To triple check that the traffic originated from an external device, we can consult our Endpoint Security system, which returns no matches for the source IP address on the internal network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*QlIIzqgA9i1Pc4G0xoBYFA.png" /></figure><p>However, the Endpoint Security system <em>does</em> contain a host of information about the destination device, WebServer1005:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hBqoQdBPXOS69nHpQw4K_w.png" /></figure><h3>Destination Device Information</h3><p>After checking the endpoint details, I found the following information about the destination device:</p><blockquote><strong><em>Hostname:</em></strong><em> WebServer1005</em></blockquote><blockquote><strong><em>Domain:</em></strong><em> letsdefend.local</em></blockquote><blockquote><strong><em>Primary User:</em></strong><em> webadmin35</em></blockquote><blockquote><strong><em>Last Login:</em></strong><em> February 15, 2022, at 01:43 PM</em></blockquote><p>This confirms that the destination IP address 172.16.17.15 belongs to an internal web server named <strong>WebServer1005</strong>, which is part of the letsdefend.local domain.</p><p>The server has a static IP address and is associated with the primary user <strong>webadmin35</strong>. The last recorded login for this user was on February 15, 2022, at 01:43 PM.</p><h3>Source IP Reputation Check</h3><p>Next, I wanted to learn more about the source IP address and check whether it had any history of suspicious activity.</p><p>For this, I used third-party threat intelligence platforms such as <a href="https://talosintelligence.com/reputation_center/">Cisco Talos</a> and <a href="https://otx.alienvault.com/browse/global/pulses?include_inactive=0&amp;sort=-modified&amp;page=1&amp;limit=10">AlienVault OTX</a>.</p><p>I started by searching for the source IP address in the <strong>Cisco Talos IP &amp; Domain Reputation Center</strong> to check its reputation and identify any reported malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hzkIMEQYJfzOPIYAYUQU0Q.png" /></figure><p>Although the hostname and domain are unavailable, we learn that the IP address has a “Poor” reputation with a Spam Level of “critical,” and that it is owned by “digital ocean inc.”.</p><p>Querying AlienVault for the source IP address provides even more context around the nature of the device:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IAN3vwNu8wt0xSkaiOPgow.png" /></figure><p>The AlienVault results showed <strong>22 related tags</strong> connecting this IP address to different types of malicious activities. It also indicated that the IP has historically appeared in <strong>Intrusion Detection System (IDS) telemetry</strong>, which adds further evidence to our investigation.</p><p>After reviewing the available threat intelligence information from Cisco Talos and AlienVault, the source IP address appears to have a suspicious history. This makes it unlikely that the traffic was part of normal network activity.</p><p>Based on these findings, I consider the traffic potentially malicious and will continue investigating to understand exactly what happened.</p><p>With the initial data collection complete, let’s move on to <strong>Step 3</strong>.</p><h3>Step 3: Examine HTTP Traffic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*52EwREVE8RmnP1YJXHIjbg.png" /></figure><p>So far, the information collected suggests that the source IP address may be involved in malicious activity. However, we still need to confirm whether an actual web attack took place.</p><p>To investigate this further, I’ll go back to the firewall logs collected earlier and take a closer look at the HTTP traffic between the source IP and the internal web server.</p><p>According to the playbook, there are three important things to focus on:</p><ul><li><strong>HTTP Response Size:</strong> Check the size of the responses returned by the web server.</li><li><strong>HTTP Response Status:</strong> Examine the HTTP status codes to understand how the server handled the requests.</li><li><strong>POST Parameters:</strong> Review the parameters submitted in the HTTP POST requests to identify any suspicious activity or attempts to manipulate application data.</li></ul><p>By examining these details, I can better understand the nature of the requests and determine whether they indicate a possible IDOR attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/762/1*LljSfw50G5GFtx9EdT1bUw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*3kL8kTPz-bjNx0vp0Q7ksQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/765/1*SpYzp4LGg-9qztV29x2ZIQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*UBByo97FIfyiYuHBR3UNnw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/1*jp6eBe0RBmDTpzIZvNshOg.png" /></figure><p>After reviewing the firewall logs, I found that the source IP address sent <strong>five consecutive HTTP requests over a period of three minutes</strong> to the same web page:</p><p><a href="https://172[.]16[.]17[.]15/get_user_info/">https://172.16.17.15/get_user_info/</a></p><p>Each request contained a different POST parameter. I also noticed that all five requests received an HTTP <strong>200 OK</strong> response, although the response sizes were different.</p><p>This indicates that the web server successfully processed the HTTP requests and returned responses. However, an HTTP 200 status code alone does not confirm that unauthorized data was accessed.</p><p>The repeated requests with different POST parameters raised my suspicion of a possible <strong>Insecure Direct Object Reference (IDOR)</strong> attack. I need to examine the actual POST parameters and determine whether the attacker was attempting to access information belonging to other users.</p><p>At this point, the activity looks suspicious, and further analysis is needed to confirm the IDOR attack.</p><h3>Step 4: Is the Traffic Malicious?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*zA6xy3y3pXexVIFteOAy0w.png" /></figure><p>At this point, we need to decide whether the activity observed so far is legitimate or malicious based on the evidence collected during the investigation.</p><p>While reviewing the firewall logs, I noticed that the source IP address sent five requests with different POST parameters to the same web page. The activity suggests that the attacker may have manipulated these parameters to access private information belonging to five different users without authorization.</p><p>This behaviour is consistent with a possible <strong>Insecure Direct Object Reference (IDOR)</strong> attack. Since the requests indicate potential unauthorized access to other users’ information, I classified the traffic as <strong>Malicious</strong>.</p><p><strong>Playbook Answer: Malicious.</strong></p><h3>Step 5: What Is the Attack Type?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*zc0WpMGZaqV6ofc-TmbL7A.png" /></figure><p>Now that we have classified the traffic as malicious, the next step is to identify the type of attack involved.</p><p>During the firewall log analysis, I found five consecutive HTTP requests coming from the same source IP address within three minutes. All requests targeted the same web page but contained different POST parameters.</p><p>I also noticed a pattern in the submitted parameters: user_id=n+1, where the user ID was incremented with each request. This suggests that the attacker was manipulating the user ID value to access information belonging to other users.</p><p>This behaviour is consistent with an <strong>Insecure Direct Object Reference (IDOR)</strong> vulnerability, where an application fails to properly verify whether a user is authorized to access a requested resource.</p><p>Based on these findings, the identified attack type is <strong>IDOR</strong>.</p><p><strong>Playbook Answer: IDOR.</strong></p><h3>Step 6: Check If It Was a Planned Test</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1005/1*Eu8X4PxY9f3_CkIBEf2Y_A.png" /></figure><p>Before moving forward with the incident response, we need to check whether this activity was part of an authorized penetration test or a planned security assessment. Sometimes, these activities can trigger security alerts even when they are performed by internal security teams.</p><p>To verify this, I searched the <strong>Email Security</strong> system for any internal communication related to the destination hostname WebServer1005 and its IP address 172.16.17.15.</p><p>However, the search returned no matching results for either of these indicators.</p><p>Since I couldn’t find any evidence of an approved security test or planned attack simulation, there is no reason to consider this activity authorized.</p><p><strong>Playbook Answer: Not Planned.</strong></p><h3>Step 7: What Is the Direction of Traffic?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*A-54SXhrwA9HlTN44t7FqQ.png" /></figure><p>The next step is to identify the direction from which the suspicious traffic originated.</p><p>Based on the firewall logs, I confirmed that the source IP address 134.209.118.137 is external, while the destination IP address 172.16.17.15 belongs to the internal web server <strong>WebServer1005</strong>.</p><p>This means the communication originated from an external network and was directed towards the company’s internal network.</p><p><strong>Playbook Answer: Internet → Company Network.</strong></p><h3>Step 8: Check Whether the Attack Was Successful</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*ugUHJWJ3wEFuyL5io03FEg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*KkAoqTYZms6SPTq3t0ljHg.png" /></figure><p>Before deciding on the next response action, we need to determine whether the attacker actually managed to access information they were not authorized to view.</p><p>To investigate this, I reviewed the HTTP response sizes for the five requests in the firewall logs. The response sizes varied between <strong>158 and 351 bytes</strong>.</p><p>These differences suggest that the server returned different amounts of data for the manipulated user IDs. This could indicate that the attacker successfully accessed information associated with multiple user accounts.</p><p>Based on the available evidence and the playbook’s assessment, I classified the attack as successful.</p><p><strong>Playbook Answer: Yes — Successful Attack.</strong></p><h3>Step 9: Containment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*S1l0XMXXVb0gw9Aw_f8bOg.png" /></figure><p>Since the investigation indicates that the IDOR vulnerability on <strong>WebServer1005</strong> was successfully exploited, the next step is to contain the affected server. This helps limit further unauthorized access while allowing the security team to investigate the incident and plan remediation.</p><p>To do this, I searched for <strong>WebServer1005</strong> in the Endpoint Security system. After locating the device, I opened the <strong>Endpoint Information</strong> section and enabled the <strong>Containment</strong> option to isolate the server from the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6C6jXuje6i9rwoL3_4zGZA.png" /></figure><p>With the affected host contained, we can now proceed to the next step of the playbook.</p><h3>Step 10: Add Artifacts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*xYapLA79D7_WR6zpz7Y5Hg.png" /></figure><p>Now that <strong>WebServer1005</strong> has been contained, the next step is to add the relevant artifacts collected during the investigation.</p><p>Adding artifacts is important because it helps preserve key evidence and provides useful information for other analysts who may review or continue working on the incident.</p><p>Since the source IP address 134.209.118.137 has been identified as suspicious based on the threat intelligence findings, I added it as an artifact along with a note recommending that it be blocked to prevent further communication from this address.</p><p>This ensures that the important indicators and recommended actions are documented as part of the case for further investigation and remediation.</p><h3><strong>Step 11: Do You Need Tier 2 Escalation?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/995/1*PR2nJcMWeUuaygPWM5TShw.png" /></figure><p>After adding the relevant artifacts, the next step is to decide whether this incident requires escalation to the Tier 2 team for further investigation and remediation.</p><p>Since the investigation confirmed that the IDOR attack was successful and the attacker potentially accessed information belonging to multiple users, this incident requires additional attention.</p><p>Tier 2 analysts can perform a deeper investigation, assess the full impact, and work on fixing the vulnerability to prevent similar attacks in the future.</p><p><strong>Playbook Answer: Yes — Escalate to Tier 2.</strong></p><p>With the escalation decision made, let’s move on to the final step of the investigation.</p><h3>Step 12: Analyst Note</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*9RpO2enzD_VGrZ9TweBP7w.png" /></figure><p>We have now reached the final step of the playbook: documenting the investigation in the Analyst Note.</p><p>This is an important step because it provides a clear summary of what happened, the evidence collected, and the actions taken during the investigation. It also helps Tier 2 analysts understand the incident and continue with further investigation and remediation without having to repeat the initial analysis.</p><p>According to the playbook, the Analyst Note should cover the following points:</p><ul><li><strong>Alert Summary:</strong> Briefly explain which alert was triggered and why.</li><li><strong>Investigation and Evidence:</strong> Summarize the analysis performed and include the supporting evidence.</li><li><strong>Actions Taken:</strong> Document the containment measures and other response actions completed during the investigation.</li><li><strong>Recommended Next Steps:</strong> Mention any additional investigation or remediation required.</li></ul><p>Once the note is completed, the case will be ready for escalation to Tier 2.</p><h3>Alert Closure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1017/1*5lLyRgorhba6pefYyktMQg.png" /></figure><p><strong>Final Verdict: True Positive</strong></p><p>The alert was a genuine IDOR attack against WebServer1005. The attacker successfully manipulated POST parameters to access information belonging to multiple users without authorization. The affected host was contained, the malicious source IP was documented for blocking, and the incident was escalated to Tier 2 for further investigation and remediation.</p><p><strong>Alert Closed!</strong></p><h3>Conclusion</h3><p>This investigation was a great learning experience and helped me understand how an IDOR vulnerability can be exploited to access sensitive information belonging to other users.</p><p>During the investigation, I analysed firewall logs, reviewed HTTP requests and responses, checked IP reputation using threat intelligence platforms, and examined the communication between the external source and the internal web server. By correlating these findings, I identified suspicious patterns in the POST parameters that indicated an attempt to manipulate user IDs and access unauthorized information.</p><p>The investigation confirmed that the activity was malicious and that the IDOR attack was successful. I also learned the importance of proper incident response, including containing the affected server, documenting relevant artifacts, and escalating the case to Tier 2 for further investigation and remediation.</p><p>Overall, this challenge improved my understanding of web application attacks and strengthened my practical SOC investigation skills, especially in log analysis, evidence correlation, and incident handling.</p><p>Thanks for reading my investigation! I hope you found this write-up helpful. See you in the next one! 🔐</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ed7f8ccf848" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC168 — Whoami Command Detected in Request Body — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc168-whoami-command-detected-in-request-body-letsdefend-296a3aac0fd6?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/296a3aac0fd6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[command-injection]]></category>
            <category><![CDATA[letsdefend-writeup]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 17:49:37 GMT</pubDate>
            <atom:updated>2026-11-12T17:49:37.888Z</atom:updated>
            <content:encoded><![CDATA[<p>Thank you for being part of my journey toward becoming a Cybersecurity Analyst! To gain practical experience and improve my investigation skills, I’ve been working through the Security Analyst path on LetsDefend.io, where I get hands-on experience handling real-world security alerts in a Virtual SOC environment. Along the way, I’ve been learning to work with SIEM tools, analyse endpoint logs, investigate network and email traffic, use threat intelligence platforms, and follow SOC playbooks to understand different security incidents. With that background, let’s move on to today’s investigation, where I’ll walk through the alert, analyse the available evidence, and explain the steps I followed to reach my final verdict.</p><h3>! INVESTIGATION TIME !</h3><h3>SOC168- Whoami Command Detected in Request Body</h3><p><strong><em>Selecting a Soc alert</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z1nJZUtm4SbCloFtv1Qj6w.png" /></figure><p>I jumped into the SIEM today really in the mood for a challenge. I had a plethora of Web-attacks to pick from, but “Soc Alert 168 — Whoami Command Detected in Request Body” was listed as high severity and sounded interesting. Here goes nothing!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1010/1*WJywWVQb1Ukrf9HrZkMmqQ.png" /></figure><h3>1. Data Collection — Source and Destination IP Analysis</h3><p>The first step in the playbook was to collect the available information related to the alert. Fortunately, the SIEM provided most of the required details in the investigation channel, where I had already taken ownership of the alert.</p><p><strong>Source IP:</strong> 61.177.172.87<br><strong>Destination IP:</strong> 172.16.17.16</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpFpzvGnAX_8TsqNlaKPeg.png" /></figure><p>I started by checking the reputation of the source IP using <strong>VirusTotal</strong>. The results immediately caught my attention, as the IP address was flagged by 1 <strong>security vendors</strong>, including Fortinet. The lookup also showed that the IP belongs to Chinanet, a major internet service provider in China.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*St1s9LNPprVcYP3aY7WqWQ.png" /></figure><p>To get another perspective, I checked the same IP using <strong>Cisco Talos Intelligence</strong>. It showed a poor reputation and classified the IP as untrusted. I also found that it appeared on two Spamhaus blocklists:</p><ul><li>PBL.SPAMHAUS.ORG</li><li>SBL.SPAMHAUS.ORG</li></ul><p>Finally, I searched for the source IP in our endpoint security platform, but no matching results were found.</p><p>Based on these initial checks, the source IP appeared suspicious and required further investigation. Its poor reputation gave me a reason to look more closely at the request and determine whether it was part of an actual attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDrOZIzWy76oX179c0pQ3A.png" /></figure><h3>Who Does the Destination IP Belong To?</h3><p>Next, I wanted to identify the system behind the destination IP address, so I searched for 172.16.17.16 in the endpoint security platform.</p><p>The results showed that this IP belongs to an internal host named <strong>WebServer1004</strong>, which is associated with the user <strong>Webadmin3</strong>.</p><p>I also checked the system’s last login activity and found that it was last logged into on <strong>February 8, 2022, at 11:11 AM</strong>. This was approximately 20 days before the alert was generated on <strong>February 28, 2022</strong>.</p><p>To verify whether the destination IP had any known security issues, I also checked it using <strong>VirusTotal</strong> and <strong>Cisco Talos Intelligence</strong>. Neither platform returned any suspicious results.</p><p>Based on these findings, I identified the destination as a known internal web server, with no obvious reputation-related concerns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZDrOZIzWy76oX179c0pQ3A.png" /></figure><h3>2. HTTP Traffic Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*9DEL5yQG1XMn1PU9a17d1g.png" /></figure><p>The next step in the playbook was to analyse the HTTP traffic and look for suspicious payloads, such as SQL Injection, Cross-Site Scripting (XSS), and Command Injection.</p><p>The investigation section of the SIEM didn’t provide the complete HTTP request and response details, so I switched to the <strong>Log Management platform</strong> to get a better view of the network activity.</p><p>I searched for the source IP 61.177.172.87 and found that it had communicated only with the internal IP address 172.16.17.16. There were no connections to any other internal machines, which was a positive finding.</p><p>After that, I located the complete HTTP request and response information, including the POST parameters. While reviewing the request body, I noticed that the source IP had submitted a total of <strong>five different Linux commands</strong>. One of them was whoami, which was responsible for triggering the SOC168 alert.</p><h3>Understanding the Commands Used in the Attack</h3><p>Before analysing each command, it’s important to understand how parameters are passed through HTTP requests. Query parameters are commonly used in URLs to pass additional information to a web server, while POST parameters can carry data inside the request body. In this investigation, the attacker used the c parameter to submit commands to the web application.</p><p>Here are the five commands I identified:</p><p><strong>1. </strong><strong>?c=whoami</strong></p><p>This was the command that triggered our alert. The whoami command displays the username of the account currently executing the command. An attacker could use this information to identify the privileges associated with the compromised account and understand what actions might be possible.</p><p><strong>2. </strong><strong>?c=ls</strong></p><p>The ls command lists files and directories in the current working directory. Attackers may use it to explore the server&#39;s file system and identify potentially sensitive files or directories for further exploitation.</p><p><strong>3. </strong><strong>?c=uname</strong></p><p>The uname command displays basic system information, such as the operating system name and kernel details. This information can help an attacker understand the target environment.</p><p><strong>4. </strong><strong>?c=cat /etc/passwd</strong></p><p>This command displays the contents of the /etc/passwd file, which contains information about user accounts configured on a Linux system. Attackers may use this information to identify existing usernames and potential targets for further attacks.</p><p><strong>5. </strong><strong>?c=cat /etc/shadow</strong></p><p>The /etc/shadow file stores password hashes and other password-related information for Linux user accounts. Access to this file could be particularly dangerous because attackers may attempt to crack the hashes to recover user passwords.</p><h3>Initial Findings</h3><p>Looking at these commands together, I noticed a clear pattern. The attacker was not simply sending random requests; they were attempting to gather information about the target system, its users, and the privileges available.</p><p>The combination of whoami, ls, uname, and attempts to access /etc/passwd and /etc/shadow strongly suggests <strong>command injection activity followed by system enumeration</strong>.</p><p>This made the alert more concerning, so I continued investigating to determine whether the commands were successfully executed and whether the internal web server was actually compromised.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*31wCKE9HuUOJZbDDTcES_A.png" /></figure><h3>Is the Activity Malicious?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*4ys9JiXsyUTCvCOIKP81MA.png" /></figure><p>Based on the HTTP traffic analysis in the Log Management platform, I found several suspicious commands submitted through the POST parameters.</p><p>The attacker attempted to execute commands such as whoami, ls, and uname, along with commands to access sensitive Linux files like /etc/passwd and /etc/shadow.</p><p>These commands indicate an attempt to gather information about the server, identify user accounts, and access sensitive system information.</p><p>Considering these findings, I classified the activity as <strong>Malicious</strong>.</p><p><strong>Answer: Malicious</strong></p><h3>What Is the Attack Type?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*YzNnvJJSFQHsPcfEwzHI1w.png" /></figure><p>The activity is consistent with a <strong>Command Injection attack</strong>. The attacker attempted to execute Linux operating system commands through the web application’s HTTP request body.</p><p>This suggests that the attacker was trying to exploit a vulnerability in the web application to execute commands on the underlying server.</p><h3>Was This a Planned Test?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/993/1*PzSJrDybngtWXygRE-fvhw.png" /></figure><p>Before treating the activity as an actual attack, I needed to check whether it could have been part of an authorized security assessment or an internal attack simulation.</p><p>Planned penetration tests and security simulations can sometimes trigger SIEM alerts, so checking for prior communication is an important part of the investigation.</p><p>I searched the email logs using the following details:</p><ul><li><strong>Username:</strong> Webadmin3</li><li><strong>Source IP:</strong> 61.177.172.87</li><li><strong>Destination IP:</strong> 172.16.17.16</li><li><strong>Hostname:</strong> WebServer1004</li><li><strong>Attack Simulation Tools:</strong> Verodin, AttackIQ, and Picus</li></ul><p>However, I couldn’t find any emails or notifications related to these systems, IP addresses, or an authorized security testing activity.</p><p>Based on the available information, there was no indication that this activity was part of a planned security test.</p><p><strong>Playbook Answer: Not Planned</strong></p><h3>What Is the Direction of the Traffic?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/1*9e7yGU59LK3cITt9WpDyTg.png" /></figure><p>Next, I checked the direction of the network traffic to understand where the attack originated and which system was targeted.</p><p>The traffic originated from the external source IP address 61.177.172.87, located in China, and was directed toward our internal web server at 172.16.17.16 (WebServer1004).</p><p>Since the request came from an external IP address and targeted a system inside the company network, the traffic direction is:</p><p><strong>Answer: Internet → Company Network</strong></p><h3>Was the Attack Successful?</h3><p>Based on the evidence I found during the investigation, I believe the attack was successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*MX6VlZPabRskoR6URV8L6A.png" /></figure><p>First, I reviewed the HTTP logs in the Log Management platform. The request containing the whoami command returned an <strong>HTTP 200 OK</strong> response with a response size of <strong>912 bytes</strong>. This caught my attention because the response seemed unusually large for a command that normally returns only a username.</p><p>I also noticed that the requests sent before and after the whoami command returned HTTP 200 responses as well. This suggested that the attacker was able to submit multiple commands and potentially explore the server&#39;s directory structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GtBVvvKW6-S5jsZ7ZtvNFw.png" /></figure><p>However, the most important finding came from the <strong>Endpoint Security logs</strong>. When I checked the process information, I noticed that the User field showed <strong>Root</strong>.</p><p>This was a significant finding because root is the highest-privileged account on a Linux system. It suggests that the commands were being executed with root-level privileges, potentially giving the attacker extensive control over the server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zJdFrC1kCGK9usGVh_bNmQ.png" /></figure><p>Considering the HTTP responses and the endpoint process information together, I classified the attack as <strong>Successful</strong>.</p><h3>Was the Attack Successful?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*Sk3V65gX6uhNoff5BmSJIA.png" /></figure><p><strong>Answer: Yes — Successful Attack</strong></p><p>Based on the HTTP response logs and Endpoint Security findings, I confirmed that the attacker was able to execute commands on the internal web server with <strong>root-level privileges</strong>. This indicates that the attack was successful.</p><h3>Containment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/1*vxneuTbTHbEXjJwN81_7tA.png" /></figure><p>Since the investigation confirmed that the attack was successful and commands were executed with root-level privileges, immediate containment was necessary.</p><p>I decided that <strong>WebServer1004</strong> needed to be isolated from the network to prevent further unauthorized access and limit the potential impact on the internal environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gozBpNehpjn8791ahpJe0A.png" /></figure><p>Isolating the affected server would help restrict the attacker’s access and reduce the risk of the compromise spreading to other systems.</p><p><strong>Playbook Answer: Yes — Isolate the Device.</strong></p><h3>Artifacts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*3C655qgKDX3SdWrQcC9O9g.png" /></figure><p>Adding artifacts is an important part of a SOC investigation because it helps preserve the evidence collected during the analysis. Information such as IP addresses, URLs, and suspicious commands can be useful for threat intelligence, identifying related activity, and supporting future investigations.</p><p>After reviewing the available evidence, I added the following artifacts to the case:</p><p><strong>URL Address:</strong><br>https://172.16.17.16/video/</p><p><strong>Source IP Address:</strong><br>61.177.172.87 – Identified as a suspicious IP associated with Chinanet.</p><p><strong>Destination IP Address:</strong><br>172.16.17.16 – Internal web server (WebServer1004).</p><p><strong>Suspicious Commands Identified:</strong></p><ul><li>?c=whoami – Command that triggered the alert.</li><li>?c=ls – Attempt to list files and directories.</li><li>?c=uname – Attempt to gather system information.</li><li>?c=cat /etc/passwd – Attempt to access Linux user account information.</li><li>?c=cat /etc/shadow – Attempt to access password hash information.</li></ul><p>Adding these artifacts helped me keep all the important indicators and evidence in one place, making the investigation easier to review and supporting the containment process.</p><h3>Tier 2 Escalation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*5B-SKvVEv7V8HGDWUuyxLw.png" /></figure><p>Since the investigation confirmed that the attacker successfully executed commands on the internal web server with root-level privileges, this incident requires further investigation by the Tier 2 team.</p><p>The attack was successful, and the compromised server may be at risk. Escalating the alert will allow Tier 2 analysts to perform a deeper investigation, assess the full impact, and take any additional actions needed to secure the environment.</p><p><strong>Playbook Answer: Yes — Escalate to Tier 2.</strong></p><h3>Analyst Note</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*c1clj3wPmWQHwSkbScZYLA.png" /></figure><p>On February 28, 2022, at 4:11 AM, the suspicious Chinanet IP <strong>61.177.172.87</strong> first contacted the internal web server <strong>WebServer1004 (172.16.17.16)</strong>. During the investigation, I found that the attacker initially submitted the ls command through the HTTP POST request body.</p><p>At 4:12 AM, a SIEM alert was triggered after the whoami command was detected in another request body. The attacker continued sending commands between 4:13 AM and 4:15 AM, including uname, cat /etc/passwd, and cat /etc/shadow. These commands indicate attempts to gather system information and access sensitive account data.</p><p>Based on the available evidence, I confirmed that the command injection attack was successful and that commands were executed under the root account. As a result, <strong>WebServer1004 was isolated from the network, and the incident was escalated to the Tier 2 team for further investigation and remediation.</strong></p><h3>Alert Closure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6PrgBFEa_DhISnDtHQooQw.png" /></figure><p><strong>Final Verdict: True Positive</strong></p><p>The alert was a genuine command injection attack against WebServer1004. The attacker successfully executed commands with root-level privileges. The affected host was contained, and the incident was escalated to Tier 2 for further investigation and remediation.</p><p><strong>Alert Closed!</strong></p><h3>Wrap Up</h3><p>This investigation was a great opportunity to learn more about command injection attacks against web applications and understand how quickly an attacker can compromise a server when a vulnerability is successfully exploited.</p><p>I enjoyed working through this alert in a SOC environment and applying my skills in log analysis, endpoint investigation, and email analysis to understand what happened. I also got some hands-on experience with threat intelligence tools like VirusTotal and Cisco Talos to check the reputation of suspicious IP addresses.</p><p>Overall, this investigation helped me improve my understanding of the SOC investigation process, from identifying suspicious activity and analyzing evidence to confirming the attack, containing the affected host, and escalating the incident to Tier 2.</p><p>If you’ve made it this far, thank you for reading! I hope you found this investigation useful, and I’ll see you in the next write-up.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=296a3aac0fd6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC167 — LS Command Detected in Requested URL — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc167-ls-command-detected-in-requested-url-letsdefend-81b8e25ef418?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/81b8e25ef418</guid>
            <category><![CDATA[letsdefend-writeup]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 09:01:56 GMT</pubDate>
            <atom:updated>2026-11-09T09:01:56.386Z</atom:updated>
            <content:encoded><![CDATA[<h3>Alert Overview and Initial Identification of the ls Command in Web Traffic</h3><p>In this section, I’ll explain how the alert was triggered and what caught my attention during the initial investigation.</p><p>The alert was generated after a detection rule identified the ls command in web traffic. This immediately caught my attention because ls is a Linux command commonly used to list files and directories. When this command appears in a web request, it can indicate an attempt to execute system commands on a web server.</p><p>I decided to investigate the request further to understand why the command appeared in the traffic and whether it was related to a possible command injection or remote code execution attempt.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9l3N1UYY82Dd4axRZGY__A.png" /></figure><p><strong>Alert Name:</strong> SOC167 — LS Command Detected in Requested URL<br><strong>Severity: </strong>Medium<br><strong>Event ID:</strong> 117<br><strong>Event Time: </strong>Feb 27, 2022, 12:36 AM<br><strong>Category</strong>: Web Attack</p><h3>Playbook</h3><h3>1. Alert Overview</h3><p>A web attack alert was triggered on the endpoint <strong>EliotPRD</strong> after the detection rule identified the ls keyword in the requested URL.</p><p>The ls command is commonly used in Linux to list files and directories. However, when it appears in web traffic, it can sometimes indicate a <strong>command injection attempt</strong>, where an attacker tries to execute operating system commands through a vulnerable web application.</p><p>The security device allowed the request, so I decided to investigate it further. During my initial review, I noticed that the ls keyword appeared to be part of a normal search query rather than an attempt to execute a system command.</p><p>I continued analysing the request and related logs to confirm whether this was genuine malicious activity or a false positive.</p><h3>2. Key Event Details</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4GYeCRuhEd-9outHjWW7YA.png" /></figure><h3>3. Why This Alert Was Triggered</h3><p>The <strong>SOC167 detection rule</strong> is designed to detect operating system command keywords inside requested URLs. These keywords can sometimes indicate a possible <strong>command injection attack</strong>.</p><p>During my investigation, I found that the alert was triggered because the word <strong>skills</strong> contains the substring <strong>ls</strong>. The detection rule matched this substring and generated the alert.</p><p>However, after checking the context, I noticed that ls was not used as a standalone Linux command or in a way that suggested command execution. It was simply part of a normal search term.</p><p>This indicates that the alert was likely triggered by a <strong>false positive caused by substring matching</strong> rather than an actual command injection attempt.</p><h3>4. IP Reputation Check</h3><p>Next, I checked the destination IP address to understand whether the request was communicating with a suspicious or legitimate external service.</p><p><strong>Destination IP:</strong> 188.114.96.15</p><p>During the investigation, I found that this IP address is associated with a legitimate public website.</p><p>This finding did not indicate any obvious malicious activity from the destination. I kept it in mind while correlating the remaining evidence to determine whether the alert was genuine or a false positive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/595/1*gU-0SfNn9fECb6KFKbwMDQ.png" /></figure><ul><li>No indicators of malicious infrastructure</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-pIl_v_apDFXiVKQV84Kw.png" /></figure><blockquote>No threat intelligence sources flagged either IP as malicious.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*klE72wNeiq1zde6xXtiOQw.png" /></figure><h3>5. Initial Investigation and Traffic Analysis</h3><p>Next, I reviewed the network traffic to understand how the request was generated and whether it contained any suspicious activity.</p><p>During the analysis, I found the following:</p><ul><li>The traffic originated from an <strong>internal host</strong>, rather than an external internet source.</li><li>The request was a normal <strong>HTTP GET</strong> request sent to a blog search endpoint.</li><li>The URL parameter ?s=skills was used for a regular search operation.</li><li>I didn’t find any suspicious characters, encoding techniques, or command chaining patterns in the request.</li></ul><p>Based on these findings, the request appeared to be normal web activity. The ls keyword was simply part of the word skills, and there were no clear signs of an attempt to execute an operating system command.</p><p>This further supported the possibility that the alert was a <strong>false positive</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IklDVl_Xn1edbwOpyHMc_Q.png" /></figure><ul><li>The User-Agent string matches a legitimate Firefox browser on Linux.</li><li>These indicators strongly suggest normal user browsing behavior.</li></ul><h3>6. User and Activity Review</h3><p>After reviewing the network traffic, I moved on to checking the source system and related user activity.</p><p>During this step, I found the following:</p><ul><li>The hostname <strong>EliotPRD</strong> belongs to a known internal system.</li><li>I didn’t find any signs of unauthorized user activity or unusual behaviour.</li><li>There was no evidence of scheduled vulnerability scans, penetration testing, or automated attack activity.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3XR70orTbSZ-kTIOFJpc_g.png" /></figure><p>Based on these findings, the request appeared to be generated through normal activity on a legitimate internal system rather than by an attacker.</p><p>This provided further evidence that the alert was triggered by a normal search request and was most likely a <strong>false positive</strong>.</p><h3>7. Additional Traffic Review</h3><p>I also reviewed the surrounding network traffic to check whether the same source IP had generated any other suspicious requests.</p><p>During this review, I found:</p><ul><li>No additional web attack patterns.</li><li>No repeated command-related keywords.</li><li>No unusual request frequency or suspicious traffic behaviour.</li></ul><p>I couldn’t find any further evidence suggesting malicious activity. This supported my earlier findings that the alert was triggered by a legitimate search request.</p><h3>8. Impact Assessment</h3><p>After completing the investigation, I assessed whether the activity had caused any security impact.</p><p>AreaFindingsCommand ExecutionNo evidence foundWeb Application CompromiseNone identifiedData ExposureNoneBusiness ImpactNone</p><p>Based on the available logs and investigation results, there was no indication that the system was compromised or that any data was exposed.</p><h3>9. Recommended Actions</h3><p>Based on my investigation, I recommend the following actions:</p><ol><li><strong>Close the Alert:</strong> Classify the alert as a False Positive because the ls keyword was part of a legitimate search query.</li><li><strong>Tune Detection Rules:</strong> Improve the detection logic to avoid triggering alerts based only on command-related keywords appearing as substrings in normal URL parameters.</li><li><strong>Continue Monitoring:</strong> Monitor future web requests for actual command injection patterns and suspicious command execution attempts.</li></ol><h3>Final Verdict</h3><p><strong>False Positive — Non-Malicious Traffic</strong></p><p>After reviewing the request, source system, IP reputation, and surrounding network activity, I concluded that this alert was a false positive.</p><p>The detection rule triggered because the word skills contained the substring ls. However, there was no evidence of command injection, command execution, or any other malicious activity.</p><p>This investigation highlighted the importance of analysing the complete request context rather than relying only on keyword-based detection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2gOehUdDNXgzqwsiCUA_rg.png" /></figure><h3>Analyst Note</h3><p>The alert was triggered because the substring ls was detected in the search parameter of the requested URL (?s=skills).</p><p>Although ls is a commonly used Linux command, I found that it was simply part of the word skills and was not being used to execute any system command.</p><p>The request originated from an internal host and was sent to a legitimate external website through a standard HTTP GET request. During the investigation, I found no suspicious payloads, unusual traffic patterns, or additional malicious activity.</p><p>Based on the available evidence, I classified this alert as a <strong>False Positive</strong>. No system compromise or security impact was identified, so no further remediation actions were required.</p><p><strong>Note</strong><br>The alert was triggered due to keyword-based detection matching the string `ls` inside a legitimate search query (`skills`). The request originated from an internal system and was sent to a trusted external website using normal browsing behavior. No command injection patterns, malicious payloads, or suspicious follow-up activity were observed. This activity is confirmed as non-malicious and classified as a false positive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81b8e25ef418" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC166 — JavaScript Code Detected in Requested URL — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc166-javascript-code-detected-in-requested-url-letsdefend-e1e931ce576b?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1e931ce576b</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[letsdefend-writeup]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 11:12:46 GMT</pubDate>
            <atom:updated>2026-11-07T11:12:46.215Z</atom:updated>
            <content:encoded><![CDATA[<p>While working on the <strong>Let’sDefend SOC platform</strong>, I came across an alert named <strong>SOC166 — JavaScript Code Detected in Requested URL</strong>.</p><p>This type of alert is usually triggered when a requested URL contains suspicious JavaScript code that could be related to a <strong>Cross-Site Scripting (XSS)</strong> attack.</p><p>My goal was to investigate the alert, analyse the requested URL, and check whether the activity was actually malicious or just a false positive.</p><h3>Initial Review</h3><p>I started the investigation by opening the alert in the <strong>Let’sDefend SOC platform</strong> and checking the request details.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hcSriBX4_dwEAtdpFfBL4g.png" /></figure><p>The request contained the following URL:</p><pre>GET /search/?q=&lt;$script&gt;javascript:$alert(1)&lt;$/script&gt;</pre><p>After looking at the request, I noticed that the q parameter contains a suspicious JavaScript payload. This looks like a possible <strong>Reflected Cross-Site Scripting (XSS)</strong> attempt, where an attacker tries to inject JavaScript through a URL parameter and get it executed in a victim&#39;s browser.</p><p>I decided to investigate further to determine whether the payload was actually executed or simply detected in the request.</p><h3>Deeper Investigation</h3><h3>Step 1: Source IP Reputation</h3><p>The first thing I checked was the reputation of the source IP address involved in the request.</p><p><strong>Source IP:</strong> 112.85.42.13</p><p>I looked up this IP address on <strong>AbuseIPDB</strong> to check whether it had been reported for any suspicious activity. The results showed multiple reports associated with this IP, mainly related to <strong>brute-force attempts and scanning activity</strong>.</p><p>This made the source IP look suspicious and gave me another reason to investigate the alert further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*GgfHj5anFKmQaHxFQtuYSg.png" /></figure><h3>Step 2: HTTP Response Code</h3><p>Next, I checked the HTTP response returned for the request.</p><p>The server responded with <strong>HTTP 302 Found</strong>, and the response size was <strong>0 bytes</strong>.</p><p>This indicates that the request was redirected and the server did not return any response body.</p><p>Based on this information, there was no evidence of a page being rendered or the injected JavaScript being executed. This suggests that the XSS attempt may have been unsuccessful.</p><p>However, I kept this finding in mind and continued checking the available evidence before reaching a final conclusion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tCnUIJX0qDUGkRn3tI04UA.png" /></figure><h3>Step 3: Pattern of Activity</h3><p>After that, I reviewed the logs around the alert time to check whether the source IP had performed any additional suspicious actions.</p><p>During this review, I didn’t find any signs of follow-up activity, such as:</p><ul><li>No suspicious POST requests.</li><li>No signs of data exfiltration.</li><li>No evidence of authentication session hijacking.</li></ul><p>Based on the available logs, this appeared to be a one-time scanning or probing attempt rather than part of a larger attack.</p><h3>Is the Traffic Malicious?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/1*atEc4jPLgk5BBpnsMlo3sw.png" /></figure><p><strong>Verdict: Malicious Traffic</strong></p><p>After reviewing the evidence, I classified the traffic as malicious.</p><p>The request contained a clear XSS payload:</p><pre>&lt;script&gt;javascript:alert(1)&lt;/script&gt;</pre><p>The request also originated from an IP address with multiple abuse reports on AbuseIPDB. Although the server returned a <strong>302 Found</strong> response with a <strong>0-byte response body</strong>, this does not change the suspicious nature of the request.</p><p>There was no evidence that the payload successfully executed, but the request itself showed an attempt to test or exploit a potential XSS vulnerability.</p><h3>Attack Type</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*QS2OoJRkt3W08m0z0FxLmQ.png" /></figure><p><strong>Attack Vector:</strong> URL — Query Parameter<br><strong>Attack Type:</strong> Cross-Site Scripting (Reflected XSS)</p><p>After analysing the request, I identified the attack vector as a URL query parameter. The attacker tried to inject the following JavaScript payload into the <strong>q parameter</strong>:</p><pre>&lt;script&gt;javascript:alert(1)&lt;/script&gt;</pre><p>This is a common technique used in <strong>Reflected XSS attacks</strong>. In this type of attack, the attacker sends a specially crafted URL containing a malicious payload. If the web application reflects the input in its response without proper validation or sanitization, the JavaScript code may execute in the victim’s browser.</p><p>In this case, the request contained an XSS payload, but the available evidence did not confirm successful execution.</p><h3>Was the Attack Planned or Unplanned?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*IxDj44lVJzZlMVo79WB41A.png" /></figure><p><strong>Verdict: Unplanned Activity</strong></p><p>I also checked whether this activity could be part of an authorized security test or internal simulation.</p><p>To verify this, I reviewed the available information and found the following:</p><ul><li>I searched the internal email logs and security notifications, but couldn’t find any messages or alerts mentioning the source IP, hostname, or an authorized testing activity.</li><li>The source IP address (112.85.42.13) was not associated with any known attack simulation tools, such as Verodin, AttackIQ, or Picus.</li><li>The hostname also didn’t show any connection to internal testing or simulation infrastructure.</li></ul><p>Based on these findings, I found no evidence that this activity was part of a planned security test. I therefore classified it as <strong>unplanned malicious activity</strong>.</p><h3>Direction of Traffic</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/986/1*0P066A_2IhWfj9Z4W-cS2w.png" /></figure><p><strong>Traffic Direction: Internet → Company Network</strong></p><p>Next, I checked the direction of the network traffic to understand where the request originated and which asset it targeted.</p><p>The request came from an external IP address (112.85.42.13), geolocated to <strong>Shanghai, China</strong>, and was directed toward an internal company asset.</p><p>Based on this information, I identified the traffic direction as <strong>Internet to Company Network</strong>. This confirms that the suspicious request originated outside the organisation and targeted an internal-facing web application.</p><h3>Attack Success?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*2wWQ7nljWO4piTlenD4E3g.png" /></figure><p><strong>Verdict: Unsuccessful</strong></p><p>After reviewing the HTTP response and the surrounding logs, I found no evidence that the attack was successful.</p><p>The server returned an <strong>HTTP 302 Redirect</strong> with a <strong>response size of 0 bytes</strong>. This means the server redirected the request without returning a response body containing the injected payload.</p><p>I also couldn’t find any evidence of JavaScript execution, data compromise, or suspicious follow-up activity.</p><p>Based on the available evidence, I concluded that the XSS attempt was <strong>unsuccessful</strong>, even though the request itself was malicious.</p><h3>Artifacts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*XxvkcwxBNwtxlLbYLgV8bQ.png" /></figure><h3>Is Tier 2 Escalation Needed?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*W-PAe-gvuL1Wbc_6IKKlFQ.png" /></figure><p><strong>No, Tier 2 escalation was not required.</strong></p><p>Since the investigation found no evidence of successful exploitation, JavaScript execution, or data compromise, I decided that escalation to Tier 2 was not necessary.</p><p>The activity was classified as a <strong>malicious but unsuccessful XSS attempt</strong>. The findings were documented, and the alert could be closed at Tier 1.</p><h3>Closed Alert</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VeUJbE-uQZDeTv8t8snhbQ.png" /></figure><p>After reviewing all the available evidence, I completed the investigation and closed the alert.</p><p>The final verdict was <strong>True Positive — Unsuccessful XSS Attempt</strong>. The request contained a malicious JavaScript payload, but there was no evidence that it was successfully executed or caused any compromise.</p><p>Since the attack was unsuccessful and no further suspicious activity was identified, <strong>Tier 2 escalation was not required</strong>. I documented the findings and closed the alert at Tier 1.</p><h3>Final Determination</h3><p>After completing the investigation, I reached the following conclusions:</p><ul><li><strong>Alert Verdict:</strong> True Positive</li><li><strong>Attack Type:</strong> Reflected Cross-Site Scripting (XSS)</li><li><strong>Attack Status:</strong> Unsuccessful</li><li><strong>Tier 2 Escalation:</strong> Not Required</li></ul><p>The alert was valid because the request contained a genuine malicious JavaScript payload intended to test or exploit an XSS vulnerability. However, there was no evidence that the script was successfully executed. The available evidence suggests that the defensive controls prevented the attack from succeeding.</p><p>The source IP address was also identified as suspicious based on its AbuseIPDB reputation, so continued monitoring is recommended.</p><h3>True Positive or False Positive?</h3><p><strong>Final Verdict: True Positive</strong></p><p>I classified this alert as a <strong>True Positive</strong> because the request contained a clear XSS payload. Even though the attack was unsuccessful, the malicious activity was genuine and the alert correctly detected it.</p><h3>Conclusion</h3><p>This investigation helped me understand how to analyse and classify a potential Reflected XSS attempt.</p><p>The request originated from a suspicious external IP and contained a JavaScript payload injected through the URL’s q parameter. After reviewing the HTTP response and surrounding logs, I found no evidence of successful exploitation or any follow-up malicious activity.</p><p>Based on the findings, I confirmed this as a <strong>True Positive — Unsuccessful XSS Attempt</strong>. No Tier 2 escalation was required, and continued monitoring of the source IP is recommended in case of future suspicious activity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1e931ce576b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC104 — Malware Detected — LetsDefend]]></title>
            <link>https://medium.com/@tanmaydhanula1234/soc104-malware-detected-letsdefend-220e1416d3e2?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/220e1416d3e2</guid>
            <category><![CDATA[letsdefend-writeup]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Thu, 05 Nov 2026 10:43:24 GMT</pubDate>
            <atom:updated>2026-11-05T10:43:24.497Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to my blog!</p><p>In my first post, I’m sharing my experience investigating the <strong>SOC104 — Malware Detected</strong> alert on the <strong>LetsDefend</strong> platform. I’ll walk through the investigation step by step, explain the findings, and share how I analysed the alert to reach the final verdict.</p><h3>1. Initial Alert</h3><p>When I checked the security alerts, I found that the rule <strong>SOC104 — Malware Detected</strong> had been triggered, generating an alert with <strong>Event ID: 36</strong>.</p><p>The alert was related to a file named Invoice.exe, which was detected on the endpoint with the following details:</p><ul><li><strong>Hostname:</strong> AdamPRD</li><li><strong>IP Address:</strong> 10.15.15.18</li><li><strong>File Name:</strong> Invoice.exe</li><li><strong>Event ID:</strong> 36</li></ul><p>I also noticed the <strong>T1204</strong> technique mentioned in the alert. After checking it against the MITRE ATT&amp;CK framework, I found that it corresponds to <a href="https://attack.mitre.org/techniques/T1204/"><strong>T1204 — User Execution</strong></a>.</p><p>This technique indicates that the malware may have been executed through user interaction. Another important thing I noticed was that the security system allowed the file to execute instead of blocking it.</p><p>Since the file was successfully executed, I decided to investigate further to understand whether it was actually malicious and what impact it might have had on the endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*saEJIaTHUnTUoRi7_b1ULg.png" /></figure><h3>2. Define Threat Indicator</h3><p>After creating a ticket and opening the case, I started working through the investigation using the provided playbook.</p><p>To check whether the malware was trying to communicate with any external servers, I selected the <strong>Unknown or unexpected outgoing internet traffic</strong> option.</p><p>This step helps identify any suspicious outbound connections that the malware might have established and gives us a better idea of its network activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*daVLvZ6DP8gDAV-B_Wc1ig.png" /></figure><h3>3. Check if the Malware is Quarantined/Cleaned</h3><p>Next, I clicked on the <strong>Endpoint Security</strong> option to check whether the detected malware had been quarantined or removed from the system.</p><p>I also wanted to review the endpoint’s security status and available activity details to understand what happened after the file was detected.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*SqMHNfCJg7-KjIT_d0bOGQ.png" /></figure><p>When I searched for the <strong>AdamPRD</strong> device in the Endpoint Security section, I noticed that its <strong>Containment</strong> status was showing as <strong>Passive</strong>.</p><p>This means the device was not actively isolated from the network. So, I needed to investigate further to understand whether the malware was still present on the system and if any suspicious activity had occurred.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ppadwwKwjf2xrMgXjIYgQ.png" /></figure><p>When I checked the <strong>Processes</strong> tab, I noticed that the device was showing <strong>No Agent Installed</strong>. Because of this, I couldn’t retrieve any process-related information from the endpoint.</p><p>However, on the alert card, I found that the <strong>Device Action</strong> was marked as <strong>Allowed</strong>. This indicates that the security system allowed the file to execute instead of blocking or quarantining it.</p><p>So, there was no confirmation that the malware had been quarantined or removed from the system.</p><p>Based on the evidence collected so far, I selected the <strong>Not Quarantined</strong> option under the <strong>Check if the malware is quarantined/cleaned</strong> question in the playbook.</p><p>Since the device action was marked as <strong>Allowed</strong> and no quarantine activity was confirmed, I proceeded with the <strong>Not Quarantined</strong> option and moved on to the next step of the investigation.</p><h3>4. Analyze Malware</h3><p>Next, I moved to the <strong>Analyze Malware</strong> section of the playbook. Here, LetsDefend provides a list of recommended third-party tools that can be used to investigate and analyse suspicious files.</p><p>These tools help us check file reputation, identify malicious indicators, and understand the behaviour of the suspected malware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ougrV4AAQHe-_OK2C17yOQ.png" /></figure><p>To investigate the suspicious file further, I took the MD5 hash <strong>f83fb9ce6a83da58b20685c1d7e1e546</strong> from the initial alert and searched for it on <strong>VirusTotal</strong> to check its reputation.</p><p>I also opened the available <strong>ANY.RUN Sandbox Report</strong> and reviewed the analysis details to get a better understanding of how the file behaves during execution.</p><p>This helped me gather more information about the suspicious file and identify any possible signs of malicious activity.</p><h3><strong>VirusTotal</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a0jEvpT6JLBLwmS4Vpt7Rg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9PwdUnngGhnYNhJuRYWojw.png" /></figure><h3><strong>ANY.RUN</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xy0xB5OmAXryHdGM0r2Ejw.jpeg" /></figure><h3>5. Check If Someone Requested the C2</h3><p>Next, I moved to the <strong>Log Management</strong> section to investigate whether the suspicious file had established any communication with external Command and Control (C2) servers.</p><p>The main goal here was to identify any unusual outbound connections that could indicate malware communication with an attacker-controlled server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/805/1*V0qoPJSlM1X9VGZRR7UF0w.png" /></figure><p>I searched the logs using the victim device’s source IP address <strong>10.15.15.18</strong> to check its network activity.</p><p>After reviewing the results, I found that the device was communicating directly with an external IP address <strong>92.63.8.47</strong>, which appeared suspicious.</p><p>This finding could indicate possible Command and Control (C2) communication, so I decided to investigate the external IP further to understand whether it was associated with malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f9cn7YQq1FCSmE34ufOyOA.png" /></figure><h3>6. Containment</h3><p>Since I identified suspicious communication between the victim machine and an external IP address, the next step was to focus on containment.</p><p>To prevent any further suspicious communication and reduce the risk of the malware affecting other systems on the network, I proceeded with isolating the victim machine from the network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/1*E6oJWhSPC-1ymwJO_3hR6A.png" /></figure><p>I searched for the hostname <strong>AdamPRD</strong> again in the <strong>Endpoint Security</strong> section and activated its <strong>Containment</strong> status.</p><p>This action isolated the victim machine from the network, helping prevent further communication with the suspicious external IP address and reducing the risk of the malware spreading or affecting other systems.</p><p>With the endpoint successfully contained, I moved forward with the remaining investigation steps.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DWKGS2ZlyxfXIaU0KBeSmQ.png" /></figure><h3>7. Add Artifacts</h3><p>In this section, I added all the important technical evidence collected during the investigation to the case panel.</p><p>This included the relevant file hash, suspicious IP address, and other indicators that could help document the incident and support further analysis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*3TGXZH0ClrZrT0oF6O9IDg.png" /></figure><h3>8. Close Alert</h3><p>After completing all the investigation steps, I added my final analysis and findings to the analyst notes.</p><p>Since the investigation confirmed malicious activity, I marked the alert as <strong>True Positive</strong> and submitted the case to close it.</p><p>With that, the investigation was successfully completed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YaI47P3S9N1eR0CTjeLMbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gnj-uMiOJ8d9hk0AZXF-TQ.png" /></figure><h3>Conclusion</h3><p>That brings us to the end of this investigation!</p><p>During this SOC104 investigation, I got hands-on experience analysing a malware alert, checking file reputation using VirusTotal, reviewing sandbox analysis in ANY.RUN, identifying suspicious C2 communication, and performing endpoint containment.</p><p>One important takeaway from this lab was understanding how important it is to correlate different sources of evidence before making a final decision. Detecting malware is only one part of a SOC Analyst’s job; knowing how to investigate, respond, and contain threats is equally important.</p><p><strong>Final Verdict: TRUE POSITIVE</strong> 🚨</p><p>Thanks for taking the time to read my write-up! I hope you found it helpful.</p><p>I’ll continue sharing my SOC investigations, hands-on labs, and cybersecurity learning journey. Stay tuned for more!</p><p><strong>Happy Learning &amp; Keep Hunting!</strong> 🔍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=220e1416d3e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malware Analysis:SOC109-Emotet Malware Detected]]></title>
            <link>https://medium.com/@tanmaydhanula1234/malware-analysis-soc109-emotet-malware-detected-93e972cd185c?source=rss-4addcfc91375------2</link>
            <guid isPermaLink="false">https://medium.com/p/93e972cd185c</guid>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[letsdefend-writeup]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[TanmayDhanula]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 18:15:05 GMT</pubDate>
            <atom:updated>2026-11-04T18:15:05.551Z</atom:updated>
            <content:encoded><![CDATA[<p>First lets start with alert information -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BKOz2afwgOicsq7HSH5Qfw.png" /></figure><p>The alert detected <strong>Emotet malware</strong> on <strong>March 22, 2021</strong>, on a system with the hostname <strong>RichardPRD</strong> and IP address <strong>172.16.17.45</strong>. During the investigation, I found that the suspicious activity was linked to a file named <strong>1word.doc</strong>, which could be related to an Emotet malware infection. The alert shows that the malware has been cleaned, but I would still recommend further investigation to make sure the infection is completely removed. We should also check for any persistence mechanisms or additional malicious payloads that might have been installed on the system.</p><h3>Now let’s start analysing the suspicious file —</h3><p>Since the alert already provides the file hash, there is no need to download the suspicious file to the system. If we ever need to analyse the file manually, it would be safer to do it inside an isolated environment, such as a virtual machine.</p><p>For this investigation, I will use the provided hash <strong>349d13ca99ab03869548d75b99e5a1d0</strong> and check it on <strong>VirusTotal</strong> to see if there are any known detections or reputation results for the file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7_PzKH327T9O1LPzb4-fzw.png" /></figure><p>After checking the hash on <strong>VirusTotal</strong>, the results clearly indicate that the file is malicious. I found that 50 <strong>security vendors</strong> flagged the file as malicious, and <strong>6 automated sandbox analyses</strong> also detected suspicious activity. Based on these results, we can confirm that the file is not safe and is likely associated with malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/901/1*x_3h311yX2mjQ2ODuxspbg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_tOS9Cu9BUiR0NZwUYuoaw.png" /></figure><p>As shown in <strong>Figure 2</strong> and <strong>Figure 3</strong>, we can see several malicious URLs and domains contacted by the file.</p><p>Next, I moved to the <strong>Behavior</strong> tab to check how the file behaves inside the sandbox environment. This helps us understand its execution process, identify suspicious activities, and get a better idea of what the malware is doing on the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SLPPpF15jyPstGZqMW1CGA.png" /></figure><p>After reviewing the sandbox results, I found that the file performs several suspicious activities. It creates WMI processes and executes PowerShell and VBScript commands. It also uses different techniques to avoid detection, such as privilege escalation, process injection, masquerading, and long sleep intervals.</p><p>The file also appears to use document macros and possible software vulnerabilities to execute its malicious activities. During the discovery phase, it collects system, process, and file information and also checks for virtualized environments.</p><p>Another thing I noticed is that the file communicates with remote servers using different network protocols. This could be used to download additional malicious payloads and establish command-and-control (C2) communication.</p><p>Based on these findings, we can confirm that the file is malicious. However, dynamic malware analysis would help us understand its execution in more detail and identify its complete impact on the infected system.</p><h3>Endpoint Security —</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*S2_wbi2aZldJzDKqEaqcCg.png" /></figure><p>While checking the endpoint, I couldn’t find any suspicious activity on the system for the date when the alert was generated.</p><h3>Checking Logs —</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oQ6pymf2x3XYQCfRwtI2tw.png" /></figure><p>After reviewing the available logs, I noticed that the recorded events were from before the alert was generated. So, these logs are not very useful for our current investigation, and we would need logs from the relevant time period to get a better understanding of what happened.</p><h3>Dynamic Malware Analysis —</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*LJOOY38kjoZOFhtXJEJjWg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*js0zgXlw_VaRJaXq_19lvw.jpeg" /></figure><p>When I opened the document file, I noticed that it automatically started a PowerShell process. After looking into it further, I found that the PowerShell activity was malicious and was also generating unauthorized network connections. I’ll investigate this network activity in the next steps to understand what the file is trying to do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/328/1*alq6-qLuZRZwBVTm_IL4Hg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/1*TMu-v1oZ3R0cGHR2MRKDxw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*peTm7Zu1pUKqNynkmYWy3w.jpeg" /></figure><p>The URLs contacted by the PowerShell process are also flagged as malicious on <strong>VirusTotal</strong>. I also found the same URLs under the malware’s <strong>Memory Pattern URLs</strong> section in the Behavior tab. The server responses were received in HTML format, which adds more evidence of suspicious network activity.</p><p>With this, we’ve completed our analysis of the suspicious file and its behavior. We now have a better understanding of the malware and its activities.</p><p>Let’s move on to answering the playbook questions.</p><h3>Playbook</h3><p><strong>1- Select threat indicator</strong></p><p>Ans: Unknown or unexpected outgoing internet traffic</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4sluH9Hc2rLlNiX6TEb8QQ.png" /></figure><p><strong>2- Malware quarantined/cleaned?</strong></p><p>Ans: Yes, quarantined and cleaned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qVSpKEnr_oEpQtkyAahE9w.png" /></figure><p><strong>3- Analyze Malware</strong></p><p>Ans: It’s Malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k1KYtTrRwoL9MIlJYVKC3g.png" /></figure><p><strong>4- Check If Someone Requested the C2</strong></p><p>Ans: <strong>Not Accessed</strong>, since we couldn’t find any communication.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ZmAmMrOthHYJUIoygH4zQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sXLTdAfLwyN97NYXfqhfMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BZxm0YhNyunuYjOfr2iz8w.png" /></figure><p>Finally, based on all the evidence collected during the investigation, we can confidently mark this alert as a <strong>True Positive</strong> because the file was confirmed to be malicious and showed suspicious PowerShell execution and network activity.</p><p>With that, we’ve reached the end of this investigation. Hope you found this breakdown helpful! 🙂</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93e972cd185c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>