<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://blog.ospreycyber.net/feed.xml" rel="self" type="application/atom+xml" /><link href="https://blog.ospreycyber.net/" rel="alternate" type="text/html" /><updated>2026-11-13T00:31:01+00:00</updated><id>https://blog.ospreycyber.net/feed.xml</id><title type="html">Security Circus</title><subtitle>Escapades in cyber: write-ups of real phishing emails, the lures, the infrastructure, the TTPs and the indicators.</subtitle><author><name>omarisml</name></author><entry><title type="html">Welcome to Security Circus</title><link href="https://blog.ospreycyber.net/2026/11/12/welcome/" rel="alternate" type="text/html" title="Welcome to Security Circus" /><published>2026-11-12T00:00:00+00:00</published><updated>2026-11-12T00:00:00+00:00</updated><id>https://blog.ospreycyber.net/2026/11/12/welcome</id><content type="html" xml:base="https://blog.ospreycyber.net/2026/11/12/welcome/"><![CDATA[<p>This is where I’ll write up interesting phishing emails I come across: the clever ones, the new tricks, and the occasional campaign that’s just bad enough to be funny.</p>

<h2 id="what-each-write-up-covers">What each write-up covers</h2>

<p>Every analysis follows roughly the same structure, so they’re easy to compare and skim:</p>

<ol>
  <li><strong>Summary.</strong> What was impersonated and what the attacker wanted.</li>
  <li><strong>The email.</strong> A redacted screenshot, the sender details and the lure.</li>
  <li><strong>Header analysis.</strong> SPF, DKIM and DMARC results, and where the email really came from.</li>
  <li><strong>Infrastructure.</strong> The links, redirects, domains and hosting behind it.</li>
  <li><strong>Landing page or payload.</strong> What happens if someone clicks.</li>
  <li><strong>TTPs.</strong> The techniques used, mapped to MITRE ATT&amp;CK.</li>
  <li><strong>Indicators of compromise.</strong> A table of defanged IOCs for defenders to hunt with.</li>
  <li><strong>Takeaways.</strong> Detection ideas and lessons.</li>
</ol>

<h2 id="how-indicators-look-here">How indicators look here</h2>

<p>All URLs, domains and IPs are <strong>defanged</strong> so they can’t be clicked by accident. The examples below use reserved documentation addresses, not real indicators:</p>

<table>
  <thead>
    <tr>
      <th>Type</th>
      <th>Indicator</th>
      <th>Notes</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Domain</td>
      <td><code class="language-plaintext highlighter-rouge">example[.]com</code></td>
      <td>Landing page</td>
    </tr>
    <tr>
      <td>URL</td>
      <td><code class="language-plaintext highlighter-rouge">hxxps://example[.]com/login</code></td>
      <td>Credential form</td>
    </tr>
    <tr>
      <td>IP</td>
      <td><code class="language-plaintext highlighter-rouge">192.0.2[.]10</code></td>
      <td>Hosting</td>
    </tr>
  </tbody>
</table>

<blockquote class="note">
  <p>To use an indicator in your own tools, “refang” it by replacing <code class="language-plaintext highlighter-rouge">hxxp</code> with <code class="language-plaintext highlighter-rouge">http</code> and <code class="language-plaintext highlighter-rouge">[.]</code> with <code class="language-plaintext highlighter-rouge">.</code>.</p>
</blockquote>

<p>More soon.</p>]]></content><author><name>omarisml</name></author><category term="meta" /><summary type="html"><![CDATA[This is where I’ll write up interesting phishing emails I come across: the clever ones, the new tricks, and the occasional campaign that’s just bad enough to be funny.]]></summary></entry></feed>