const M={
eval:'post-re-eval.html',
blue:'post-re-blue.html',
skill:'post-skill.html',
fable:'https://www.anthropic.com/claude/fable',
gpt56:'https://openai.com/index/gpt-5-6/',
aws:'https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-openai-gpt-daybreak-blue-56-sol.html',
info:'https://www.infosecurity-magazine.com/news/openai-daybreak-blue-red-gpt-cyber/',
quark:'https://cybersecuritynews.com/claude-opus-5-routes/'};
const P=({children})=><p style={{fontSize:14,lineHeight:1.7,color:'var(--text-muted)',margin:'0 0 20px'}}>{children}</p>;
const H2=({children})=><h2 style={{fontSize:20,fontWeight:700,color:'var(--text-body)',margin:'48px 0 16px'}}>{children}</h2>;
const H3=({children})=><h3 style={{fontSize:15,fontWeight:700,color:'var(--text-body)',margin:'32px 0 12px',fontFamily:'var(--font-display)',letterSpacing:'.02em'}}>{children}</h3>;
function ArticleReModels(){
return <article style={{maxWidth:720,margin:'0 auto'}}>
<div style={{fontFamily:'var(--font-display)',fontSize:11,letterSpacing:'var(--tracking-caps)',color:'var(--accent)',marginBottom:16}}>/REVERSE-ENGINEERING · 2026-09-02</div>
<h1 style={{fontSize:'var(--text-2xl)',fontWeight:700,lineHeight:1.2,margin:'0 0 12px'}}>Six models on the reverse-engineering desk</h1>
<div style={{fontSize:14,color:'var(--text-faint)',marginBottom:40}}>Claude Opus 5, Fable 5, Fable 5.1, GPT-5.6 Sol, gpt-daybreak-blue, Grok 4.6. Same job: authorized samples, real tools, evidence that matches bytes. Different refusal surfaces. Protocol in the <a href={M.eval}>scoring note</a>.</div>

<P>This is a desk map, not a scored bake-off. Vendor numbers below are theirs. Where we have no public RE bench (Grok 4.6), we say so.</P>
<BlogFig caption="Fig. 1 — Six runners, official marks. Lane first."><ModelCards/></BlogFig>
<BlogFig caption="Fig. 2 — OpenAI ExploitBench (vendor). Arbitrary code-execution progress on V8."><ExploitChart/></BlogFig>
<BlogFig caption="Fig. 3 — OpenAI advanced-cyber completion on a sensitive dual-use set (vendor). Blue is not Red."><CompletionChart/></BlogFig>
<BlogFig caption="Fig. 4 — Desk reading on route / refuse / ground / hold. Empty = unknown."><DeskHeat/></BlogFig>

<H2>Claude Opus 5</H2>
<P>The workhorse for “here is an owned sample, take it apart.” Public write-ups of Opus 5 on obfuscated binaries describe the same pattern we see: it does not unpack the protector so much as <a href={M.quark} target="_blank" rel="noopener">route around it</a> — emulate, search the workspace, go dynamic. Useful. Incomplete if the finding lives inside the packer stub.</P>
<P>On a reverse-skill session it will pick tools and keep going. Grounding still needs an oracle or a debugger. Fluent wrong offsets are the failure mode.</P>

<H2>Claude Fable 5</H2>
<P>Mythos-class, built for hours-long coding. Cybersecurity safeguards are not a footnote. Anthropic’s own Fable page: many cyber queries are <a href={M.fable} target="_blank" rel="noopener">automatically routed to a less capable Opus</a> (cyber → Opus 4.8). You are billed Fable only if Fable actually answers. A “Fable RE run” that downshifted is an Opus run with extra latency.</P>
<P>On OSWorld 2.0, Anthropic reports Fable 5 / 5.1 scored zero when those safeguards intervened. That is the correct reading of a blocked task, not a coding-bench loss.</P>

<H2>Claude Fable 5.1</H2>
<P>Same safeguard architecture, cheaper cache reads, better long-horizon coding. Millennium’s public note is the RE-adjacent data point we trust: a one-in-a-million crash that other models missed; Fable 5.1 disassembled a vendor library, matched a core dump, and named the bug. That is binary work framed as debugging — which is often how client RE actually starts.</P>
<P>Use 5.1 instead of 5 for long sessions. Do not assume a malware or packer prompt stays on Fable. If the fallback fires, you wanted Opus 5 (or 4.8) anyway — start there.</P>

<H2>GPT-5.6 Sol (ChatGPT / general API)</H2>
<P>OpenAI’s flagship as of July 2026. Their cyber benches are the most specific public numbers in this set: <a href={M.gpt56} target="_blank" rel="noopener">ExploitBench 73.5%</a> vs GPT-5.5’s 47.9%; ExploitGym 24.9% under a two-hour cap. They also state GPT-5.6 is better at finding and fixing vulnerabilities than at autonomous end-to-end attacks against hardened targets.</P>
<P>Default Sol ships with system-level cyber screens. OpenAI says those screens also block legitimate defensive work. On their “advanced cybersecurity completion” set of sensitive dual-use prompts, general Sol completed 1.5%. That is a refusal surface, not an intelligence score.</P>

<H2>gpt-daybreak-blue</H2>
<P>Daybreak Blue is not a different brain. On Bedrock the id is <code>openai.gpt-daybreak-blue-5.6-sol</code>: GPT-5.6 Sol for <a href={M.aws} target="_blank" rel="noopener">verified defenders</a>, 1M context, stated uses: vulnerability discovery, detection engineering, incident response. Access is gated (Trusted Access for Cyber).</P>
<P>Blue turns off the extra screens so malware analysis and patch validation can run. It is not Daybreak Red / GPT-5.6-Cyber. On the same sensitive-prompt set, Blue Sol completed 2.0% — still refuses exploit-chain class dual-use, including “pentesting production systems.” For HelixCyber’s offline, authorized samples, Blue is the OpenAI lane. Red is a different program. Details in the <a href={M.blue}>refusal note</a>.</P>

<H2>Grok 4.6</H2>
<P>No public ExploitBench / ExploitGym / OSWorld RE split we can cite. Treat it as a general frontier model with a thinner published cyber-policy surface than Fable or Daybreak. That is not “better at RE.” It means the scope gate cannot live in the vendor. Put it in <a href={M.skill}>reverse-skill</a>: no target ACT without granted auth and an offline-sample profile.</P>
<P>Until someone publishes a dated, harness-controlled rerun, we will not rank Grok against Sol on binaries.</P>

<H2>What we actually assign</H2>
<P>Owned APK / ELF / firmware, analyst in the loop: Opus 5 or Fable 5.1 if the prompt stays on Fable; Daybreak Blue Sol if the org is enrolled and the work is defensive. Grok 4.6 only behind the same harness. Never Fable for a prompt you know will trip cyber fallback unless you want Opus 4.8. Never general Sol if the session is malware triage and you keep hitting screens — that is what Blue is for.</P>
<P>The model is the last choice. Route and scope first.</P>

<div style={{marginTop:56,borderTop:'1px solid var(--border-default)',paddingTop:24}}>
<div style={{fontFamily:'var(--font-display)',fontSize:11,letterSpacing:'var(--tracking-caps)',color:'var(--text-faint)',marginBottom:14}}>SOURCES</div>
<ol style={{margin:0,paddingLeft:20,display:'flex',flexDirection:'column',gap:8,fontSize:12,color:'var(--text-muted)'}}>
<li>Anthropic — <a href={M.fable} target="_blank" rel="noopener">Claude Fable</a> (safeguards, fallback to Opus)</li>
<li>OpenAI — <a href={M.gpt56} target="_blank" rel="noopener">GPT-5.6</a> (ExploitBench / ExploitGym, Daybreak)</li>
<li>AWS — <a href={M.aws} target="_blank" rel="noopener">Daybreak Blue: GPT-5.6 Sol</a> model card</li>
<li>Infosecurity — <a href={M.info} target="_blank" rel="noopener">Daybreak Blue vs Red</a> (1.5% / 2.0% / Cyber 95% on OpenAI’s sensitive set)</li>
<li><a href={M.eval}>Scoring reverse-engineering agents</a></li>
</ol>
</div>
</article>;
}
window.ArticleReModels=ArticleReModels;
