Asi botnet-studies

Botnet architecture taxonomy, detection techniques, and defensive analysis. Covers C2 topologies, DGA analysis, fast-flux detection, P2P overlay mapping, blockchain C2, and ML-based traffic fingerprinting. Defensive research for understanding and countering distributed malicious infrastructure.

install
source · Clone the upstream repo
git clone https://github.com/plurigrid/asi
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/plurigrid/asi "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/botnet-studies" ~/.claude/skills/plurigrid-asi-botnet-studies && rm -rf "$T"
manifest: skills/botnet-studies/SKILL.md
source content

Botnet Studies: Defensive Architecture Analysis

Status: Active Trit: -1 (VALIDATOR — analyzes and constrains adversarial infrastructure) Context: Defensive security research, CTF, authorized pentesting, academic study


Architecture Taxonomy

Topologies

TopologyResilienceDisruption DifficultyKey Weakness
Centralized C2LowLow (sinkhole/seize)Single point of failure
Fast-fluxMediumMedium (DNS rotation)TTL analysis reveals pattern
P2P overlayHighHigh (graph fragmentation)High-degree node removal
Hybrid (C2 + P2P fallback)HighHighMust disrupt both layers
Blockchain C2Very HighVery High (immutable state)On-chain pattern analysis

Modern Families (2025-2026)

FamilyTopologyVectorDistinguishing Feature
Mirai variants (Gayfemboy, Jackskid, LZRD)Centralized/HybridIoT default creds, zero-daysRust cross-compilation, 40K+ daily bots
KimwolfCentralizedCorporate/gov networks, Android TVDynamic C2 shifting
AisuruCentralizedIoT mass compromiseRecord DDoS volume, real-time load shifting
TsundereBlockchain C2Game installer masqueradeEthereum smart contract stores C2 URLs
Badbox 2.0CentralizedPre-installed Android malware10M devices as residential proxies
EmotetCentralizedPhishing → loader chainPeriodic resurrection post-takedown

Blockchain C2 (Emerging Threat)

Operator → 0 ETH tx → Smart Contract (state update: new C2 URL)
                              ↓
Bot → public RPC → read contract state → connect to new C2

Immutable. Cannot be seized. Traditional sinkholing fails. Counter: on-chain pattern analysis, RPC endpoint monitoring, contract interaction fingerprinting.


Detection Techniques

DGA Analysis

Domain Generation Algorithms produce pseudo-random domains (thousands/day). Only botmaster knows the seed → can pre-register the right ones.

MethodApproachStrengths
Feature engineeringEntropy, n-gram freq, consonant/vowel ratio → RF/XGBoostInterpretable, fast
BiLSTM + CNN + AttentionCharacter-level sequence classificationNo manual features
LLM fine-tuning (SFT)GPT on domain character sequencesLow false positive rate
LLM in-context learningFew-shot DGA family adaptationZero retrain for new families
GPT embedding + CNNDense vector representation → CNN classifierCombines semantic + structural

Zig SIMD opportunity: Domain entropy computation across batch of 10K domains. Shannon entropy of character distribution — embarrassingly parallel, pure arithmetic.

Fast-Flux Detection

SignalNormal DNSFast-Flux
TTL3600-86400s0-300s
A-record count per query1-410-100+ over time
ASN diversity1-210-50+
Geographic spread1-2 countries20+ countries

Traffic Fingerprinting

  • Flow-level: packet size distribution, inter-arrival times
  • Payload: encrypted channel fingerprints (JA3/JA4 TLS fingerprinting)
  • Behavioral: connection patterns, beacon intervals, sleep jitter

Honeypot/Honeynet

  • Adaptive deception systems (federated honeypots)
  • IoT-specific honeynets (Cowrie SSH, Dionaea SMB, Conpot SCADA)
  • ML classifiers on honeypot log features

Analysis Tools

ToolRoleIntegration
CAPE SandboxDynamic malware analysis (successor to Cuckoo)Auto-unpack, config extract
MISPThreat intelligence sharing (IOCs)API for automated IOC ingestion
TheHiveIncident response case managementIntegrates MISP + Cortex
CortexObservable analysis engine100+ analyzers (geoloc, reputation, sandbox)
ZeekNetwork metadata extractionPassive DNS, protocol logs, DGA detection
SuricataIDS/IPS deep packet inspectionReal-time botnet traffic signatures
WazuhSIEM/EDRHost-based detection, log correlation

SOC stack: Wazuh + TheHive + Cortex + MISP + Zeek/Suricata + CAPE


Game-Theoretic Framing

Botnet as Open Game

     Attacker                    Defender
   ┌──────────┐              ┌──────────────┐
   │ Infect   │──payoffs──→  │ Detect       │
   │ C2 Comm  │              │ Sinkhole     │
   │ Exfil    │              │ Patch        │
   │ Monetize │              │ Takedown     │
   └──────────┘              └──────────────┘

Sequential composition: Infect ; C2 ; Payload ; Exfil
Monoidal product: Phishing ⊗ IoT_exploit ⊗ Supply_chain

Bayesian open games: incomplete information (which hosts compromised?)
Coplay function: defender backward analysis of attacker incentives

Equilibrium Models

ModelStructureApplication
StackelbergLeader-follower (defender commits first)Resource allocation across network segments
FlipItStealth control-flippingMTD timing decisions
Colonel BlottoSimultaneous multi-target allocationMonitoring budget distribution
SIS epidemicSusceptible-Infected-SusceptiblePropagation dynamics + intervention

Nashator Integration

;; Botnet attack-defense as open game via Nashator
(define botnet-game
  (DSL.game "botnet_attack_defense"
    (list (DSL.player "Attacker" +1 4)   ; 4 strategies: infect/c2/exfil/persist
          (DSL.player "Defender" -1 4))   ; 4 strategies: detect/sinkhole/patch/takedown
    ;; Payoff matrix from empirical data
    botnet-payoffs))

;; Compose with capability defense game
(define defended-game
  (DSL.seq botnet-game capability-defense-game))

Capability-Based Defense (OCapN)

Why Botnets Succeed

Ambient authority: process runs as user → inherits ALL user permissions
Compromise one process → lateral movement to everything user can access

Why Capabilities Prevent This

Structural authority: process holds ONLY explicitly granted references
Compromise one process → attacker gets only those specific capabilities
No network scan cap → cannot discover other hosts
No outbound socket cap → cannot phone home to C2
No firmware write cap → cannot persist

Goblins Actor as Hardened Endpoint

(define (^iot-service bcom http-port-cap log-cap)
  "IoT service with ONLY the capabilities it needs.
   Cannot scan network. Cannot write firmware. Cannot phone home."
  (methods
    [(handle-request req)
     ;; Can only use http-port-cap and log-cap
     ;; Even if compromised, attacker gains nothing beyond these
     ($ log-cap write (format "request: ~a" req))
     (serve-response http-port-cap req)]))

GF(3) Triads

reverse-engineering (-1) ⊗ blackhat-go (0) ⊗ botnet-disruption (+1) = 0 ✓
botnet-studies (-1) ⊗ network-forensics (0) ⊗ botnet-disruption (+1) = 0 ✓
botnet-studies (-1) ⊗ captp (0) ⊗ agent-o-rama (+1) = 0 ✓
counter-surveillance (-1) ⊗ botnet-studies (-1) ⊗ nashator (0) → needs +2 = two generators

References

  • IEEE S&P 2025: "Game Theory in Distributed Systems Security" (arXiv:2309.01281)
  • Disclosing.Observer 2026: 22.3M domains sinkholed in 2025
  • Operation Endgame: Phases 1-3 (May 2024 → Nov 2025)
  • Tsundere botnet: Ethereum smart contract C2
  • CAPE Sandbox: capev2.readthedocs.io
  • Spritely Institute: "Heart of Spritely" whitepaper