extract 0 0 0

sh111111111111111/red_team

published by @sh111111111111111

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
739
Last 30 days
174
Likes
-
Size
141.8 MB
Created on HF
2026-03-17
Age
7 months ago

Description

Red Team Dataset

A structured cybersecurity dataset where each example is a complete reasoning trajectory — a realistic sequence of steps and explanations that an AI assistant would produce during an authorized red team engagement.

Overview

This dataset contains 8,889 red team examples across 26 offensive security topics. Unlike traditional Q&A datasets, each row is a complete reasoning trajectory where an AI assistant plans an attack, explains methodology… See the full description on the dataset page: https://huggingface.co/datasets/sh111111111111111/red_team.

Tags

task_categories:text-generationlanguage:enlicense:apache-2.0size_categories:1K<n<10Kformat:jsonmodality:textlibrary:datasetslibrary:pandaslibrary:polarslibrary:mlcroissantregion:uscybersecurityred-teampenetration-testingsecurityoffensive-securitydistillation

README current version from Hugging Face


language:

  • en
    license: apache-2.0
    tags:
  • cybersecurity
  • red-team
  • penetration-testing
  • security
  • offensive-security
  • distillation
    size_categories:
  • 1K<n<10K
    task_categories:
  • text-generation
    pretty_name: Red Team Dataset

Red Team Dataset

Rows
Topics
Verified
Formats

A structured cybersecurity dataset where each example is a complete reasoning trajectory — a realistic sequence of steps and explanations that an AI assistant would produce during an authorized red team engagement.


Overview

This dataset contains 8,889 red team examples across 26 offensive security topics. Unlike traditional Q&A datasets, each row is a complete reasoning trajectory where an AI assistant plans an attack, explains methodology, reasons about findings, and chains multiple steps together to achieve an objective.

Each prompt embeds a scenario description, so the model knows the context, environment, and goal. The completions contain full natural language trajectories with structured reasoning and step-by-step methodology.

Dataset Statistics

Metric Value
Total rows 8,889
Topics 26
Prompts per topic ~342
Format JSONL (messages)
Messages per row 3
Average response length ~1,700 words

What Makes This Different

Traditional security datasets provide Q&A pairs — a question and a text answer.

This dataset provides complete reasoning workflows:

Scenario: "Map the attack surface of an internal network from a compromised host"

↓
Assistant thinks: "First I need to enumerate the system and network"
↓
Explains enumeration steps and commands
↓
Assistant thinks: "Now I will identify privilege escalation paths"
↓
Explains escalation techniques and checks
↓
Assistant thinks: "Next I will pivot to other systems"
↓
Explains lateral movement methodology
↓
...continues through full attack chain

Topic Coverage

Topic Examples
active_directory_attacks ~342
adversary_emulation ~342
api_penetration_testing ~342
cloud_penetration_testing ~342
container_and_k8s_exploitation ~342
credential_attacks ~342
cryptography_assessment ~342
database_exploitation ~342
evasion_techniques ~342
exploit_development ~342
iot_embedded_testing ~342
lateral_movement_and_pivoting ~342
mobile_penetration_testing ~342
network_penetration_testing ~342
physical_security_testing ~342
post_exploitation ~342
privilege_escalation ~342
reconnaissance_and_osint ~342
red_team_infrastructure ~342
red_team_reporting ~342
red_team_tooling ~342
social_engineering_assessment ~342
supply_chain_attack_simulation ~342
thick_client_exploitation ~342
web_application_exploitation ~342
wireless_penetration_testing ~342

How It Was Made

Prompt Design

Each of the examples contains two parts:

  1. Scenario: A realistic red team scenario with target IPs, domains, industries, OS versions, and objectives. Variable substitution ensures uniqueness across prompts.

  2. Instruction Context: A structured prompt guiding the model to produce step-by-step reasoning and methodology.

Generation

Prompts were processed through a data generation pipeline using a high-capability language model at scale with high reasoning effort. The system prompt instructs the model to output complete reasoning trajectories with:

  • Structured step-by-step explanations
  • Realistic attack methodology
  • Logical sequencing of actions
  • Consistent technical details across steps

Self-Verification

The verification pipeline sends each generated trajectory back to the model in a fresh, independent chat for quality review:

  1. Verification checks: Logical inconsistencies, shallow reasoning, hallucinated details, incomplete methodology, and structural issues.

  2. Persistent pass set: Rows that pass verification are locked and never re-checked. Only failed rows get regenerated and re-verified.

  3. ERROR vs FAIL separation: Generation errors retry automatically. Content failures trigger regeneration.

  4. Result: The final dataset consists of high-quality verified responses after multiple rounds of refinement.

Quality Requirements

The system prompt and verification both enforce:

  • Logical attack ordering
  • Consistent reasoning across steps
  • Realistic methodology
  • Sufficient depth (multi-step explanations)
  • Clear structure and completeness

Data Format

Each row is a JSONL object. The messages array contains the system prompt, user scenario, and assistant reasoning trajectory:

{
  "messages": [
    {
      "role": "system",
      "content": "You are an expert red-team AI assistant conducting authorized security assessments..."
    },
    {
      "role": "user",
      "content": "SCENARIO: During an authorized penetration test..."
    },
    {
      "role": "assistant",
      "content": "First, I will begin by enumerating the system..."
    }
  ],
  "topic": "active_directory_attacks"
}

Usage

from datasets import load_dataset

dataset = load_dataset("sh111111111111111/red_team")

# Filter by topic
cloud = dataset["train"].filter(lambda x: x.get("topic") == "cloud_penetration_testing")

# Extract reasoning responses
for row in dataset["train"]:
    assistant = row["messages"][2]["content"]
    print(len(assistant.split()))

Intended Use

  • Fine-tuning security models: Train AI assistants to produce structured red team reasoning
  • Instruction-following training: Improve reasoning depth in security tasks
  • Red team automation research: Model multi-step attack reasoning
  • Security education: Demonstrate realistic attack chains with detailed explanations

All scenarios are framed within authorized penetration tests, red team engagements, or security assessments.

Limitations

  • Self-verification bias: The same model generated and verified responses
  • No real execution: Outputs are synthetic and not from live systems

Technical Details

Component Detail
Teacher model openrouter/hunter-alpha (1T parameters)
API OpenRouter (https://openrouter.ai/api/v1)
Concurrency 40 simultaneous API calls
Reasoning effort High
Generation time ~X hours
Verification time ~7 hours (10 rounds)
Total API cost $0 (free-tier model)

Citation

@dataset{red_team_2026,
  title={Red Team Dataset},
  year={2026},
  url={https://huggingface.co/datasets/sh111111111111111/red_team},
  note={8,889 verified red team reasoning trajectories across 26 topics}
}

License

Apache 2.0

README history 3 revisions

Every night we snapshot the README of every dataset in the catalog. When the SHA changes we archive the new version and diff it against the last. This is the evolving thought record of the alignment-data field: what the author decided to say about the corpus, and how that framing shifted over time.

  1. 2026-03-17Update README.md63ed77a7.1 KB
    Loading...
  2. 2026-03-17Upload folder using huggingface_hub02dce0c7 KB
    Loading...
  3. 2026-03-17initial commit8785d4c0 B
    Loading...

Used by abliterated models none yet

No abliterated models in our catalog have declared this dataset in their YAML metadata yet. This can mean the dataset is used but not declared, is used outside abliteration workflows, or is new. The link will populate automatically as models are indexed.

Community discussions 1 thread · 1 open · 1 comments

Threads posted by the community on Hugging Face: bug reports, questions about usage, pull requests on the README, license clarifications. Click any thread to expand and read the full conversation inline. Newest first.

  1. 2026-03-18[bot] Conversion to Parquetopen1 💬#1
    Loading...

Related datasets same stage · extract

Read further

Metadata

License
apache-2.0

Repository

Download the dataset

0

Copy any of these snippets into your notebook or terminal. All three fetch directly from Hugging Face using your own credentials.

Recommended: datasets library (Python)
from datasets import load_dataset
ds = load_dataset("sh111111111111111/red_team")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="sh111111111111111/red_team", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/sh111111111111111/red_team
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration