<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cybercrime.club</title><link>https://cybercrime.club/tags/incident-anatomy/</link><description>Infrastructure security news for people who build infrastructure.</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 07 Jun 2026 10:00:00 -0400</lastBuildDate><atom:link href="https://cybercrime.club/tags/incident-anatomy/" rel="self" type="application/rss+xml"/><item><title>Anatomy of the Interlock Campaign: How a ClickFix Gang Learned to Burn Firewall Zero-Days</title><link>https://cybercrime.club/deep-dives/anatomy-interlock-ransomware-clickfix-to-cisco-zero-day/</link><pubDate>Sun, 07 Jun 2026 10:00:00 -0400</pubDate><guid>https://cybercrime.club/deep-dives/anatomy-interlock-ransomware-clickfix-to-cisco-zero-day/</guid><description>For a year, the surest way to get hit by Interlock was to paste a command into your own Run dialog. On January 26, 2026, the group stopped waiting for users to make mistakes and started exploiting a pre-auth, root-level Cisco firewall zero-day instead. The same crew now runs both ends of the sophistication ladder — and that should change how you model initial access.</description></item></channel></rss>