Skip to content

Commit 2ab0c36

Browse files
committed
Fix build
1 parent c346837 commit 2ab0c36

2 files changed

Lines changed: 2 additions & 3 deletions

File tree

src/data/challenges.ts

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -143,7 +143,6 @@ Analyze the attached SMTP log. Identify the spoofing technique, locate the hidde
143143
author: 'nikolap994',
144144
writeupAvailable: true,
145145
},
146-
]
147146

148147
{
149148
id: 'phish-kit',

src/pages/blog/phishing-infrastructure-analysis.astro

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,15 +53,15 @@ const description = 'Phishing campaigns rarely use a single domain. This post ex
5353

5454
<h2>What the data looks like</h2>
5555
<p>A passive DNS registration feed for a 72-hour window might look like this in JSON:</p>
56-
<pre class="code-block"><code>{
56+
<pre class="code-block"><code>{`{
5757
"domain": "paypal-secure-login.net",
5858
"registered": "2026-06-14T07:22:00Z",
5959
"registrar": "QuickReg LLC",
6060
"nameservers": ["ns1.phastdns.cc", "ns2.phastdns.cc"],
6161
"privacy": false,
6262
"registrant_email": "phish.operator99@proton.me",
6363
"ip": "185.220.101.47"
64-
}</code></pre>
64+
}`}</code></pre>
6565
<p>A single record like this — with <code>"privacy": false</code> — is the thread that unravels the campaign. Every other record with the same registrar, nameserver pair, and IP range belongs to the same operator.</p>
6666

6767
<h2>Automating the analysis</h2>

0 commit comments

Comments
 (0)