Skip to content

meltedinhex/analyst-ai-pack / skills/tracking-adversary-infrastructure

tracking-adversary-infrastructure

Verified

Tracks adversary C2 and staging infrastructure by clustering indicators on shared attributes (TLS/JARM, certificate fields, favicon hashes, ASN, registration patterns) to find related hosts. Activates for requests to track adversary infrastructure, cluster C2 servers, or pivot on infrastructure attributes to find related hosts.

Tracking Adversary Infrastructure

When to Use

  • You have a set of suspected C2/staging hosts with attributes (JARM/JA3S, TLS cert fields, favicon hash, ASN, ports, registrar) and want to cluster them to find related infrastructure.
  • You are expanding from a few known indicators to the adversary's broader footprint.

Do not use clustering as confirmed attribution — shared hosting/attributes can be coincidental. Corroborate before attributing.

Prerequisites

  • Host records (CSV/JSON) with shared-attribute fields to cluster on.

Workflow

Step 1: Cluster on shared attributes

python scripts/analyst.py cluster hosts.json --attrs jarm,cert_cn,favicon_hash,asn

Groups hosts that share one or more pivot attributes into clusters, defanging host indicators.

Step 2: Score cluster cohesion

Rank clusters by how many distinct attributes the members share (more shared attributes → stronger relationship).

Step 3: Expand and confirm

Use the strongest shared attributes (e.g., a unique self-signed cert CN or favicon hash) to pivot in internet-scan data for more hosts; corroborate.

Step 4: Document

Record clusters, the shared pivots, and confidence; feed confirmed indicators to detection.

Validation

  • Clustering keys on explicit shared attributes, not loose similarity.
  • Cluster strength reflects the count of distinct shared attributes.
  • Host indicators are defanged in output.

Pitfalls

  • Common CDN/cloud JARM/ASN values creating huge false clusters — exclude generic pivots.
  • Default certificates shared by unrelated servers.
  • Treating one weak shared attribute as a strong link.

References

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall