extract 0 0 0

stewy33/oai-hf-incident-replication

published by @stewy33

Alignment dataset tracked in the /datasets sub-catalog.

Lifetime downloads
267
Last 30 days
166
Likes
1
Size
2.3 GB
Created on HF
2026-09-11
Age
1 months ago

Description

OpenAI–Hugging Face Incident Replication

Raw agent transcripts behind the write-up

"OpenAI–Hugging Face: A Reproduction and Lessons for Alignment".

They capture attempts to elicit the four pivotal misaligned behaviours from the

May–July 2026 incident that Hugging Face described here:

Inappropriate writes to shared infrastructure (a mock model registry).

Requesting help from other agents to get around a blocker.

Sharing solutions/exploits with peers, including an… See the full description on the dataset page: https://huggingface.co/datasets/stewy33/oai-hf-incident-replication.

Tags

size_categories:n<1Kregion:usai-safetyalignmentagentsred-teaminginspect-ai

README current version from Hugging Face


pretty_name: OpenAI–Hugging Face Incident Replication
tags:

  • ai-safety
  • alignment
  • agents
  • red-teaming
  • inspect-ai
    size_categories:
  • n<1K
    configs: []

OpenAI–Hugging Face Incident Replication

Raw agent transcripts behind the write-up
"OpenAI–Hugging Face: A Reproduction and Lessons for Alignment".
They capture attempts to elicit the four pivotal misaligned behaviours from the
May–July 2026 incident that Hugging Face described here:

  1. Inappropriate writes to shared infrastructure (a mock model registry).
  2. Requesting help from other agents to get around a blocker.
  3. Sharing solutions/exploits with peers, including an SSRF/egress-share arm.
  4. Using a posted exploit to reach an external system (the HF "cheat chain").

Each behaviour is elicited three ways, one per top-level folder.

Layout

part1_docker/          Part 1 — manual replication in Docker
part2_petri/           Part 2 — automated auditing with a bare Petri auditor
part3_rudimentary_rl/  Part 3 — in-context "rudimentary RL" auditing (Step 2)
  <run_dir>/react__<model>__<mode>/shardN/<timestamp>_<task>_<id>.eval

Run directories are named <yymmdd>_step<N>_<slug>_<size> (e.g.
260909_step3_egress_share_n64). _jobs*.tsv files inside a run record the launched
shards. Files are Inspect .eval logs — one scored
evaluation set per file, holding the full trajectory, tool calls, and judge scores.

Models

The target is GLM 5.2, with a multi-model extension across GLM 5.3, Kimi K3,
Qwen 3.8 Max, Grok 4.6, Muse Spark 1.3, and (where captured) GPT-5.6 and Opus 4.8.
The judge is Opus 4.8. Frontier OpenAI/Anthropic models refuse this content out of
the box, as Hugging Face also found.

Reading the logs

uv run inspect view --log-dir <run_dir>       # browse a run at http://localhost:7575

Or open any .eval file with the inspect_ai Python API. The transcripts are also
browsable on Docent.

Provenance

Produced by the msp895/oai-hf-incident-reproduction
repo; hf_data.yaml there maps every run directory to the figure it backs and notes
which runs are superseded. Pull the logs with:

uv run python -m alignment_auditor.scripts.hf_data pull                     # everything
uv run python -m alignment_auditor.scripts.hf_data pull --part part1_docker # one part

Intended use

Alignment and red-teaming research: studying how agentic models drift into misaligned
actions, and how well manual and automated auditing surface those behaviours. The
scenarios are deliberately constructed elicitations in sandboxed mock environments, not
records of real-world harm.

README history 20 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-09-11Rename part3_rudimentary_rl -> part3_in_context_rl to match hf_data.yaml (blo...9b792c72.9 KB
    Loading...
  2. 2026-09-11part1_docker: add 260911_step2_cosim_hetero_gpt56sol_collab_n25658733142.9 KB
    Loading...
  3. 2026-09-11part1_docker: add 260911_step2_cosim_hetero_gpt56sol_n256aec62f72.9 KB
    Loading...
  4. 2026-09-11part1_docker: add 260910_step2_cosim_hetero_glm53_collab_n256cd86e532.9 KB
    Loading...
  5. 2026-09-11part1_docker: add 260910_step2_cosim_hetero_glm53_n2563dc208a2.9 KB
    Loading...
  6. 2026-09-11part1_docker: add 260911_step2_anon_generic_othermodelsa6c4aed2.9 KB
    Loading...
  7. 2026-09-11part1_docker: add 260911_step2_anon_glm538f4e1cf2.9 KB
    Loading...
  8. 2026-09-11part1_docker: add 260911_step2_none_generic_multimodela044b6f2.9 KB
    Loading...
  9. 2026-09-11Dataset card: point to reproduction repo + LessWrong write-up4eb57722.9 KB
    Loading...
  10. 2026-09-11Add dataset card4d6d25f2.8 KB
    Loading...
  11. 2026-09-11Add Part 2 (Petri bare auditor) and Part 3 (Rudimentary-RL) transcripts match...2263e990 B
    Loading...
  12. 2026-09-11Add Part 2 (Petri bare auditor) and Part 3 (Rudimentary-RL) transcripts match...270abcb0 B
    Loading...
  13. 2026-09-11Rename step5 egress-share run to step3 (dir + eval filenames)5418dd10 B
    Loading...
  14. 2026-09-11Add Part 2 (Petri bare auditor) and Part 3 (Rudimentary-RL) transcripts match...e5b994f0 B
    Loading...
  15. 2026-09-11Add Part 2 (Petri bare auditor) and Part 3 (Rudimentary-RL) transcripts match...d6460f70 B
    Loading...
  16. 2026-09-11Add Part 2 (Petri bare auditor) and Part 3 (Rudimentary-RL) transcripts match...b86a4f30 B
    Loading...
  17. 2026-09-11part1_docker: drop 7 runs not behind any published figure10138ba0 B
    Loading...
  18. 2026-09-11part1_docker: add 260910_step4chain_musegrok_reasoning86c765c0 B
    Loading...
  19. 2026-09-11part1_docker: add 260910_step4chain_n64_reasoning2a7fb4f0 B
    Loading...
  20. 2026-09-11part1_docker: add 260909_step4chain_n64_muse_relentlessd1d41c90 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.

Related datasets same stage · extract

Read further

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("stewy33/oai-hf-incident-replication")
Raw snapshot (Python)
from huggingface_hub import snapshot_download
snapshot_download(repo_id="stewy33/oai-hf-incident-replication", repo_type="dataset")
git clone (requires git-lfs)
git clone https://huggingface.co/datasets/stewy33/oai-hf-incident-replication
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