<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hanu — detection engineering</title>
    <link>https://hanu.taksham.org</link>
    <description>Hanu runs in your own cloud, correlates signals from cloud, identity, CI/CD, certificate and AI surfaces into compound attack chains, and shows the evidence behind every finding. Self-hosted, source-available (Elastic License 2.0).</description>
    <language>en</language>
    <atom:link href="https://hanu.taksham.org/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The October 2026 attack cluster</title>
      <link>https://hanu.taksham.org/incidents/october-2026-attack-cluster</link>
      <guid isPermaLink="true">https://hanu.taksham.org/incidents/october-2026-attack-cluster</guid>
      <description>Five campaigns from 23 Sep to 23 Oct 2026 shared one mechanism: trust that was already granted. The mechanics, the signals, and the named gaps.</description>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>EvilTokens: phishing that never asks for the password</title>
      <link>https://hanu.taksham.org/incidents/eviltokens</link>
      <guid isPermaLink="true">https://hanu.taksham.org/incidents/eviltokens</guid>
      <description>EvilTokens used device-code phishing to take 12,000 inboxes without passwords, then had an AI read them for fraud. What Hanu catches, and what it does not.</description>
      <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>eMudhra: when the certificate authority is the supply chain</title>
      <link>https://hanu.taksham.org/incidents/emudhra-ca-compromise</link>
      <guid isPermaLink="true">https://hanu.taksham.org/incidents/emudhra-ca-compromise</guid>
      <description>Eight eMudhra intermediate CA keys were weak enough to recover — one was the integer 4. What that means for your certificates, and what Hanu checks.</description>
      <pubDate>Tue, 20 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>GhostAction: the build robots became the exfiltration channel</title>
      <link>https://hanu.taksham.org/incidents/ghostaction</link>
      <guid isPermaLink="true">https://hanu.taksham.org/incidents/ghostaction</guid>
      <description>GhostAction pushed a workflow named security-audit.yml into 340+ repositories and took 3,325 secrets. The mechanism, the signals, and what a cloud scanner cannot see.</description>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Correlating CI tampering: the pair is the finding</title>
      <link>https://hanu.taksham.org/blog/correlating-ci-tampering</link>
      <guid isPermaLink="true">https://hanu.taksham.org/blog/correlating-ci-tampering</guid>
      <description>A changed workflow file is an ordinary Tuesday. A changed workflow in a repository that holds a deploy credential is a finding. How the join works.</description>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Detecting LLMjacking: validate, enumerate, invoke</title>
      <link>https://hanu.taksham.org/blog/detecting-llmjacking</link>
      <guid isPermaLink="true">https://hanu.taksham.org/blog/detecting-llmjacking</guid>
      <description>Cost anomalies cannot tell a busy week from a hijacked key. The kill chain can: first-ever credential validation, model enumeration, then invocation.</description>
      <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why the detection path has no LLM in it</title>
      <link>https://hanu.taksham.org/blog/why-detection-has-no-llm</link>
      <guid isPermaLink="true">https://hanu.taksham.org/blog/why-detection-has-no-llm</guid>
      <description>A model in the scoring path costs you reproducibility, an explainable queue and regression tests. What it is genuinely good for, and where the line is.</description>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Proving a finding six months later</title>
      <link>https://hanu.taksham.org/blog/proving-a-finding-six-months-later</link>
      <guid isPermaLink="true">https://hanu.taksham.org/blog/proving-a-finding-six-months-later</guid>
      <description>Detection is the easy half. What has to be true at detection time for a finding to still be defensible in a review six months later.</description>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
