<?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 Araf Rahman on Medium]]></title>
        <description><![CDATA[Stories by Araf Rahman on Medium]]></description>
        <link>https://medium.com/@arafwho?source=rss-22928e139f7d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*D2An3wk2pnWj9yJQXl2Kjg.jpeg</url>
            <title>Stories by Araf Rahman on Medium</title>
            <link>https://medium.com/@arafwho?source=rss-22928e139f7d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:04:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arafwho/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[SOC257 — VPN Connection Detected from Unauthorized Country]]></title>
            <link>https://medium.com/@arafwho/soc257-vpn-connection-detected-from-unauthorized-country-6486f8356c41?source=rss-22928e139f7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6486f8356c41</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[lets-defend]]></category>
            <dc:creator><![CDATA[Araf Rahman]]></dc:creator>
            <pubDate>Sun, 08 Mar 2026 06:23:24 GMT</pubDate>
            <atom:updated>2026-03-08T06:24:41.508Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sJuCA-8p1yS6UkvXl_stjQ.png" /></figure><h3>Summary</h3><p>On February 13, 2024, at approximately 02:04 AM, a VPN login alert was triggered for user Monica’s account originating from an IP address in Vietnam. Investigation confirmed that the attacker had successfully bruteforced Monica’s password but was ultimately blocked by Multi-Factor Authentication (MFA). The host machine was not compromised. Immediate remediation steps include forcing a password reset for the affected account.</p><p>Alert: true positive.<br>Incident type: unauthorized access.<br>Source IP: external; malicious.<br>No critical systems, sensitive data affected; isolation not neccessary.</p><h3>Threat Intelligence</h3><p>The source IP <strong>113[.]161.158.12</strong> was investigated via VirusTotal and internal threat intelligence feeds:</p><ul><li>Flagged by <strong>8 security vendors</strong> on VirusTotal</li><li>Previously categorized as a <strong>brute force attacker</strong> in threat intel</li><li>Geolocated to <strong>Hanoi, Vietnam</strong></li><li>Access attempted via Chrome on Windows</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Qfk-T_nLVgEZ0V5Uq5sBQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3T9taMCMawRclXBps4HvoQ.png" /></figure><h3>Attack Breakdown</h3><h4>1. Credential Bruteforce</h4><p>The attacker successfully bruteforced Monica’s account password. Network logs confirm a POST request to URI=/logon.html with a 200 response, indicating the password was accepted by the authentication layer. This is the primary point of failure, the account password was weak or previously exposed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IPUaW774Ll1KMyU2IqDXiw.png" /></figure><h4>2. MFA Interception Attempt</h4><p>Following the successful password authentication, the system triggered an OTP email to Monica’s registered address. The attacker’s IP (113[.]161.158.12) is recorded in the MFA notification email, confirming the request originated from their session. The attacker attempted to complete the OTP challenge but failed <strong>3 consecutive times</strong>, preventing account access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u2XzYQloefZkEC05Ho3gLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HrBfg0W5j8uru2GipUSULg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0IYJr28OS_aNLmbmgt7TRw.png" /></figure><h3>Recommendations</h3><ol><li><strong>Force a password reset</strong> for <a href="/service/mailto:monica@letsdefend.io">monica@letsdefend.io</a> with enforcement of strong password policy.</li><li><strong>Block IP 113.161.158.12</strong> on firewall.</li><li><strong>Implement account lockout policies</strong> after 3+ failed authentication attempts to slow future bruteforce campaigns.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fb8YTHSzkFLbP_GHG4MZYw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6486f8356c41" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC251 — Quishing Detected (QR Code Phishing)]]></title>
            <link>https://medium.com/@arafwho/soc251-quishing-detected-qr-code-phishing-e70654f07e17?source=rss-22928e139f7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e70654f07e17</guid>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Araf Rahman]]></dc:creator>
            <pubDate>Sun, 15 Feb 2026 17:57:39 GMT</pubDate>
            <atom:updated>2026-02-15T18:07:09.335Z</atom:updated>
            <content:encoded><![CDATA[<p>We received a SIEM alert that our employee Claire received a potential QR phising email on Jan, 01, 2024, 12:37 PM. Let’s investigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*izmZzArhBfSA8eiCon72Uw.png" /></figure><h3>Analyzing the email</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TCWFNDCU_TxeYe_eQUz7RQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v0vO5VbVf2Gsj5xrX8NcRA.png" /></figure><p>The email urges her to scan a QR code to implement MFA. Failure to do so within a certain time frame threatens with an account block. The first sign of a phishing email is urgency so this isn’t a good sign.</p><p>The email came from security@microsecmfa[.]com, SMPT address 158[.]69.201.47 (<strong>external</strong>).</p><p>The microsecmfa[.]com sender domain is a red flag. Additionally, the SMTP address has been flagged by different security vendors as malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2o4mBZ8WC1c4RNPzbNZkJQ.png" /></figure><h3>Scanning the QR code</h3><p>It’s not wise to use your phone to directly scan and visit the URL as it might be malicious.</p><p>I downloaded the QR code image and used an online tool to get the URL.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MlC2j3M9J7Ptp_rqWn5PHg.png" /></figure><p>This is where the QR code takes us:<br><a href="https://ipfs.io/ipfs/Qmbr8wmr41C35c3K2GfiP2F8YGzLhYpKpb4K66KU6mLmL4#">https://ipfs[.]io/ipfs/Qmbr8wmr41C35c3K2GfiP2F8YGzLhYpKpb4K66KU6mLmL4#</a></p><p>This URL has been flagged as malicious by different security vendors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i5iYebInaH5kb2cHvbFFzA.png" /></figure><p>Visiting the URL in a sandbox instance shows us a 410 error (content removed). This tells us that the page has been blocked due to legal, abuse, malware or security reasons.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x0shp9moQMY-eLDZKnR4Bg.png" /></figure><p>Below is what we should have actually seen (taken from <a href="https://medium.com/@topcyberdawg/letsdefend-soc-walkthrough-soc251-quishing-detected-qr-code-phishing-48c286422ed2">another article</a>), not the 410 error:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tsrHO2R29cZFymbe.jpeg" /></figure><p>From the image, it is clear that attacker is <strong>phishing for information.</strong></p><h3>Analyzing Network Logs</h3><p>We don’t see any network logs from Claire, IP: 172[.]16.17.181.</p><p>As QR codes are scanned from a phone, we won’t have a log of Claire accessing the URL. <strong>It is best to assume she accessed the URL</strong> and gave away her credentials. For this reason, <strong>we contain the endpoint.</strong></p><h3>Analyzing Victim’s Endpoint</h3><p>We analyzed process, network, terminal and browser, however, nothing suspicious was found.</p><h3>Scope of Attack</h3><p>This email was sent only to Claire. Other systems aren’t affected at this moment.</p><h3>True Positive or False Positive?</h3><p>The email is using a QR code to phish for user credentials. The alert is a <strong>true positive.</strong></p><h3>Result</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rsEwDo3lTT0aqZ-7B6nBwQ.png" /></figure><h3>Lessons Learned</h3><p><strong>How did the cyber attack happen?</strong><br>Victim was sent a phishing email with a QR code that takes them to a fake login page. Victim scans the QR code with their phone and gives away login credentials.</p><p><strong>What corrective actions can prevent similar incidents in the future?</strong><br>- Train employees to detect phishing emails<br>- Develop solutions to block phishing emails from reaching inbox.<br>- Implement MFA to make automated phishing harder.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e70654f07e17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOC176 — RDP Brute Force Detected]]></title>
            <link>https://medium.com/@arafwho/soc176-rdp-brute-force-detected-d2b47113ab1a?source=rss-22928e139f7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2b47113ab1a</guid>
            <dc:creator><![CDATA[Araf Rahman]]></dc:creator>
            <pubDate>Sat, 14 Feb 2026 11:13:57 GMT</pubDate>
            <atom:updated>2026-02-15T18:08:36.020Z</atom:updated>
            <content:encoded><![CDATA[<p>On Mar, 07, 2024, 11:44 AM, we receieved an alert that an attacker with <strong>external IP </strong>attempted to brute force the login process and RDP into an internal host.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hmgR3pkKqPXprcKgdPFdQ.png" /></figure><h3>Source Reputation Check</h3><p><strong>Attackers IP is suspicious </strong>according to VirusTotal and AbuseIPDB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7vnd2efmUJutP0M1mdIB_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j03DLO3abjWD61yoU_8cFw.png" /></figure><h3>Network Log Analysis</h3><p>Upon checking 3 paginations worth of logs, we see that the <strong>attacker attempted multiple times to use port 3389 to RDP into the host. </strong>Attacker tried to login using usernames such as admin, guest, sysadmin, Mathew.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lI27FbVZwVAYdnKlG-G6og.png" /></figure><p>After multiple failed attempts, <strong>attacker was successfully able to log in with the Mathew username. </strong>We see Windows EventID 4624 in the log which means successful login.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EcYwwKbydoA89PHzf3R-Qw.png" /></figure><p>This is a brute force attack where attacker used common usernames and passwords to login. Attacker was using an automated tool as we received a high number of login attempts within a single minute (11:44).</p><h3>Scope</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BzM73b0LhMuTlsXwEeyP9w.png" /></figure><p>From network logs, we see that <strong>attacker’s IP only tried to RDP into the Mathew endpoint.</strong></p><h3>Endpoint Analysis</h3><p>We check Mathew’ terminal and see that attacker has run multiple commands. Attacker is trying to perform reconnaissance, which means they’re trying to gather information about the user, system and network in order to launch further attacks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aaU43Gm4FZ_suC6PguJ5EA.png" /></figure><p><strong>The device requires isolation.</strong></p><h3>Lessons Learned</h3><p><strong>Prevent similar incidents in the future:<br></strong>* Require MFA for RDP instead of just username and password. <br>* Allow RDP from only whitelisted IP addresses.<br>* Restrict RDP port access from the internet.<br>* Only allow bastion to RDP into a host.<br>* Lock out an account automatically if brute force attack is suspected.<br>* Keep operating system and RDP services up to date.</p><p><strong>Detect similar incidents in the future:</strong><br>* Look out for RDP logins from unknown IP addresses.<br>* Look for failed login attempts (Windows EventID 4625)</p><h3>Result</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9iS6Gy4nIbm_KkCW5GC9g.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2b47113ab1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend SOC282 — Phishing Alert — Deceptive Mail Detected]]></title>
            <link>https://medium.com/@arafwho/letsdefend-soc282-phishing-alert-deceptive-mail-detected-38d205978433?source=rss-22928e139f7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d205978433</guid>
            <dc:creator><![CDATA[Araf Rahman]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 01:24:03 GMT</pubDate>
            <atom:updated>2026-02-13T02:48:08.990Z</atom:updated>
            <content:encoded><![CDATA[<p>An email promising free coffee was sent to our internal company email <a href="/service/mailto:felix@letsdefend.io">felix[@]letsdefend.io</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OQPk3pX7CJ0D8vhzUL7LEA.png" /></figure><p>The email contains a link and also a free-coffee.zip file attachment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BlixeTlMGX-Hn_LaF9B55g.png" /></figure><p>It is generally safe to download a zip file but it is important you don’t extract it on your computer. If you want to investigate the behavior of this potential malware, you should do this in a sandboxed environment.</p><h3>Analysing sender, link &amp; zip file attachment</h3><p>We investigate the SMTP address (103[.]80[.]134[.]63) on VirusTotal and see that it was flagged by 8 security vendors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tcYXqBlj-709uMI3Nu0wQ.png" /></figure><p>Now let’s investigate the link. We right-click on the link and investigate the sender (<a href="/service/mailto:free@coffeeshooop.com">free[@]coffeeshooop.com</a>) on VirusTotal. 11 security vendors have flagged it as malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2UNpMFPSLyJDexjHXcCr7w.png" /></figure><p>Now let’s investigate the zip file. I downloaded and uploaded it to VirusTotal.</p><p>If you don’t want to download the file, you can also use use the file hash to scan: 6f33ae4bf134c49faa14517a275c039ca1818b24fc2304649869e399ab2fb389</p><p>VirusTotal found that 17 security vendors have flagged the file as malicious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SjqwMWiZF7d_-3pTnWHiLw.png" /></figure><p>Upon seeing all this, we can definitively say that this is <strong>malicious and the alert is true positive.</strong></p><h3><strong>Analysing Felix’s endpoint</strong></h3><p>Upon checking Felix’s browser history, we see that the <strong>malicious link was opened.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pFXmkB_u2QCgY1iwayNpUg.png" /></figure><p>Upon checking terminal history, we see that attacker is trying to gather information about the system and network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzNyO20HU4SvLZSWlt8L0Q.png" /></figure><p>Here’s arough idea on what these commands mean:</p><p>net user: Displays a list of all local user accounts on the system.</p><p>systeminfo: displays detailed information about the operating system and hardware.</p><p>Hostname: displays computer name.</p><p>wmic logicaldisk get caption,description,providername: lists all logical drives on the system, showing their drive letters, type (local/network), and mapped network path</p><p>tasklist /svc: display all running processes.</p><p>ipconfig /all: displays network configuration info.</p><p>route print: displays the system’s IP routing table.</p><p>It is clear that attacker is trying to perform <strong>reconnaissance.</strong> This is where attackers try to gather info before launching further attacks.</p><p>We <strong>delete the email and contain the endpoint</strong> to prevent further damage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EHoK25-P6mesO_zgx9ZwFA.png" /></figure><h3>Artifacts</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iLObEQYq8I4L6rmN5QD2lw.png" /></figure><h3>Result</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MW4Iyyx3F4NwJs6ydLazcw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d205978433" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LetsDefend SOC246 — Forced Authentication Detected Explained]]></title>
            <link>https://medium.com/@arafwho/letsdefend-soc246-forced-authentication-detected-explained-025a04a748b7?source=rss-22928e139f7d------2</link>
            <guid isPermaLink="false">https://medium.com/p/025a04a748b7</guid>
            <category><![CDATA[detecting-web-attacks]]></category>
            <category><![CDATA[lets-defend]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <dc:creator><![CDATA[Araf Rahman]]></dc:creator>
            <pubDate>Thu, 12 Feb 2026 03:37:10 GMT</pubDate>
            <atom:updated>2026-02-13T01:30:37.825Z</atom:updated>
            <content:encoded><![CDATA[<h3>LetsDefend SOC246 — Forced Authentication Detected</h3><p>We will invest a SOC alert on the LetsDefend SIEM about a potential authentication attack that occurred on 12 Dec 2023.</p><p>The alert occured because IP 120[.]48.36.175 made an unusual number of POST requests to the web server’s login endpoint. This suggests a potential brute force credential attack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LBmztRgebG5LNlthAe-r_g.png" /></figure><h3>Log Analysis</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkvxzjfSRV5Qgkoupx-AeQ.png" /></figure><p>We see multiple POST requests to the same login endpoint, where the attacker used different set of credentials to try to login. This is known as a <strong>brute force credential attack (select attack type as Other on LetsDefend). </strong>One such example is this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QrrLDWmJHoqClH66vJAgQ.png" /></figure><p>I checked internal company emails and there is<strong> no sign that this was a planned test attack.</strong></p><p><strong>The traffic is definitely malicious and the alert is a true positive.</strong></p><p>On Dec, 12, 2023, 02:15 PM, the source IP was able to successfully log with admin credentials. The attack was unfortunately successful. The web server is under the attacker’s control now and they can launch further attacks into our internal network, so <strong>tier 2 escalation is needed.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Z4_1qwMER-G4O5l8tG90A.png" /></figure><p>By looking at what credentials the attacker used at 2:15 pm before successfully logging in, we find out what credential was used to log in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BUILjUTJtJrUqEuDobIbXw.png" /></figure><p>The web server was using weak and possibly default credentials. The attacker was able to try common weak credentials to log in.</p><h3>Direction of Traffic Flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b5QP12zqHqCVI2rHRT2A9w.png" /></figure><p>Let’s look at both IP addresses:<br>Source ip: 120[.]48.36.175<br>Dest ip: 104[.]26.15.61</p><p>Source IP is a public IP, while destination IP belongs to our web server. Thus, traffic is coming <strong>from internet to company network.</strong></p><h3>Results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nRh__Jd3-nNkyNV1yP8XXg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=025a04a748b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>