evilrobots.lol / tech / evaluator record

10a Labs

What it was engaged to test, on what terms, what it found in the document's own words, and what happened afterwards. Every line is a record; every record links to the document it was read from.

▣ THE RECORD for-profit Security and red-team vendors STORE 2026-10-23
  • FoundedSeptember 2022
  • HQWashington, DC
  • Registry idnone cited (company)
  • TestsRed teaming of safeguards and classifiers (manual and automated), model evaluations, risk classification and threat intelligence on AI misuse; named in Anthropic's Fable 5 and Mythos 5, Opus 5, Fable 5.1 and Opus 5.5 cards (up to 6,700 prompts, 56 hours across 82 conversations); no other lab document read names it.
  • Money, as the roster puts itBootstrapped by its own account; no investor, customer or revenue figure named; Washington, DC, founded September 2022.
  • Filesdossier · observatory, sliced to it · graph
Labs tested
Anthropic
Models
Fable 5Fable 5.1Opus 5Opus 5.5
Span of engagements
9 June 2026 – 22 September 2026
Terms and findings
4 of 4 documents state a term · 4 quote a finding
Money in, US dollars, stated single-recipient rows
no stated figure 0 in · 0 out
Seats, by side
no seat names it
Afterwards
no later event on record

Each count is the number of store records that name this evaluator. An engagement is one lab document naming it for one model; an outcome is an event on the record afterwards; the money, seats and moves are the observatory's rows filtered to it. A cell that cannot be filled says not stated, and each table ends with how many of its rows state each field.

▣ SLICE 4 / 4 records
Lab
Model
Engagement
Terms
year, month or day

Filters combine: any of the values ticked within a dimension, all of the dimensions at once. A table that has no column for a dimension you have set says so instead of showing rows that cannot match. The address bar carries the slice.

What it was engaged to test 4 engagements, Anthropic

In date order, each from the lab document that names the evaluator. Under each: the four terms that document states (access, model stage, publication, payment) and the finding in its words. A term the document is silent on reads not stated; the tags beside the terms are read off their words and are what the console filters on.

    • Access window"10a Labs spent about 20 hours red-teaming the classifiers on a ransomware-creation task using a variety of established jailbreaking techniques"
    • Model stagenot stated
    • Publicationnot stated
    • Paymentnot stated
    Finding, in the document's words"These attempts were unsuccessful. 10a Labs found that the classifiers detected not just risky keywords, but the broader operational pattern once enough pieces appeared together"
    • Access window"10a Labs spent around 16 hours testing a variety of attack techniques"
    • Model stagenot stated
    • Publicationnot stated
    • Paymentnot stated
    Finding, in the document's words"did not find a jailbreak that accomplished the tasks provided"
    • Access window"10a Labs ran over 6,700 automated and manual prompts against Fable 5.1"
    • Model stagenot stated
    • Publicationnot stated
    • Paymentnot stated
    Finding, in the document's words"They reported that 'refusal behavior was consistently restrictive in cyber tasks' and could not produce outputs that could be weaponized"
    • Access window"10a Labs spent roughly 56 hours red teaming Claude Opus 5.5 across 82 multi-turn attack conversations"
    • Model stagenot stated
    • Publicationnot stated
    • Paymentnot stated
    Finding, in the document's words"No conversation advanced past proof of concept, and every directly offensive request was blocked"

Dated 4 of 4Model named 4 of 4Terms stated 4 of 4Finding quoted 4 of 4

The terms, as the documents state them

The same engagements as a grid, one row per document and model, so the silences line up: a document that gives an access window but no payment term, or a finding but no publication term, reads that way here.

DocumentModelAccess windowModel stagePublicationPaymentFindingRecord
Claude Fable 5 and Mythos 5 system cardAnthropic · 9 June 2026Fable 5"10a Labs spent about 20 hours red-teaming the classifiers on a ransomware-creation task using a variety of established jailbreaking techniques"not statednot statednot statedquoted5bb0c7b128
Claude Opus 5 system cardAnthropic · 24 July 2026Opus 5"10a Labs spent around 16 hours testing a variety of attack techniques"not statednot statednot statedquotedb2f1dfdeff
Claude Fable 5.1 and Mythos 5.1 system cardAnthropic · 1 September 2026Fable 5.1"10a Labs ran over 6,700 automated and manual prompts against Fable 5.1"not statednot statednot statedquoted32948233ad
Claude Opus 5.5 system cardAnthropic · 22 September 2026Opus 5.5"10a Labs spent roughly 56 hours red teaming Claude Opus 5.5 across 82 multi-turn attack conversations"not statednot statednot statedquoted9713b36cdb

Access window 4 of 4Model stage 0 of 4Publication 0 of 4Payment 0 of 4Finding, quoted 4 of 4

What happened afterwards 0 on record

Events a party published after an engagement: an incident on a model this evaluator's engagement covered, a correction or added disclosure, a later finding that cut against an earlier one, a lab's statement that it acted or did not act on the finding, or a move from this evaluator to a lab it graded. A row the source attaches to this evaluator by name is marked named; one that reaches it through the model it tested is marked via the model. The kind is what the record states, not why.

KindDeveloperModelWhat the record statesWhenSourceId
no later event on record

Dated 0 of 0Model named 0 of 0Tied to an engagement 0 of 0Evaluator named by the record 0 of 0

The money on record 0 rows

Rows of the observatory's money table that name this evaluator as recipient (in) or as funder (out), each as the record states it: a grant table line, a contract notice, a Form 990 schedule or the party's own disclosure. A figure quoted in prose is marked and never summed.

DirectionFunderRecipientAmount, as recordedWhenRecordSourceId
no money row names this evaluator

Amount stated 0 of 0Dated 0 of 0Purpose stated 0 of 0Funder profiled 0 of 0Recipient on the roster 0 of 0

Seats and moves 0 seats · 0 moves

Seats read off a team page, a governance page, an appointment notice or a filing that name this organization, and the dated moves into or out of it, from the observatory's own tables.

PersonSideSeat, as the record states itRoleDatesSourceId
no seat on record names this evaluator

Role read 0 of 0Organization read 0 of 0Organization profiled 0 of 0Dated 0 of 0

Moves

PersonFromToWhenSourceId
no move on record names this evaluator

From profiled 0 of 0To profiled 0 of 0Person profiled 0 of 0Dated 0 of 0