re-attribution

Attributes cyber threat activity using diamond model analysis, infrastructure graphing, and confidence grading.

64|9|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/dslsdzc/rev-skills --skill re-attribution-dslsdzc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: re-attribution
Source: https://github.com/dslsdzc/rev-skills/tree/main/.claude/skills/re-attribution
Command: npx skills add https://github.com/dslsdzc/rev-skills --skill re-attribution-dslsdzc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-whois, networkx, and includes references (resource) components.

What problem does it solve? Determining who is behind a cyber attack is error-prone: shared infrastructure, commodity tooling, and false flags routinely cause misattribution. This Skill provides a rigorous methodology for threat attribution that grades evidence strength, prevents overclaiming, and produces defensible, confidence-rated conclusions. ## Core Features & Use Cases - Diamond Model Analysis: Maps adversary, capability, infrastructure, and victim corners to identify attribution gaps and structure multi-event correlation. - Infrastructure Graphing: Clusters C2 domains, IPs, and certificates using whois, certificate transparency (crt.sh), dnsx, and networkx to distinguish control-plane from shared-plane evidence. - Confidence Grading & Reporting: Applies a three-tier confidence scale (low/medium/high) with strict wording rules, counter-evidence tracking, and a sanitized report template. - Use Case: Given several intrusion events sharing C2 domains, correlate registration data, certificate reuse, and unique malware strings to determine whether they form one campaign and issue a "suspected same activity" statement with documented evidence chains. ## Quick Start Use the re-attribution skill to analyze these C2 domains and malware samples, build an infrastructure graph, and produce a confidence-graded attribution report.

Frequently Asked Questions about re-attribution

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I attribute a cyber attack to a threat actor?▼

Start with the diamond model: map known information across victim, infrastructure, capability, and adversary corners. You need at least two corners before making any attribution claim, then cross-correlate independent evidence types like registration data, certificates, and unique code features.

What tools are used for threat infrastructure analysis?▼

The workflow uses whois for registration data, crt.sh for certificate transparency lookups, dnsx for DNS enumeration, and networkx for graph clustering of related domains and IPs. MISP supports intelligence correlation and sharing.

Why is shared C2 infrastructure not enough for attribution?▼

C2 servers and domains are frequently sold, rented, or hijacked, so shared infrastructure only proves shared resources, not shared operators. Only control-plane evidence like registration emails, certificate private keys, or unique configurations counts as strong attribution evidence.

How are attribution confidence levels determined?▼

Low confidence means one weak evidence type; medium requires two independent evidence types or one strong unique indicator; high requires three or more evidence types with consistent timelines and no contradictions. Any counter-evidence forces a downgrade and must be documented.

Can threat attribution results be used as legal evidence?▼

No. Intelligence attribution is probabilistic and graded, while criminal evidence requires proof beyond reasonable doubt with chain of custody. The output is an intelligence judgment and must be labeled with its limitations if handed to legal proceedings.

When should I not perform organization-level attribution?▼

Do not attribute when you only have a single corner of evidence, such as one malware sample or one domain. In that case, output an intelligence-lead level deliverable with IOC lists and feature descriptions instead of naming any organization.