<?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 rangbuls on Medium]]></title>
        <description><![CDATA[Stories by rangbuls on Medium]]></description>
        <link>https://medium.com/@rangbuls?source=rss-bd4e6bd0ebd7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*wApCv6CIOH9NvE8h</url>
            <title>Stories by rangbuls on Medium</title>
            <link>https://medium.com/@rangbuls?source=rss-bd4e6bd0ebd7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:29:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rangbuls/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[IP and Domain Threat Intel | TryHackMe Walkthrough]]></title>
            <link>https://medium.com/@rangbuls/ip-and-domain-threat-intel-tryhackme-walkthrough-e5bf907ab53d?source=rss-bd4e6bd0ebd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5bf907ab53d</guid>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[tryhackme-writeup]]></category>
            <category><![CDATA[tryhackme-walkthrough]]></category>
            <dc:creator><![CDATA[rangbuls]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 09:14:40 GMT</pubDate>
            <atom:updated>2026-06-17T09:14:40.621Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>IP and Domain Threat Intel | TryHackMe</strong></h3><h3>Task 1 Introduction</h3><p>Security Operations runbooks revolve around the process verify → enrich → decide, and IP and domain enrichment remains a core skill any L1 should have. In this room, we will pivot on geolocation, ASNs, open-service footprints, and DNS records to decide whether the indicator is malicious or not, and also get some additional context about the attack.</p><h4>Learning Objectives</h4><ul><li>Enrich domains with WHOIS age, DNS records, and TLS details</li><li>Learn the concepts of ASNs and geolocation for SOC triage</li><li>Spot red-flag services using VirusTotal, Shodan, and Censys</li><li>Detect VPN, proxy, and Tor exit nodes with IP2Proxy and Spur</li><li>Correlate signals across sources instead of trusting one verdict</li></ul><h4>Prerequisites</h4><ul><li><a href="https://tryhackme.com/room/cyberthreatintel">Intro to Cyber Threat Intel</a></li><li><a href="https://tryhackme.com/room/fileandhashthreatintel">File and Hash Threat Intel</a></li></ul><h4>Practice</h4><p>Before we start, download the archive with the exported threat intel attached to this task. You’ll need it for most of the exercises, since live threat intel changes daily, and the data you query today may look different tomorrow.</p><p><a href="https://tryhackme.com/room/ipanddomainthreatintel">Download Task File</a></p><h3>Task 2 Domain Enrichment</h3><h4>Resolving DNS Domains</h4><p>Every time a user clicks a link or a system resolves a hostname, the Domain Name System (DNS) springs into action. DNS is the mechanism that converts human-friendly names like <a href="https://tryhackme.com/">tryhackme.com</a> into IP addresses that machines understand. Let’s first check out what analysts can get from a regular domain using tools like <a href="https://www.nslookup.io/">nslookup.io(opens in new tab)</a> or <a href="https://dnschecker.org/">dnschecker.org(opens in new tab)</a>.</p><p><strong>A / AAAA Records<br></strong>These records map the domain to IPv4 and IPv6 addresses. For example, tryhackme.com resolves to an Amazon IP address, which means it is either hosted in AWS cloud, or uses a proxy that uses AWS (in this case, Vercel CDN). You can then investigate the resolved IP and see if it is tied to a known APT infrastructure or maps to a known attack campaign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IPST5Tz1LQXQ8qs6.png" /></figure><p><strong>TXT Records<br></strong>TXT records can tell a lot about the domain: from its mail security settings (SPF/DKIM) to the tools it uses. Below, you can see that tryhackme.com uses Google Workspace and Zapier and has legitimate-looking SPF records. On the other hand, an attack on infrastructure will generally have empty TXT records or point you to some interesting discoveries, such as suspicious SPF records or a faked DKIM signature, often abused during phishing campaigns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*REIfqSqRrHcndWP-.png" /></figure><p><strong>WHOIS / RDAP<br></strong><a href="https://whois.domaintools.com/">WHOIS(opens in new tab)</a> (gradually being replaced by RDAP) is another useful tool for domain enrichment. It reveals information such as the registrar, registration, and expiry dates, and, most importantly, the domain’s age. Modern attack infrastructure rarely stays online for more than a few months, since it is either taken down or rotated to avoid detection. Below, you can see that tryhackme.com has been registered for nearly 10 years, which is a reassuring sign. Malicious domains, by contrast, often live for only a few days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/997/0*9_DoiqYus95DI6li.png" /></figure><h4>Attack Techniques Using DNS</h4><ul><li><strong>CDN Abuse<br></strong>Attackers route malicious traffic through legitimate CDNs like Cloudflare, Akamai, or Fastly to hide the real origin server. If an A record points to a CDN range, the IP itself won’t tell you much, since the same IP can front thousands of legitimate and malicious services simultaneously.</li><li><strong>Typosquatting<br></strong>Domains like tryhakme[.]com or micros0ft[.]net rely on visual similarity to trick users. Treat any look-alike of a known brand as high risk. Note that companies can register obvious typos of their own domain defensively, so a typosquat resolving to the legitimate brand is not necessarily malicious.</li><li><strong>IDN Attacks<br></strong>Domain names allow non-ASCII characters, which adversaries abuse by substituting Cyrillic or Greek letters that look identical to Latin ones. For example, tryhаckme[.]com uses a Cyrillic &quot;а&quot; in place of the Latin one. The domain looks the same, but resolves entirely differently. When in doubt, convert the domain to its Punycode representation (the xn-- form) using a tool like <a href="https://www.punycoder.com/">punycoder.com(opens in new tab)</a>. If the result starts with xn--, the domain contains non-ASCII characters and needs a closer look.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AfQYajDy9IpbWGP6.png" /></figure><h4>SOC Practice</h4><p><strong>On June 1, 2026</strong>, the SIEM raises a critical alert pointing to the domain purematrixa[.]com. As an L1 analyst, enrich this indicator by using tools such as <a href="https://www.nslookup.io/">nslookup.io(opens in new tab)</a> or <a href="https://whois.domaintools.com/">whois.domaintools.com(opens in new tab)</a>.<br><strong>IMPORTANT NOTE</strong>: Domain intel changes rapidly, so online tools may give you incorrect answers over time.</p><ul><li>To answer the questions, please use the attached PDF reports</li><li>However, you are encouraged to try out online tools as well</li></ul><p><strong>Answer the questions below</strong></p><p>Which CDN does the purematrixa[.]com domain use?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*NjeVuLCYgfhwzkGn-koyeg.png" /></figure><p><strong>Answer : Cloudflare</strong></p><p>According to the report, how old was the domain when SIEM raised an alert?Answer Example: 2 years old</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*F1BPPm5TjHf4ZW83JlHFEQ.png" /></figure><p><strong>Answer : 1 days old</strong></p><h3>Task 3 IP Enrichment</h3><h4>IP Enrichment Within the SOC</h4><p>Most SIEM or EDR alerts contain at least one IP address. An IP address could belong to a compromised router in a home office, a shared CDN edge, or a cloud service used by thousands of tenants. Without enrichment, we risk overreacting (blocking legitimate infrastructure) or underreacting (ignoring a real command-and-control server). The simplest enrichment L1 can do is to query the IP address in two services:</p><ul><li><a href="https://www.abuseipdb.com/">AbuseIPDB(opens in new tab)</a>: To see if the IP was involved in any port scans or brute-force attacks</li><li><a href="https://www.virustotal.com/">VirusTotal(opens in new tab)</a>: To get the overall IP reputation and read its community comments (if any)<br><strong>Note</strong>: if the IP is not within the CDN range, even 1 detection is an indicator of a risky IP</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*COaX2qbIWaouGu3g.png" /></figure><h4>Autonomous Systems</h4><p>An<strong> </strong>Autonomous System (AS) is a collection of IP prefixes under a single organization’s control. Each AS is assigned a unique number (ASN). <a href="https://bgp.tools/">BGP.Tools(opens in new tab)</a> website would give you the most comprehensive info about the AS and its purpose. Looking at the ASN helps analysts assess the likely role of an IP, for example:</p><ul><li><strong>Residential ASNs</strong>: Alerts on these may indicate VPN usage or compromised consumer devices.<br>Example: AS124888 (Vodafone)</li><li><strong>Server Hostings</strong>: The most risky role, as it is often used by adversaries to distribute malware.<br>Example: AS215439 (PLAY2GO)</li><li><strong>Cloud/CDN ASNs</strong>: Used by both legitimate services and adversaries, needs deeper analysis.<br>Example: AS16509 (Amazon AWS)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ch5nfrq9od9kCXlG.png" /></figure><h4>Geolocation (GeoIP)</h4><p>Geolocation enrichment complements ASN lookup and is useful during the investigation of anomalous logons. Tools like <a href="https://ipinfo.io/">ipinfo.io(opens in new tab)</a> and <a href="https://iplocation.net/">iplocation.net(opens in new tab)</a> provide approximate country, but city-level accuracy is generally unreliable. Overall, geolocation lookup helps you with:</p><ul><li><strong>User logon analysis</strong>: If a US-based employee logs on from the Netherlands, it might indicate an intrusion</li><li><strong>Network analysis</strong>: If you monitor a local European company, any traffic to, let’s say, Vietnam is suspicious</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bnVcwkVbgkaSgX37.png" /></figure><h4>SOC Practice</h4><p>Another alert appears, now pointing to 2[.]58[.]56[.]50, a potential C2 server address. Use the learned tools and services (e.g., VirusTotal and BPG.Tools) to answer the questions.</p><p><strong>IMPORTANT NOTE:</strong> Same as with domains, IP ownership changed rapidly.</p><ul><li>To answer the questions, please use the attached PDF reports</li><li>However, you are encouraged to try out online tools as well</li></ul><p>Answer the questions below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*w8pdX3GZ8OA9DM3Ykbj7Tg.png" /></figure><ul><li>What country does the malicious IP resolve to?<br><strong>Answer : Netherlands</strong></li><li>Looking at VirusTotal comments, what C2 server is hosted behind the IP?<br><strong>Answer : Remcos</strong></li><li>What Autonomous System does the IP belong to? (Full name)<br><strong>Answer : 1337 Services GmbH</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*b4UzToqMbfUTqBd263sx8w.png" /></figure><p>According to BGP.Tools, ASN 210558 (1337 Services GmbH) is associated with two tags: Server Hosting and Tor Services.</p><ul><li>What two tags does BPG.Tools attribute to the ASN? (Tag1, Tag2)<br><strong>Answer : Server Hosting, Tor Services</strong></li></ul><h3>Task 4 Service Exposure</h3><h4>Exposed Services</h4><p>Knowing what services are exposed on an IP is useful from two angles. The <strong>first</strong> is when you’re looking at a victim’s public IP address and trying to figure out how the attacker got in. If SSH is exposed, it’s likely a starting point. The <strong>second</strong> is when you look up the attacker’s IP. If it runs outdated services or has RDP exposed, the host was likely compromised and is being used as a jump point by attackers.</p><p><strong>Shodan Reconnaissance<br></strong><a href="https://www.shodan.io/">Shodan(opens in new tab)</a> is a powerful reconnaissance tool for IP address analysis. By indexing internet-connected devices and services, Shodan provides detailed information about open ports, running services, and system configurations. Let us look at the IP address from our flagged list, 69[.]197[.]185[.]26. You can do it by visiting the Shodan website and pasting the defanged IP in the search box:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fB2Db_UQSqz7LU-1.png" /></figure><p>From our search, we can extract information on:</p><ul><li><strong>Open Ports</strong>: This is the first fingerprint of exposure. Both Nginx and Rsync can be targeted by threat actors.</li><li><strong>Service Banners</strong>: These provide hints on service versions. An old version usually means a vulnerable version.</li></ul><p><strong>Censys Search<br></strong><a href="https://search.censys.io/">Censys.io(opens in new tab)</a> can be a good alternative to Shodan for blue teams, as it shows exposed services even on non-standard ports and provides some advanced search capabilities. However, note that some of these features may require an account on the platform. For example, below you may see that Censys found yet another exposed port, 56003/SSH.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o-KeEqNYy6gJEbS8.png" /></figure><h4>TLS Certificates</h4><p>IPs that expose HTTPS services bring in a new interesting indicator: TLS certificates. We can use tools such as <a href="https://crt.sh/">crt.sh(opens in new tab)</a> to look at TLS certificate information as a gold mine for enrichment (Note that the service is often unavailable due to high request volume). Alternatively, we can investigate the certificates with Censys or <a href="https://www.sslshopper.com/ssl-checker.html">SSL Shopper(opens in new tab)</a>. The key fields to look out for include:</p><ul><li><strong>Issuer</strong>: A self-signed certificate is a strong indicator that the website is worth investigating</li><li><strong>Validity</strong>: Newly-created and long-lived certificates can also indicate malware infrastructure</li><li><strong>Subject</strong>: For self-certificates, this can point to a program behind the HTTPS (e.g., Pfsense)</li></ul><h4>SOC Practice</h4><p>This time, you are asked to help with a deeper investigation of 64[.]89[.]160[.]44. The IP is clearly malicious, but the CTI team wants to get more context on the IP&#39;s role.</p><p><strong>IMPORTANT NOTE:</strong> Shodan and Censys save information for just a few weeks.</p><ul><li>To answer the questions, please use the attached screenshots</li><li>However, you are encouraged to try out online tools as well</li></ul><p>Answer the questions below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5qDkqjGuPsmc79fmlIDoRw.png" /></figure><ul><li>Refer to the attached Censys screenshots. What remote access service is exposed?<br><strong>Answer : RDP</strong></li><li>How many ports have been identified as open on the server?<br><strong>Answer : 9</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GFkG36InfwEN5uyYTNX-iQ.png" /></figure><p>While reviewing the services exposed by the target IP in Censys, I noticed an unknown service running on TCP port 1000. Inspecting its TLS certificate provided additional details about the service, including information that revealed the name of the framework associated with it. Based on the certificate data, I was able to identify the active Command-and-Control (C2) server.</p><ul><li>One of the exposed services leaks an active C2 server! What is the name of that C2? (E.g., Cobalt Strike)<br><strong>Answer : AsyncRAT</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fLeQZxbUHN0x0V0WBvQGTg.png" /></figure><p>During service enumeration in Censys, I discovered an unknown service on <strong>TCP port 7777</strong>. The TLS certificate identified it as <strong>DcRat</strong>, and by examining the certificate details via its fingerprint, I obtained the validity period required to answer the question.</p><ul><li>For how many days is the C2 server’s certificate valid?<br><strong>Answer : 3935</strong></li></ul><h3><strong>Task 5 VPN Detection</strong></h3><h4>VPN Detection</h4><p>Consider this scenario: you’re investigating an alert about a Microsoft 365 login outside working hours. The location looks normal: same country, same city, same user-agent. An inexperienced analyst would close the alert as a False Positive, and that’s exactly what attackers count on. Services like ProtonVPN, NordVPN, and dozens of others make it trivial to fake any location in the world. Thus, the SOC’s job is to answer one question: Is this a real user, or someone behind a VPN?</p><p><strong>IP2Proxy and Spur</strong></p><p><a href="https://www.ip2proxy.com/">IP2Proxy(opens in new tab)</a> and <a href="https://spur.us/">Spur(opens in new tab)</a> are two essential resources for labeling VPN, proxy, and Tor exit nodes. Both have a free tier for personal use, but you should push your company to buy a subscription and integrate it with your SIEM. For example, the screenshot below shows that 185[.]98[.]171[.]238 is a known VPN node, which means you can&#39;t trust the geolocation of users behind it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZAD-C7y5f07efrnv.png" /></figure><h4>SOC Analyst Workflow</h4><p>At a minimum, our workflow for IP and domain threat intel would look as follows.<br>Be mindful that some steps may be skipped or reordered depending on the alert.</p><p><strong>Investigate the domain</strong></p><ul><li>Does it “look” legit? Does it remind you of typosquatting?</li><li>What is its reputation? Is it a known malicious domain?</li><li>When was it registered? If it’s new, that’s suspicious.</li><li>Resolve the domain to IP and investigate the IP.</li></ul><p><strong>Investigate the IP</strong></p><ul><li>Is it a CDN range? If yes, no need to investigate further.</li><li>What is its reputation? Use VirusTotal, AbuseIPDB, etc.</li><li>Where is it located? Is it a VPN node? How does it match the alert?<br>(Example: US-based user is not expected to log in from Asia)</li><li>What AS type does it belong to? How does it match the alert?<br>(Example: employees are not expected to log in from cloud hosting)</li></ul><p>Answer the questions below</p><ul><li>A London-based user logs in from a London IP address.<br>You can confirm the IP belongs to a Mullvad VPN provider.<br>Would you raise the alarm and prioritize the alert (Yea/Nay)?<br><strong>Answer : Yea</strong></li><li>Same scenario, but the IP doesn’t match any VPN providers.<br>Would you close the alert as a False Positive then? (Yea/Nay)<br>Note: Please read the hint once you attempt an answer.<br><strong>Answer : Nay</strong></li></ul><h3>Task 6 Challenge</h3><h4>Challenge</h4><p>An APT group has just struck your company, and the Incident Response team is working through it. As an L1 analyst, you’ve volunteered to help and have been tasked with gathering everything you can on a malicious domain and identifying the infrastructure the malware relies on. The domain is:</p><ul><li>raytracingengine[.]com</li></ul><p><strong>NOTE</strong>: Start with the online tools covered earlier. If they return nothing useful, which is likely, since attacker infrastructure is short-lived and often already taken down within days, fall back to the attached incident report for exported enrichment data.</p><p>Answer the questions below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*mMeW9WHiAXQeToo3B7K-pA.png" /></figure><p>Using NSLookup, I identified that raytracingengine.com resolves to the IPv4 address 35.188.105.97. The lookup also showed that the address is hosted on Google Cloud (AS396982), providing insight into the infrastructure behind the domain.</p><ul><li>What IP does the domain resolve to?<br><strong>Answer : </strong>35.188.105.97</li><li>What cloud provider did the attacker use? (E.g., Amazon Cloud)<br><strong>Answer : Google Cloud</strong></li><li>What country is the malicious server located in? (E.g., France)<br><strong>Answer : United States</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*sPW1bf-RqjzYE_-yi5WJKQ.png" /></figure><p>We can also use tools such as WHOIS to gather additional information about a domain. For raytracingengine.com, the lookup revealed the registrar, registration dates, and other details that help provide a better understanding of the domain’s background.</p><ul><li>When was the malicious domain name created? (E.g., 24.05.2026)<br><strong>Answer : </strong>21.02.2026</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*q82YyF4sL8ObBg6mmWTOkg.png" /></figure><p>We can also use tools such as Censys to identify exposed services and open ports. For 35.188.105.97, the host was found to expose several services, including SSH, SMTP, and multiple HTTP-based services, helping us better understand the target’s attack surface.</p><ul><li>According to the exposed service, what is the attack server’s OS?<br><strong>Answer : Linux</strong></li></ul><h3>Conclusion</h3><blockquote>Throughout this room, I learned how to investigate IP addresses and domains using various threat intelligence techniques and OSINT tools. Starting from a domain name, I gathered information through DNS lookups, WHOIS records, ASN data, and TLS certificates to better understand the infrastructure behind the target. I also used Censys to identify exposed services and uncover indicators such as C2-related certificates. These techniques provide valuable context during threat hunting, incident response, and alert triage by helping analysts quickly identify ownership, hosting providers, exposed services, and potentially malicious infrastructure.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5bf907ab53d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>