How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/smartworldarafath/rea_skill --skill offensive-c2-frameworksBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
C2 Traffic Analysis & Network Detection (offensive-c2-frameworks)
Authorization & Scope Notice: This skill is part of the REA_Skill + claude-red Unified Security & Reverse Engineering Suite. It is designed strictly for authorized security assessments, defensive architecture reviews, vulnerability triage, bug bounty verification, and remediation engineering on software, infrastructure, and assets you own or have explicit permission to test.
Overview
Network threat hunting and detection engineering for command-and-control (C2) channels covering JA3/JA4 TLS fingerprinting, periodic beacon jitter statistical analysis, DNS tunneling entropy detection, and egress proxy inspection.
Operational Workflow
- Surface & Architecture Inventory
- Identify all entrypoints, trust boundaries, parsers, and configuration files relevant to C2 Traffic Analysis & Network Detection (
forensicsdomain). - Combine static code/binary inspection (via REA MCP tools,
rg, AST analysis, or decompilation) with runtime configuration verification.
- Hypothesis & Vulnerability Verification
- Test each security invariant systematically against known CWE and OWASP patterns.
- Record concrete evidence: affected file/procedure, line numbers or binary offsets, request/response trace, and root cause.
- Impact & Reachability Triage
- Evaluate whether the issue is reachable across trust boundaries, whether defense-in-depth controls mitigate it, and compute an accurate CVSS v3.1 / v4.0 score.
- Remediation & Regression Verification
- Implement or provide production-ready, copy-pasteable remediation code.
- Write an automated regression test or verification command to prove the flaw is resolved with 0 regressions.
Audit & Verification Checklist
| Phase | Check | Verification Method | Expected Secure State |
|---|---|---|---|
| 1. Discovery | Enumerate all forensics surfaces and dependencies | Source search / REA binary & bundle inspection | Complete inventory of trust boundaries |
| 2. Input & State | Validate parser behavior, type safety, and state transitions | Boundary testing & static taint analysis | Strict schema validation and invariant checks |
| 3. Auth & Isolation | Verify caller identity, tenant isolation, and least privilege | Horizontal/vertical privilege matrix check | Explicit deny-by-default enforcement |
| 4. Defense-in-Depth | Inspect secondary controls, logging, and compiler/runtime flags | Config & header/binary flag audit | Full hardening and telemetry enabled |
| 5. Remediation | Apply fix and execute automated regression test | npm test / toolchain build & test suite | 0 vulnerabilities, 0 build errors |
Integration with REA MCP & Tooling
- Static & Binary Analysis: Pair with
rea-universal-orchestrator,rea-binary-disassembly,rea-web-bundle-recovery, orrea-mobile-app-recoverywhen source code is unavailable. - Interactive Scoping: Invoke
/rea-grill-mebefore large-scale assessments to clarify scope, target environments, and acceptance criteria. - Reporting: Pair with
offensive-reportingto format findings with CVSS vectors, CWE mappings, and remediation patches.