<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Threat Hunting on Jonias Fortuna</title>
    <link>https://potato.id/en/tags/threat-hunting/</link>
    <description>Recent content in Threat Hunting on Jonias Fortuna</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 01 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://potato.id/en/tags/threat-hunting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I Get Access ClickFix Dashboard Due to Bad SecOps</title>
      <link>https://potato.id/en/posts/weak-secops-exposed-clickfix-dashboard/</link>
      <pubDate>Sat, 16 May 2026 00:00:00 +0000</pubDate>
      <guid>https://potato.id/en/posts/weak-secops-exposed-clickfix-dashboard/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;That afternoon, one of my monitoring teammates casually mentioned a new alert: “Why is this user opening a Polygon crypto website?” That immediately caught my attention and I suspected the user had accessed a website infected with ClickFix.&lt;/p&gt;&#xA;&lt;p&gt;The suspicion became stronger because the user was not from the IT team and had no known involvement with cryptocurrency or Web3-related activities. In addition, a few days earlier we had investigated another incident where a user accidentally visited a ClickFix-infected website, which led to several IoCs, including connections to Web3 Polygon infrastructure used by the threat actor to host malware payloads.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
