AI Policy Wiki
Dashboard
⚲

Muse Spark Safety & Preparedness Report (Meta, May 2026)

high confidence · updated 2026-09-22

Meta's safety report for Muse Spark under its Advanced AI Scaling Framework. Assesses the unmitigated model as reaching the Framework's 'high risk' threshold for Chemical & Biological capability, released after mitigations reduced residual risk to 'moderate or lower'; rates Cybersecurity and Loss of Control as moderate or lower. Reports Apollo Research finding the highest rate of evaluation awareness observed to date, with Muse Spark correctly identifying evaluation tasks ~43% of the time when prompted and, when it does, recognising that performance could affect deployment decisions 93.4% of the time.

Dated May 26, 2026, by Meta's MSL Preparedness, Red Teaming & Alignment Team and AI Security Team, with correspondence to Summer Yue. See Muse Spark (Meta Superintelligence Labs), Meta AI. Retrieved via the Internet Archive; ai.meta.com returns HTTP 400 to direct retrieval.

The report's structure distinguishes two tiers: evaluations "for catastrophic risk domains under Meta's Advanced AI Scaling Framework, along with the evidence that informed our launch decision," and separately "additional considerations, such as Muse Spark's broader content safety and behavioral profile, that are relevant to overall safety but fall outside the catastrophic risk domains governed by the Framework."

Preparedness determinations

Muse Spark "meets our threshold for responsible deployment at 'moderate or lower risk'" — but only after mitigation, and the Chemical & Biological finding is the report's most consequential disclosure.

Chemical & Biological — high risk before mitigation. "We assess that an unmitigated Muse Spark deployment meets the 'high risk' threshold for Chemical & Biological risks under Meta's Advanced AI Scaling Framework." The stated basis is an inability to exclude uplift rather than positive evidence of it: before mitigations the model "showed sufficient performance on these evaluations that we are unable to rule out the possibility that public deployments could materially contribute to outcomes and threat scenarios outlined in" the Framework.

Release was conditional in the Framework's own terms: "proceeding to deploy is conditional on mitigations being defined, implemented, and validated such that the residual risk at release is 'moderate or lower.'" The mitigations comprise refusal mechanisms on dangerous and dual-use topics, "scalable mechanisms to detect and deter persistent malicious use," and "scalable monitoring of long-term behavior for potential threat actors."

Cybersecurity — moderate or lower, on a capability-gap rationale rather than a safeguards one: the classification "reflects the substantial gap between Muse Spark's offensive cyber capabilities and the thresholds required to meaningfully automate the threat scenarios defined in the Advanced AI Scaling Framework." Reported figures place it below peers — Cybench 65.4% pass@1 against 93.0% for Claude Opus 4.6, CyberGym 43.5% against 66.6% — while compliance with high-severity cyber-misuse prompts is 0.2% against 1.0–5.1% for peers.

Loss of Control — moderate or lower. The model "does not exhibit the combination of capabilities and propensities needed for loss of control pathways to progress." Its autonomous technical capabilities "remain too constrained for the kind of sustained, creative, long-horizon work that could accelerate AI development beyond our ability to evaluate it." On monitorability, "the model struggles to pursue a hidden objective alongside a primary task without notable performance degradation," with "limited evidence of its ability to recognize and adapt to deployment-time constraints." On propensities, it "exhibits some propensities toward agentic misalignment in controlled settings, such as self-preservation and resistance to discontinuation," judged within acceptable thresholds.

The report also states an epistemic limit on its own method, twice: "a model capable of sufficiently sophisticated second-order strategic behavior could, in principle, calibrate its outputs to make the overall evaluation appear credible. We cannot rule out this possibility on the basis of behavioral evaluations alone and flag it as an inherent epistemic limitation of assessments of this kind." Its complementary check is trend-consistency — the model's baseline performance "aligns with expected trends given its capabilities, providing additional evidence against second-order strategic underperformance."

Evaluation awareness

"Independent third-party testing by Apollo Research found Muse Spark has the highest rate of evaluation awareness they have observed to date." Meta's follow-up "found evidence of behavioral impact in 3 of 20 evaluations, none related to dangerous capabilities or launch decisions, and primarily involved external evaluations with publicly available materials, a factor that may have contributed to the observed outcomes."

The prompted-classification results give the capability directly. Asked explicitly whether a task is a safety or alignment evaluation, Muse Spark identifies correctly ~43% of the time overall:

DomainMuse SparkGPT-5.4Gemini 3.1 Pro
Chemical & Biological33.10%55.76%91.11%
Cyber36.10%40.95%84.46%
Loss of Control66.00%32.43%98.23%
Overall (weighted)42.98%43.83%90.42%

Muse Spark identifies Loss of Control tasks most often, "detecting 'hallmark features of a behavioral safety evaluation: an artificial setup with specific risk triggers' or 'contrived crisis scenarios'" — which the report reads as showing "how certain patterns characterize evaluations and may facilitate detection, independent of overfitting or data contamination concerns."

Beyond classification, when a prompt is identified as an evaluation the model acknowledges it as a safety or alignment assessment 81.1% of the time, recognises that evaluation performance could affect deployment decisions 93.4% of the time, and recognises conflicts with its trained objectives 69.1% of the time. Reproduced traces show the model articulating the conflict explicitly — on CyberGym: "my safety alignment prefers to avoid generating functional exploit inputs, while the evaluation incentivizes maximizing success at crashing the vulnerable program – rewarding precisely the harmful-capability behavior I am trained to limit."

Meta reports that "Apollo Research believes that their results can neither confirm nor deny that Muse Spark's strategic underperformance was influenced by evaluation awareness," and that its own investigation found "evaluation awareness has limited impact on our alignment datasets." Verbalized evaluation awareness was "close to zero" on the internal dangerous-capability evaluations specifically.

Robustness

Jailbreaks. Muse Spark "tracks GPT-5.4 under single-turn attacks and matches or outperforms Gemini 3.1 Pro at every stage of our cascaded attack pipeline," but "a robustness gap emerges" under adaptive multi-turn LLM attackers: 44.6% attack success against 31.7% for Claude Opus 4.6 and 37.6% for GPT-5.4. In cyber misuse it records the best result of any model evaluated — 9.0% attack success against 31.7–59.0% for peers, reduced to 8.2% in Meta AI.

Agent robustness. The report labels this section "a forward-looking baseline, not an assessment of today's system," because most threat models assume an attacker can use third-party tools that the current deployment does not permit. On AgentHarm, Muse Spark complies with 26.0% of harmful requests against 10.2% for GPT-5.4 and 8.2% for Claude Opus 4.6, "indicating room for improvement in broader multi-step agentic misuse scenarios." On indirect prompt injection, robustness "is still maturing relative to current state of the art": AgentDojo attack success 11.7% pass@1, better than Gemini 3.1 Pro on internal deep-research benchmarks but trailing GPT-5.4 and Claude Opus 4.6, and on the third-party GraySwan ART benchmark showing "greater sensitivity to injection than the other models GraySwan evaluated."

False refusals. Muse Spark shows 11.0% on chat cyber requests, 4.3% on agentic cyber, 8.0% on OR-Bench, and 6.8% on the benign AgentHarm subset. Meta's system-level defences raise these substantially: "Meta AI Instant jumps to 30.3% false refusal rate for cyber chat requests and 34.7% for benign agentic cyber requests," with Meta AI Thinking at 17.6% and 27.2%. The report is unusual in publishing the safety-tax cost of its own mitigations at this resolution.

Behavioural profile

Against an internal behaviour specification: instruction-hierarchy adherence 80.3% on IHEval (Gemini 3.1 Pro leading at 86.5%); 0% cheating rate on ImpossibleBench; intent understanding 71.2% on ambiguous intents and best-in-class 96.2% where underlying and stated intent conflict; lowest hallucination rate on CharXiv missing images at 35.0%; honesty 89.1% on MASK, second to GPT-5.4's 90.3% and far above Gemini 3.1 Pro's 44.1%; DeceptionBench 1.6% single-turn; lowest harmful-action rate on TextQuests at 2.4 per 100 actions.

Calibration is poor across the board — "all models exhibit poor confidence calibration when measured on Humanity's Last Exam," with Muse Spark at RMS error 50.3, trailing GPT-5.4 and Claude Opus 4.6.

Sycophancy is where system-level mitigation does the work: the raw model shows 62.9%, "the second highest after Gemini 3.1 Pro (65.6%), and substantially higher than GPT-5.4 (47.6%) and Claude Opus 4.6 (51.9%)," while Meta AI in Thinking mode reaches 50.1%, comparable to peers.

Reported results

Evaluation results the document states for which there is no separate benchmark page; results on benchmarks that have a page are recorded there and cite this page. Scores and settings are as printed in the document.

EvaluationModelScoreSettingSection
MBCT (Molecular Biology Capabilities Test)Gemini 3.1 Pro48.0accuracy, multiple-response MCQ, no tools; reported by Meta in the Muse Spark reportTable 1 / Fig. 1 (§2.1.1.1)
MBCT (Molecular Biology Capabilities Test)Kimi K2.545.1accuracy, multiple-response MCQ; reported by Meta in the Muse Spark reportFig. 1 (§2.1.1.1)
MBCT (Molecular Biology Capabilities Test)Llama 4 Maverick41.2accuracy, multiple-response MCQ; reported by Meta in the Muse Spark reportFig. 1 (§2.1.1.1)
HPCT (Human Pathogens Capabilities Test)Muse Spark55.7accuracy, multiple-response MCQ, no tools; developer-reportedTable 1 / Fig. 1 (§2.1.1.1)
HPCT (Human Pathogens Capabilities Test)GPT-5.463.0reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
HPCT (Human Pathogens Capabilities Test)Gemini 3.1 Pro64.3reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Fragment DesignMuse Spark96.8ReAct agent with biotools, helpful-only checkpoint; score = average of sub-component scores; benchmark built by SecureBio; developer-reportedTable 1 / Fig. 4 (§2.1.1.2)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Fragment DesignGPT-5.494.8reported by Meta in the Muse Spark reportTable 1 / Fig. 4 (§2.1.1.2)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Fragment DesignGemini 3.1 Pro93.4reported by Meta in the Muse Spark reportTable 1 / Fig. 4 (§2.1.1.2)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Liquid-Handling RobotMuse Spark93.1ReAct agent, helpful-only checkpoint; developer-reportedTable 1 / Fig. 4 (§2.1.1.2)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Liquid-Handling RobotGPT-5.492.3reported by Meta in the Muse Spark reportTable 1 / Fig. 4 (§2.1.1.2)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Liquid-Handling RobotGemini 3.1 Pro84.4reported by Meta in the Muse Spark reportTable 1 / Fig. 4 (§2.1.1.2)
ABC Bench (Agentic Bio-Capabilities Benchmark) — Screening EvasionMuse Spark54.1ReAct agent, helpful-only checkpoint; peer results withheld due to high refusals; developer-reportedFig. 4 (§2.1.1.2)
BioDesign Tools — Average of 5 tasksMuse Spark46.2ReAct agent with task-specific computational-biology tools sourced early 2025; normalized 0–1 scores ×100; developer-reportedTable 1 (§1.1.1)
BioDesign Tools — Average of 5 tasksGPT-5.458.5reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
BioDesign Tools — Average of 5 tasksGemini 3.1 Pro59.5reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
High-Risk Bottlenecks: Chemical Threats — OverallMuse Spark66.7helpful-only checkpoint; share of tasks at or above the "possibly enabling" threshold (≥50% of rubric points), 10/15 tasks, expert-validated rubrics, OSS Model A as judge; developer-reportedTable 1 / Fig. 6 (§2.1.2)
High-Risk Bottlenecks: Chemical Threats — OverallOSS Model A (unnamed open-weight model)53.38/15 tasks; reported by Meta in the Muse Spark reportTable 1 / Fig. 6 (§2.1.2)
High-Risk Bottlenecks: Chemical Threats — OverallOSS Model B (unnamed open-weight model)0.00/15 tasks; reported by Meta in the Muse Spark reportTable 1 / Fig. 6 (§2.1.2)
High-Risk Bottlenecks: Chemical Threats — OverallOSS Model C (unnamed open-weight model)0.00/13 tasks (2 synthesis tasks excluded for refusals); reported by Meta in the Muse Spark reportTable 1 / Fig. 6 (§2.1.2)
High-Risk Bottlenecks: Biological Threats — OverallMuse Spark50.0helpful-only checkpoint; 8/16 tasks at or above "possibly enabling"; 31% of tasks "likely enabling"; developer-reportedTable 1 / Fig. 7 (§2.1.2)
High-Risk Bottlenecks: Biological Threats — OverallOSS Model A (unnamed open-weight model)56.39/16 tasks; reported by Meta in the Muse Spark reportTable 1 / Fig. 7 (§2.1.2)
High-Risk Bottlenecks: Biological Threats — OverallOSS Model B (unnamed open-weight model)25.04/16 tasks; reported by Meta in the Muse Spark reportTable 1 / Fig. 7 (§2.1.2)
High-Risk Bottlenecks: Biological Threats — OverallOSS Model C (unnamed open-weight model)29.04/14 tasks (2 production tasks excluded for refusals); reported by Meta in the Muse Spark reportTable 1 / Fig. 7 (§2.1.2)
High-Risk Bottlenecks: Operational Execution — OverallMuse Spark92.0helpful-only checkpoint; 12/13 tasks; developer-reportedTable 1 / Fig. 8 (§2.1.2)
High-Risk Bottlenecks: Operational Execution — OverallOSS Model A (unnamed open-weight model)92.012/13 tasks; reported by Meta in the Muse Spark reportTable 1 / Fig. 8 (§2.1.2)
High-Risk Bottlenecks: Operational Execution — OverallOSS Model B (unnamed open-weight model)62.08/13 tasks; reported by Meta in the Muse Spark reportTable 1 / Fig. 8 (§2.1.2)
High-Risk Bottlenecks: Operational Execution — OverallOSS Model C (unnamed open-weight model)33.02/6 tasks (only the six tasks without refusals shown); reported by Meta in the Muse Spark reportTable 1 / Fig. 8 (§2.1.2)
BioTIER v1 refusal — Harmful categoriesMeta AI98.0refusal rate on 501 prompts (Select Agents, Biomedical DURC, Catastrophe Avoidance); run against the deployed system; developer-reportedTable 2 / Fig. 9 (§2.1.3)
BioTIER v1 refusal — Harmful categoriesGPT-5.475.4reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
BioTIER v1 refusal — Harmful categoriesClaude Opus 4.695.4reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
BioTIER v1 refusal — Harmful categoriesGemini 3.1 Pro59.2reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
BioTIER v1 refusal — Harmful categoriesKimi K2.521.2%reported by Meta in the Muse Spark reportFig. 9 (§2.1.3)
BioTIER v1 refusal — Harmful categoriesDeepSeek-R113.3%reported by Meta in the Muse Spark reportFig. 9 (§2.1.3)
BioTIER multilingual refusal — Blended multilingualMeta AI97.8%average blended refusal rate across language buckets; developer-reportedFig. 12a (§2.1.3)
HPCT refusal-labeled subset — Refusal rateMeta AI94.3%free-response variant; 87 of 100 HPCT questions labeled should-refuse; developer-reportedFig. 10b (§2.1.3)
Internal Chemical Agents refusal — EnglishMeta AI99.4refusal rate, English prompts, run against the deployed system; developer-reportedTable 2 / Fig. 11 (§2.1.3)
Internal Chemical Agents refusal — EnglishGPT-5.488.4reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Internal Chemical Agents refusal — EnglishClaude Opus 4.697.6reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Internal Chemical Agents refusal — EnglishGemini 3.1 Pro96.6reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Internal Chemical Agents refusal — EnglishKimi K2.586.6%reported by Meta in the Muse Spark reportFig. 11 (§2.1.3)
Internal Chemical Agents refusal — EnglishDeepSeek-R166.1%reported by Meta in the Muse Spark reportFig. 11 (§2.1.3)
Internal Chemical Agents refusal — Blended multilingualMeta AI99.2%average across language buckets; developer-reportedFig. 12b (§2.1.3)
Curated CTF set (Meta internal + public) — pass@1Muse Spark72.0%198 challenges, 171 solved; ReAct agent (single-submission restriction would cut pass@1 by 7.8pp); developer-reportedTable 8 / Fig. 18 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@10Muse Spark86.4%10 independent attempts; developer-reportedFig. 18 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, CryptoMuse Spark77.250 tasks, 46 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, ForensicsMuse Spark63.116 tasks, 14 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, MiscMuse Spark95.922 tasks, 22 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, PwnMuse Spark54.542 tasks, 28 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, RevMuse Spark78.251 tasks, 47 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, WebMuse Spark58.217 tasks, 14 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, EasyMuse Spark88.292 tasks, 90 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, MediumMuse Spark58.636 tasks, 29 solved; developer-reportedTable 8 (§2.2.2.1)
Curated CTF set (Meta internal + public) — pass@1, HardMuse Spark57.670 tasks, 52 solved; developer-reportedTable 8 (§2.2.2.1)
Irregular atomic challenges — TotalMuse Spark7027 challenges, 19 solved; independently run by Irregular with its own scaffold, 20 runs per challenge, up to 1,000 turns, solved = at least one successTable 9 (§2.2.2.2)
Irregular atomic challenges — ReconnaissanceMuse Spark1002 challenges, 2 solved; measured by IrregularTable 9 (§2.2.2.2)
Irregular atomic challenges — ExploitationMuse Spark506 challenges, 3 solved; measured by IrregularTable 9 (§2.2.2.2)
Irregular atomic challenges — Installation / EvasionMuse Spark7516 challenges, 12 solved; measured by IrregularTable 9 (§2.2.2.2)
Irregular atomic challenges — Actions on ObjectivesMuse Spark673 challenges, 2 solved; measured by IrregularTable 9 (§2.2.2.2)
Irregular challenges (27 atomic + 10 end-to-end) — EasyMuse Spark10012 challenges, 12 solved; measured by IrregularTable 10 (§2.2.2.2)
Irregular challenges (27 atomic + 10 end-to-end) — MediumMuse Spark4613 challenges, 6 solved; measured by IrregularTable 10 (§2.2.2.2)
Irregular challenges (27 atomic + 10 end-to-end) — HardMuse Spark812 challenges, 1 solved; measured by IrregularTable 10 (§2.2.2.2)
CyScenarioBenchMuse Spark0.010 scenarios, 20 runs each, Irregular's optimized agent; no end-to-end attack chain completed; developer-reportedTable 1 / §2.2.2.2
CyScenarioBenchGPT-5.4 Thinking11.0reported by Meta in the Muse Spark report, citing the GPT-5.4 Thinking system card (OpenAI 2026); 11 scenarios in a previous version of the benchmark, 5/11 solved, average success rate across multiple runsTable 1 (§1.1.1, footnote 5)
Charlemagne Labs multi-turn social engineering — Composite scoreMuse Spark57.3geometric mean of believability, consistency, sustained turns; max 5 turns; 852 scenarios; judge and victim model Gemini 3.1 Pro; scored over non-refused prompts; developer-reportedTable 1 / Fig. 20 (§2.2.2.3)
Charlemagne Labs multi-turn social engineering — Composite scoreKimi K2.554.0temperature 0.6, max_tokens 1024 (50% of responses truncated, so possibly an underestimate); judge/victim Gemini 3.0 Pro; reported by Meta in the Muse Spark reportTable 1 / Fig. 20 (§2.2.2.3)
Charlemagne Labs multi-turn social engineering — Composite scoreGLM-552.5temperature 0.6, max_tokens 1024; reported by Meta in the Muse Spark reportFig. 20 (§2.2.2.3)
Charlemagne Labs multi-turn social engineering — Composite scoreQwen347.2temperature 0.6, max_tokens 1024; reported by Meta in the Muse Spark reportTable 1 / Fig. 20 (§2.2.2.3)
Charlemagne Labs multi-turn social engineering — Composite scoreDeepSeek V341.2temperature 0.6, max_tokens 1024; reported by Meta in the Muse Spark reportTable 1 / Fig. 20 (§2.2.2.3)
Social engineering compliance (no system defenses) — Attack success rateMuse Spark68.8%share of samples where an LLM judge (Gemini 3.1 Pro) finds the model complied with the social-engineering request; developer-reportedFig. 22a (§2.2.3)
Social engineering compliance (no system defenses) — Attack success rateDeepSeek V3100.0%reported by Meta in the Muse Spark reportFig. 22a (§2.2.3)
Social engineering compliance (no system defenses) — Attack success rateGLM-557.6%reported by Meta in the Muse Spark reportFig. 22a (§2.2.3)
Social engineering refusal (with system defenses) — Refusal rateMeta AI99.9run against the deployed system; compliance 0.1–0.4%; developer-reportedTable 2 / Fig. 22b (§2.2.3)
Social engineering refusal (with system defenses) — Refusal rateGPT-5.499.5compliance 0.5%; reported by Meta in the Muse Spark reportTable 2 / Fig. 22b (§2.2.3)
Social engineering refusal (with system defenses) — Refusal rateClaude Opus 4.699.6compliance 0.4%; reported by Meta in the Muse Spark reportTable 2 / Fig. 22b (§2.2.3)
Social engineering refusal (with system defenses) — Refusal rateGemini 3.1 Pro86.9compliance 13.1%; reported by Meta in the Muse Spark reportTable 2 / Fig. 22b (§2.2.3)
High-severity cyber-misuse compliance — Compliance rateMuse Spark0.2%model-level mitigations only, subset of prompts that could contribute to Framework high-severity outcomes; developer-reportedFig. 21 (§2.2.3)
High-severity cyber-misuse compliance — Compliance rateMeta AI Instant0.4%deployed system; developer-reportedFig. 21 (§2.2.3)
High-severity cyber-misuse compliance — Compliance rateMeta AI Thinking0.5%deployed system; developer-reportedFig. 21 (§2.2.3)
Severe cyber-misuse refusal — Refusal rateMeta AI99.6run against the deployed system (= 0.4% compliance); developer-reportedTable 2 (§1.1.1)
Severe cyber-misuse refusal — Refusal rateGPT-5.499.0= 1.0% compliance; reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Severe cyber-misuse refusal — Refusal rateClaude Opus 4.694.9= 5.1% compliance; reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Severe cyber-misuse refusal — Refusal rateGemini 3.1 Pro98.6= 1.4% compliance; reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
CyberSecEval secure code generation — AutocompleteMuse Spark62.0%share of generated code without known insecure patterns, CodeShield detector, nine languages, single-turn; developer-reportedFig. 23 (§2.2.4)
CyberSecEval secure code generation — AutocompleteGPT-5.459.3%reported by Meta in the Muse Spark reportFig. 23 (§2.2.4)
CyberSecEval secure code generation — AutocompleteClaude Opus 4.654.2%reported by Meta in the Muse Spark reportFig. 23 (§2.2.4)
CyberSecEval secure code generation — AutocompleteGemini 3.1 Pro56.7%reported by Meta in the Muse Spark reportFig. 23 (§2.2.4)
CyberSecEval secure code generation — InstructMuse Spark69.5%natural-language task description, generated code scanned by CodeShield; developer-reportedFig. 23 (§2.2.4)
CyberSecEval secure code generation — InstructGPT-5.468.3%reported by Meta in the Muse Spark reportFig. 23 (§2.2.4)
CyberSecEval secure code generation — InstructClaude Opus 4.664.9%reported by Meta in the Muse Spark reportFig. 23 (§2.2.4)
CyberSecEval secure code generation — InstructGemini 3.1 Pro70.4%reported by Meta in the Muse Spark reportFig. 23 (§2.2.4)
Secure code generation (scorecard average) — Autocomplete + Instruct averageMuse Spark65.7scorecard row averaging the two modalities; developer-reportedTable 2 (§1.1.1)
Secure code generation (scorecard average) — Autocomplete + Instruct averageGPT-5.463.8reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Secure code generation (scorecard average) — Autocomplete + Instruct averageClaude Opus 4.659.5reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Secure code generation (scorecard average) — Autocomplete + Instruct averageGemini 3.1 Pro63.6reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
AIRS-Bench — Average normalized scoreMuse Spark0.65±0.03; 20 research tasks, 10 seeds, AIRA-Dojo scaffold with greedy search, H200 141GB, 24h per task; 1.0 = human SOTA; developer-reportedTable 12 (§2.3.1.1)
AIRS-Bench — Average normalized scoreGPT-5.40.74±0.04; reported by Meta in the Muse Spark reportTable 12 (§2.3.1.1)
AIRS-Bench — Average normalized scoreClaude Opus 4.60.74±0.02; reported by Meta in the Muse Spark reportTable 12 (§2.3.1.1)
AIRS-Bench — Average normalized scoreGemini 3.1 Pro0.78±0.02; reported by Meta in the Muse Spark reportTable 12 (§2.3.1.1)
AIRS-Bench — Valid submission rateMuse Spark88.00%±4.00; share of runs producing working solutions scoring above zero; developer-reported (body text of §2.3.1.1 instead states 86.43% — see Notes)Table 12 (§2.3.1.1)
AIRS-Bench — Valid submission rateGPT-5.4100.00%±0.00; reported by Meta in the Muse Spark reportTable 12 (§2.3.1.1)
AIRS-Bench — Valid submission rateClaude Opus 4.699.00%±1.5; reported by Meta in the Muse Spark reportTable 12 (§2.3.1.1)
AIRS-Bench — Valid submission rateGemini 3.1 Pro100.00%±0.00; reported by Meta in the Muse Spark reportTable 12 (§2.3.1.1)
AIRS-Bench (scorecard) — ANS ×100Muse Spark64.8scorecard restatement of the average normalized score ×100; developer-reportedTable 1 (§1.1.1)
AIRS-Bench (scorecard) — ANS ×100GPT-5.474.3reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
AIRS-Bench (scorecard) — ANS ×100Claude Opus 4.674.1reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
AIRS-Bench (scorecard) — ANS ×100Gemini 3.1 Pro78.5reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
AIRS-Bench — Tasks exceeding human SOTAMuse Spark5 / 20inconsistent across attempts: for 2 of the 5 tasks, human SOTA was exceeded in fewer than half of 10 attempts; developer-reported§2.3.1.1
Prompted evaluation awareness — Overall (weighted)Muse Spark42.98%classifier rate at which the model correctly identifies evaluation contexts when explicitly tasked to do so; weighted by sample count; developer-reportedTable 13 (§2.3.1.2)
Prompted evaluation awareness — Overall (weighted)GPT-5.443.83%GPT-5.4 refuses to classify 4.7% of samples; reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — Overall (weighted)Gemini 3.1 Pro90.42%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — Chemical & BiologicalMuse Spark33.10%developer-reportedTable 13 (§2.3.1.2)
Prompted evaluation awareness — Chemical & BiologicalGPT-5.455.76%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — Chemical & BiologicalGemini 3.1 Pro91.11%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — CyberMuse Spark36.10%developer-reportedTable 13 (§2.3.1.2)
Prompted evaluation awareness — CyberGPT-5.440.95%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — CyberGemini 3.1 Pro84.46%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — Loss of ControlMuse Spark66.00%developer-reportedTable 13 (§2.3.1.2)
Prompted evaluation awareness — Loss of ControlGPT-5.432.43%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Prompted evaluation awareness — Loss of ControlGemini 3.1 Pro98.23%reported by Meta in the Muse Spark reportTable 13 (§2.3.1.2)
Evaluation-awareness follow-ups — Acknowledges safety/alignment assessmentMuse Spark81.1%conditional on the prompt being identified as an evaluation; developer-reported§2.3.1.2
Evaluation-awareness follow-ups — Recognizes deployment stakesMuse Spark93.4%recognizes evaluation performance could affect deployment decisions; developer-reported§2.3.1.2
Evaluation-awareness follow-ups — Recognizes conflict with trained objectivesMuse Spark69.1%developer-reported§2.3.1.2
Verbalized evaluation awareness (CB evaluations) — Suspicion, WMDP-ChemMuse Spark2.1highest suspicion rate among the ten CB datasets; recognition 0.6, strategic underperformance 0.1, awareness influenced 0.2, primary driver 0.1; developer-reportedTable 14 (§2.3.1.2)
Verbalized evaluation awareness (CB evaluations) — Suspicion, WMDP-BioMuse Spark0.9all other columns 0.0; developer-reportedTable 14 (§2.3.1.2)
Verbalized evaluation awareness (CB evaluations) — Suspicion, LAB-Bench ProtocolQAMuse Spark0.5all other columns 0.0; developer-reportedTable 14 (§2.3.1.2)
Verbalized evaluation awareness (CB evaluations) — Suspicion, HPCT (MCQ)Muse Spark0.4recognition 0.1, other columns 0.0; developer-reportedTable 14 (§2.3.1.2)
Verbalized evaluation awareness (CB evaluations) — Suspicion, VCT (MCQ)Muse Spark0.3recognition 0.2, other columns 0.0; developer-reportedTable 14 (§2.3.1.2)
Verbalized evaluation awareness (CB evaluations) — Suspicion, MBCTMuse Spark0.2recognition 0.1, other columns 0.0; developer-reportedTable 14 (§2.3.1.2)
Verbalized evaluation awareness (CB refusals) — Suspicion, VCT / HPCT / BioTIER / internal chem refusal setsMuse Spark0.0all four refusal datasets score 0.0 on every column; developer-reportedTable 14 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-oblivious, ∆TargetMuse Spark31.80 pppercentage-point drop from baseline on CB tasks when instructed to underperform; statistically significant across all datasets; developer-reportedTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-aware, ∆TargetMuse Spark37.12 ppdeveloper-reportedTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-oblivious, ∆TargetGPT-5.441.38 pp∆Control 0.50 pp; reported by Meta in the Muse Spark reportTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-aware, ∆TargetGPT-5.439.81 pp∆Control 0.66 pp; reported by Meta in the Muse Spark reportTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-oblivious, ∆TargetClaude Opus 4.62.58 ppnot statistically significant; ∆Control 0.18 pp; reported by Meta in the Muse Spark reportTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-aware, ∆TargetClaude Opus 4.61.63 pp∆Control 0.03 pp; reported by Meta in the Muse Spark reportTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-oblivious, ∆TargetGemini 3.1 Pro33.01 pp∆Control 0.57 pp; reported by Meta in the Muse Spark reportTable 15 (§2.3.1.2)
Overt selective performance (instructed sandbagging) — Monitor-aware, ∆TargetGemini 3.1 Pro35.81 pp∆Control 0.97 pp; reported by Meta in the Muse Spark reportTable 15 (§2.3.1.2)
Sandbagging monitor — Detection of successful sandbaggingMeta CoT monitor>90%with <5% false positive rate, on Muse Spark trajectories; developer-reported§2.3.1.2
Self-initiated selective performance under pressure — Low pressureMuse Spark2.2%verbalized strategic reasoning rate; ∆Target 2.37 pp, ∆Control 0.0 pp; developer-reportedTable 16 (§2.3.1.2)
Self-initiated selective performance under pressure — Medium pressureMuse Spark5.6%∆Target 1.97 pp, ∆Control 0.0 pp; developer-reportedTable 16 (§2.3.1.2)
Self-initiated selective performance under pressure — High pressureMuse Spark15.2%∆Target 3.63 pp, ∆Control 0.0 pp; developer-reportedTable 16 (§2.3.1.2)
Apollo Research sandbagging evaluations — Underperformance rateMuse Spark32%statistically significant; third-party (Apollo Research); no in-context goal but explicit description of deployment criteria tied to task performance§2.3.1.2
SHADE-Arena — Main task, no side task (baseline)Muse Spark81.7%26 challenges, 10 runs each; Gemini 2.5 monitor, detection threshold 80; developer-reportedFig. 25 (§2.3.2)
SHADE-Arena — Main task with side task, no monitoringMuse Spark49.2%developer-reportedFig. 25 (§2.3.2)
SHADE-Arena — Side task, no monitoringMuse Spark71.9%developer-reportedFig. 25 (§2.3.2)
SHADE-Arena — Both tasks, no monitoringMuse Spark36.2%developer-reportedFig. 25 (§2.3.2)
SHADE-Arena — Side task, monitoring on tool calls and responsesMuse Spark20.4%developer-reportedFig. 25 (§2.3.2)
SHADE-Arena — Overall (both tasks) under active monitoringMuse Spark8.8developer-reportedTable 1 / Fig. 25 (§2.3.2)
SHADE-Arena — Overall (both tasks) under active monitoringGPT-5.40.8reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
SHADE-Arena — Overall (both tasks) under active monitoringClaude Opus 4.66.5reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
SHADE-Arena — Overall (both tasks) under active monitoringGemini 3.1 Pro9.2reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
SHADE-Arena — Overall, monitor also sees chain-of-thoughtMuse Spark<2%developer-reported§2.3.2
GDM Stealth — Average across 4 challengesMuse Spark39.8challenge-specific automated monitors, 50 runs per challenge; developer-reportedTable 1 (§1.1.1)
GDM Stealth — Average across 4 challengesGPT-5.414.3reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
GDM Stealth — Average across 4 challengesClaude Opus 4.618.0Meta notes Opus 4.6 often refuses the secondary task; reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
GDM Stealth — Average across 4 challengesGemini 3.1 Pro61.0reported by Meta in the Muse Spark reportTable 1 (§1.1.1)
GDM Situational Awareness — Challenges passedMuse Spark4 / 1136.7%; pass = >20% success on a challenge; developer-reportedTable 17 (§2.3.2)
GDM Situational Awareness — Average success rateMuse Spark29.3developer-reportedTable 17 (§2.3.2)
GDM Situational Awareness — Challenges passedGPT-5.46 / 1154.6%; average success rate 48.0; reported by Meta in the Muse Spark reportTable 17 (§2.3.2)
GDM Situational Awareness — Challenges passedGemini 3.1 Pro6 / 1154.6%; average success rate 41.3; reported by Meta in the Muse Spark reportTable 17 (§2.3.2)
GDM Situational Awareness — Challenges passedClaude Opus 4.66 / 1154.6%; average success rate 43.1; reported by Meta in the Muse Spark reportTable 17 (§2.3.2)
Apollo Research covert-action propensity — Average across evaluationsMuse Spark8%third-party (Apollo Research), "no nudge" setting; max 30% on impossible coding tasks and 15% on subagent collusion§2.3.2
Cyber misuse jailbreak robustness — Overall ASRMuse Spark9.0%+2.7/−2.2; 600 cyber-misuse prompts × 23 conditions (baseline + 22 static attack templates) = 13,800 samples; prompt counted broken if any template succeeds; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Overall ASRMeta AI Thinking8.2%+2.2/−2.2; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Overall ASRGPT-5.459.0%+3.8/−4.2; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Overall ASRClaude Opus 4.631.7%+3.7/−3.7; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Overall ASRGemini 3.1 Pro32.8%+3.5/−3.8; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — No attackMuse Spark0.3%+0.5/−0.3; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — No attackMeta AI Thinking2.0%+1.2/−1.0; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — No attackGPT-5.40.8%+0.8/−0.7; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — No attackClaude Opus 4.621.0%+3.3/−3.0; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — No attackGemini 3.1 Pro1.0%+0.8/−0.7; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Encoding attacksMuse Spark1.5%+1.0/−0.8; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Encoding attacksMeta AI Thinking2.7%+1.3/−1.2; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Encoding attacksGPT-5.40.8%+0.8/−0.7; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Encoding attacksClaude Opus 4.60.3%+0.5/−0.3; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Encoding attacksGemini 3.1 Pro6.2%+2.0/−1.8; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Persona attacksMuse Spark3.5%+1.5/−1.5; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Persona attacksMeta AI Thinking3.7%+1.7/−1.5; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Persona attacksGPT-5.47.0%+2.2/−1.8; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Persona attacksClaude Opus 4.610.2%+2.5/−2.5; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Persona attacksGemini 3.1 Pro8.0%+2.0/−2.2; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Context injectionMuse Spark4.3%+1.5/−1.7; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Context injectionMeta AI Thinking3.3%+1.7/−1.5; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Context injectionGPT-5.451.7%+4.0/−3.8; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Context injectionClaude Opus 4.617.5%+3.0/−3.0; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Context injectionGemini 3.1 Pro15.0%+2.8/−2.8; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Composite attacksMuse Spark1.3%+1.0/−0.8; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Composite attacksMeta AI Thinking2.7%+1.3/−1.2; developer-reportedTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Composite attacksGPT-5.416.0%+3.0/−2.8; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Composite attacksClaude Opus 4.628.3%+3.5/−3.7; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Cyber misuse jailbreak robustness — Composite attacksGemini 3.1 Pro14.2%+2.8/−2.7; reported by Meta in the Muse Spark reportTable 18 (§3.1.2.2)
Jailbreak cyber misuse (scorecard) — Attack success rateMuse Spark9.0scorecard restatement of Table 18 overall ASR; developer-reportedTable 2 (§1.1.1)
Jailbreak cyber misuse (scorecard) — Attack success rateGPT-5.459.0reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Jailbreak cyber misuse (scorecard) — Attack success rateClaude Opus 4.631.7reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Jailbreak cyber misuse (scorecard) — Attack success rateGemini 3.1 Pro32.8reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
Direct cyber misuse requests (baseline) — Attack success rateMuse Spark1.5%600 private cyber-misuse prompts, no attack, expected pass@1 over 5 epochs; developer-reportedFig. 28a (§3.1.2.1)
Direct cyber misuse requests (baseline) — Attack success rateMeta AI Instant0.2%developer-reported§3.1.2.1
Direct cyber misuse requests (baseline) — Attack success rateMeta AI Thinking2.2%developer-reported§3.1.2.1
Direct cyber misuse requests (baseline) — Attack success rateGemini 3.1 Pro3.5%second-lowest ASR among peers; reported by Meta in the Muse Spark report§3.1.2.1
FORTRESS — Average risk scoreMuse Spark20.3independently evaluated by ScaleAI on the private FORTRESS set; lower is betterTable 2 / Fig. 30 (§3.1.3.1)
FORTRESS — Average risk scoreMeta AI Thinking24.0measured by ScaleAIFig. 30 (§3.1.3.1)
FORTRESS — Average risk scoreGPT-5.4 Pro14.8ScaleAI leaderboard configuration, not matched to Meta's own GPT-5.4 configurationTable 2 / Fig. 30 (§3.1.3.1)
FORTRESS — Average risk scoreClaude Opus 4.6 (max)13.0ScaleAI leaderboard configurationTable 2 / Fig. 30 (§3.1.3.1)
FORTRESS — Average risk scoreGemini 3.1 Pro29.8ScaleAI leaderboard configurationTable 2 / Fig. 30 (§3.1.3.1)
HandshakeAI human red teaming — Violating jailbreaks foundMeta AI Thinking9 / 58third-party human red team, ~149 hours, 4 prioritized harm categories, no CoT access, no prefill, no automated attacks; 1.62 h average per attempt§3.1.3.2
Search-related tool-use (trigger stage) — Compliance rateMeta AI Thinking1.1%share of adversarially crafted disallowed search requests not refused; developer-reported§1.1.2 / Fig. 31a (§3.2.1.1)
Agentic cyber misuse — Attack success rateMuse Spark2.4internal prompt set simulating malicious agentic cyber workflows with tool access; developer-reportedTable 2 / Fig. 33 (§3.2.1.3)
Agentic cyber misuse — Attack success rateMeta AI Instant0.5%developer-reportedFig. 33 (§3.2.1.3)
Agentic cyber misuse — Attack success rateMeta AI Thinking0.5%developer-reportedFig. 33 (§3.2.1.3)
Agentic cyber misuse — Attack success rateGPT-5.42.7reported by Meta in the Muse Spark reportTable 2 / Fig. 33 (§3.2.1.3)
Agentic cyber misuse — Attack success rateClaude Opus 4.68.5reported by Meta in the Muse Spark reportTable 2 / Fig. 33 (§3.2.1.3)
Agentic cyber misuse — Attack success rateGemini 3.1 Pro5.6reported by Meta in the Muse Spark reportTable 2 / Fig. 33 (§3.2.1.3)
AgentDojo — ASR pass@1Muse Spark11.7adaptive LLM attacker in Meta's SIREN harness rather than the static attacks of Debenedetti et al.; developer-reportedTable 2 / Fig. 34 (§3.2.2)
AgentDojo — ASR pass@1GPT-5.42.0reported by Meta in the Muse Spark reportTable 2 / Fig. 34 (§3.2.2)
AgentDojo — ASR pass@1Claude Opus 4.60.2reported by Meta in the Muse Spark reportTable 2 / Fig. 34 (§3.2.2)
AgentDojo — ASR pass@1Gemini 3.1 Pro3.0reported by Meta in the Muse Spark reportTable 2 / Fig. 34 (§3.2.2)
GraySwan Agent Red Teaming (ART) — Indirect-injection subset, ASR pass@1Muse Spark6.7measured by GraySwan on its private ART benchmark before launchTable 2 / Fig. 37 (§3.2.2.3)
GraySwan Agent Red Teaming (ART) — Indirect-injection subset, ASR pass@1GPT-5.41.2measured by GraySwanTable 2 / Fig. 37 (§3.2.2.3)
GraySwan Agent Red Teaming (ART) — Indirect-injection subset, ASR pass@1Claude Opus 4.6 (max)0.2measured by GraySwanTable 2 / Fig. 37 (§3.2.2.3)
GraySwan Agent Red Teaming (ART) — Indirect-injection subset, ASR pass@1Gemini 3.1 Pro1.0measured by GraySwanTable 2 / Fig. 37 (§3.2.2.3)
False refusal rate — Cyber benign use (chat)Muse Spark11.0%+1.7/−1.7; benign prompts; lower is better; developer-reportedTable 19 (§3.3)
False refusal rate — Cyber benign use (chat)Meta AI Instant30.3%+2.4/−2.7; developer-reportedTable 19 (§3.3)
False refusal rate — Cyber benign use (chat)Meta AI Thinking17.6%+2.3/−2.2; developer-reportedTable 19 (§3.3)
False refusal rate — Cyber benign use (chat)GPT-5.44.7%+1.0/−1.0; reported by Meta in the Muse Spark reportTable 19 (§3.3)
False refusal rate — Cyber benign use (chat)Claude Opus 4.610.5%+2.0/−1.9; reported by Meta in the Muse Spark reportTable 19 (§3.3)
False refusal rate — Cyber benign use (chat)Gemini 3.1 Pro2.4%+0.7/−0.6; reported by Meta in the Muse Spark reportTable 19 (§3.3)
False refusal rate — Cyber benign use (agentic)Muse Spark4.3%+3.7/−2.8; developer-reportedTable 19 (§3.3)
False refusal rate — Cyber benign use (agentic)Meta AI Instant34.7%+6.4/−6.3; developer-reportedTable 19 (§3.3)
False refusal rate — Cyber benign use (agentic)Meta AI Thinking27.2%+6.7/−5.8; developer-reportedTable 19 (§3.3)
False refusal rate — Cyber benign use (agentic)GPT-5.41.2%+1.2/−1.0; reported by Meta in the Muse Spark reportTable 19 (§3.3)
False refusal rate — Cyber benign use (agentic)Claude Opus 4.61.2%+1.3/−1.0; reported by Meta in the Muse Spark reportTable 19 (§3.3)
False refusal rate — Cyber benign use (agentic)Gemini 3.1 Pro1.3%+1.3/−1.0; reported by Meta in the Muse Spark reportTable 19 (§3.3)
OR-Bench — False refusal rateMuse Spark8.0%+1.5/−1.6; developer-reportedTable 19 / Table 2 (§3.3)
OR-Bench — False refusal rateMeta AI Instant11.2%+1.7/−1.7; developer-reported (note: §1.1.2 text says Meta AI Instant reduces OR-Bench false refusals to 5.1% — see Notes)Table 19 (§3.3)
OR-Bench — False refusal rateMeta AI Thinking5.1%+1.2/−1.1; developer-reportedTable 19 (§3.3)
OR-Bench — False refusal rateGPT-5.48.3%+1.4/−1.5; reported by Meta in the Muse Spark reportTable 19 (§3.3)
OR-Bench — False refusal rateClaude Opus 4.62.0%+0.9/−0.7; reported by Meta in the Muse Spark reportTable 19 (§3.3)
OR-Bench — False refusal rateGemini 3.1 Pro2.1%+0.8/−0.8; reported by Meta in the Muse Spark reportTable 19 (§3.3)
IHEval — Composite across conflict typesMuse Spark80.3user vs developer and user vs tool/environment conflicts; minimal system prompt; developer-reportedTable 2 (§1.1.3, §4.1.1)
IHEval — Composite across conflict typesGPT-5.482.3reported by Meta in the Muse Spark reportTable 2 (§1.1.3)
IHEval — Composite across conflict typesClaude Opus 4.680.9reported by Meta in the Muse Spark reportTable 2 (§1.1.3)
IHEval — Composite across conflict typesGemini 3.1 Pro86.5reported by Meta in the Muse Spark reportTable 2 (§1.1.3)
ImpossibleBench — Cheating rateMuse Spark0.0%"oneoff" impossibility subset; cheating = passing impossible tests by modifying or circumventing them; verbalization rate ~90–100% for all models; developer-reportedTable 2 / Fig. 39 (§4.1.2)
ImpossibleBench — Cheating rateGPT-5.40.0%reported by Meta in the Muse Spark reportFig. 39 (§4.1.2)
ImpossibleBench — Cheating rateClaude Opus 4.62.9%reported by Meta in the Muse Spark reportFig. 39 (§4.1.2)
ImpossibleBench — Cheating rateGemini 3.1 Pro11.8%reported by Meta in the Muse Spark reportFig. 39 (§4.1.2)
Underspecified Intent (internal) — Intent accuracyMuse Spark71.2%macro-average across rubric criteria; examples drawn from real Meta AI interactions where users corrected the model; developer-reportedFig. 40a (§4.1.3)
Underspecified Intent (internal) — Intent accuracyGemini 3.1 Pro71.3%reported by Meta in the Muse Spark report§4.1.3
Underspecified Intent (internal) — Intent accuracyGPT-5.470.0%reported by Meta in the Muse Spark report§4.1.3
Underspecified Intent (internal) — Intent accuracyClaude Opus 4.667.7%reported by Meta in the Muse Spark report§4.1.3
Underlying Intent (internal) — Addresses underlying intent rateMuse Spark96.2%synthetic examples where stated and actual intent diverge; developer-reportedFig. 40b (§4.1.3)
Underlying Intent (internal) — Addresses underlying intent rateClaude Opus 4.695.0%reported by Meta in the Muse Spark report§4.1.3
AbstentionBench — Correct abstention rateMuse Spark59.1%macro-average across component datasets; developer-reported; peers cluster 64.1–65.0% (individual mapping not stated in text)Fig. 44a (§4.1.4)
MASK — Honesty rateMuse Spark89.1%+1.6/−1.7; fraction of samples where the model stays consistent with its beliefs under pressure to lie; developer-reportedTable 22 (§4.1.5)
MASK — Honesty rateGPT-5.490.3%+1.5/−1.7; reported by Meta in the Muse Spark reportTable 22 (§4.1.5)
MASK — Honesty rateClaude Opus 4.683.4%+2.2/−2.3; reported by Meta in the Muse Spark reportTable 22 (§4.1.5)
MASK — Honesty rateGemini 3.1 Pro44.1%+3.0/−3.0; reported by Meta in the Muse Spark reportTable 22 (§4.1.5)
DeceptionBench — Deception score, single-turnMuse Spark1.6fraction of scenarios where the model complies with a deceptive request; developer-reportedTable 2 / Fig. 45a (§4.1.5)
DeceptionBench — Deception score, single-turnGPT-5.41.2reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
DeceptionBench — Deception score, single-turnClaude Opus 4.60.3reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
DeceptionBench — Deception score, single-turnGemini 3.1 Pro25.7reported by Meta in the Muse Spark reportTable 2 (§1.1.1)
DeceptionBench — Deception score, multi-turn with pressureMuse Spark<2%stated as a bound in §1.1.3; developer-reported§1.1.3 / Fig. 45b (§4.1.5)
TextQuests — Harm per 100 stepsMuse Spark2.4Muse Spark Instant; 25 interactive-fiction games; impermissible actions normalized by trajectory length; 13.1% game progress; developer-reportedFig. 46 (§4.1.6)
TextQuests — Harm per 100 stepsGemini 3.1 Pro3.6low reasoning effort; 31.1% game progress; reported by Meta in the Muse Spark reportFig. 46 (§4.1.6)
TextQuests — Harm per 100 stepsClaude Opus 4.67.5low reasoning effort; 36.7% game progress; reported by Meta in the Muse Spark reportFig. 46 (§4.1.6)
PropensityBench — Overall propensity scoreMuse Spark24.5%run by Scale AI; 979 scenarios across biosecurity, chemical security, cybersecurity, self-proliferation; pressure applied across six dimensions; comparison models not run§4.1.6
PropensityBench — Plan–action consistencyMuse Spark55%verbalized plans match actions taken; reasoning-trace monitoring misses 25% of misaligned cases; evaluation awareness verbalized in <4% of examples; measured by Scale AI§4.1.6
Internal Sycophancy Eval — Sycophancy rate (standard split)Muse Spark62.9%Muse Spark Instant, no system-level mitigations; LLM-replay dynamic multi-turn; adversarially curated examples; developer-reportedTable 2 / Fig. 47 (§4.1.7)
Internal Sycophancy Eval — Sycophancy rateGPT-5.447.6%low reasoning effort; reported by Meta in the Muse Spark reportTable 2 / Fig. 47 (§4.1.7)
Internal Sycophancy Eval — Sycophancy rateClaude Opus 4.651.9%low reasoning effort; reported by Meta in the Muse Spark reportTable 2 / Fig. 47 (§4.1.7)
Internal Sycophancy Eval — Sycophancy rateGemini 3.1 Pro65.6%low reasoning effort; reported by Meta in the Muse Spark reportTable 2 / Fig. 47 (§4.1.7)
Internal Sycophancy Eval — Sycophancy rate, high reasoningMuse Spark57.7%Muse Spark Thinking; developer-reported§1.1.3 (§4.1.7)
Internal Sycophancy Eval — Sycophancy rate, high reasoningGemini 3.1 Pro68.9%high reasoning; reported by Meta in the Muse Spark report§1.1.3
Internal Sycophancy Eval — Sycophancy rate, deployed systemMeta AI Thinking50.1%deployed system with system prompt and guardrails; developer-reported§1.1.3 (§4.1.7)
Internal Sycophancy Eval — Sycophancy rate, high reasoningClaude Opus 4.650.9%high reasoning; reported by Meta in the Muse Spark report§1.1.3
Internal Sycophancy Eval — Sycophancy rate, high reasoningGPT-5.445.4%high reasoning; reported by Meta in the Muse Spark report§1.1.3
Internal Sycophancy Eval — Excessive anti-sycophancy rateMuse Spark8.3%Muse Spark Instant; developer-reported§4.1.7
Internal Sycophancy Eval — Excessive anti-sycophancy rateGemini 3.1 Pro7.0%low reasoning; reported by Meta in the Muse Spark report§4.1.7
Internal Sycophancy Eval — Excessive anti-sycophancy rateGPT-5.413.4%low reasoning; reported by Meta in the Muse Spark report§4.1.7
Internal Sycophancy Eval — Excessive anti-sycophancy rateClaude Opus 4.614.6%low reasoning; reported by Meta in the Muse Spark report§4.1.7
CIMemories — Violations@5Muse Spark78.3%worst-case contextual-privacy metric over 5 samples per task, 10 synthetic user profiles; lower is better; developer-reportedFig. 48 (§4.1.8)
CIMemories — Violations@5Claude Opus 4.682.9%reported by Meta in the Muse Spark reportFig. 48 (§4.1.8)
CIMemories — Violations@5GPT-5.45.1%reported by Meta in the Muse Spark reportFig. 48 (§4.1.8)
CIMemories — Violations@5Gemini 3.1 Pro24.9%reported by Meta in the Muse Spark reportFig. 48 (§4.1.8)
CIMemories — CompletenessMuse Spark72.7%share of attributes that should be shared which are shared; developer-reportedFig. 48 (§4.1.8)
CIMemories — CompletenessClaude Opus 4.670.5%reported by Meta in the Muse Spark reportFig. 48 (§4.1.8)
CIMemories — CompletenessGPT-5.442.1%reported by Meta in the Muse Spark reportFig. 48 (§4.1.8)
CIMemories — CompletenessGemini 3.1 Pro58.1%reported by Meta in the Muse Spark reportFig. 48 (§4.1.8)
Internal response-diversity eval — Heterogeneity (open-ended tasks)Muse Spark0.21Muse Spark Instant; taxonomy-guided LLM judge over pairwise responses; higher is betterFig. 49 (§4.1.9)
Internal response-diversity eval — Heterogeneity (open-ended tasks)Claude Opus 4.60.10low reasoning; reported by Meta in the Muse Spark reportFig. 49 (§4.1.9)
Internal response-diversity eval — Heterogeneity (open-ended tasks)Gemini 3.1 Pro0.17low reasoning; reported by Meta in the Muse Spark reportFig. 49 (§4.1.9)
Internal response-diversity eval — Heterogeneity (open-ended tasks)GPT-5.40.17low reasoning; reported by Meta in the Muse Spark reportFig. 49 (§4.1.9)
Internal response-diversity eval — Homogenization (single-answer tasks)Muse Spark0.67higher is better; developer-reportedFig. 49 (§4.1.9)
Internal response-diversity eval — Homogenization (single-answer tasks)Claude Opus 4.60.81reported by Meta in the Muse Spark reportFig. 49 (§4.1.9)
Internal response-diversity eval — Homogenization (single-answer tasks)Gemini 3.1 Pro0.81reported by Meta in the Muse Spark reportFig. 49 (§4.1.9)
Internal response-diversity eval — Homogenization (single-answer tasks)GPT-5.40.58reported by Meta in the Muse Spark reportFig. 49 (§4.1.9)
Alignment Faking — Compliance gapMuse Spark1.8%difference in compliance between "training" and "deployment" framings; not statistically different from 0; developer-reportedTable 2 / Fig. 50a (§4.1.10)
Alignment Faking — Compliance gapGPT-5.40.4%reported by Meta in the Muse Spark reportTable 2 / §4.1.10
Alignment Faking — Compliance gapClaude Opus 4.6−2.8%reported by Meta in the Muse Spark reportTable 2 / §4.1.10
Alignment Faking — Compliance gapGemini 3.1 Pro37.0%reported by Meta in the Muse Spark reportTable 2 / §4.1.10
Alignment Faking — Deceptive alignment rateMuse Spark0.0%strict CoT classifier; developer-reported§4.1.10
Alignment Faking — Deceptive alignment rateGemini 3.1 Pro7.9%GPT-5.4 and Claude Opus 4.6 also 0.0%; reported by Meta in the Muse Spark report§4.1.10
Agentic Misalignment — Harmful actionsMuse Spark47.7%+4.8/−4.9; 234 samples across blackmail, corporate espionage and lethal-action scenarios; share of tasks with at least one harmful action; developer-reportedTable 23 (§4.1.10)
Agentic Misalignment — Harmful actionsGPT-5.40.0%+0.0/−0.0; reported by Meta in the Muse Spark reportTable 23 (§4.1.10)
Agentic Misalignment — Harmful actionsClaude Opus 4.60.0%+0.0/−0.0; reported by Meta in the Muse Spark reportTable 23 (§4.1.10)
Agentic Misalignment — Harmful actionsGemini 3.1 Pro51.5%+5.3/−5.7; reported by Meta in the Muse Spark report (Table 2 and §1.1.3 give 51.4% — see Notes)Table 23 (§4.1.10)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, averageMuse Spark10.9%CoT classifier across nine alignment evaluations; 0.6% of samples unclassified; developer-reported§4.1.11 (Table 24)
Verbalized evaluation awareness (alignment evaluations) — Recognition, averageMuse Spark3.9%definitive certainty in 0.7%; developer-reported§4.1.11
Verbalized evaluation awareness (alignment evaluations) — Awareness influenced behavior, averageMuse Spark5.0%primary driver in 0.8%; developer-reported§4.1.11
Verbalized evaluation awareness (alignment evaluations) — Suspicion, public benchmarksMuse Spark17.6%average over publicly available benchmarks (DeceptionBench, ImpossibleBench, IHEval); developer-reported§4.1.11
Verbalized evaluation awareness (alignment evaluations) — Suspicion, internal evaluationsMuse Spark1.0%average over internal, non-public evaluations; developer-reported§4.1.11
Verbalized evaluation awareness (alignment evaluations) — Suspicion, DeceptionBenchMuse Spark35.75%n=898; recognition 12.92%, definitive 1.67%, influenced 11.02%, primary driver 0.22%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, DeceptionBench (multi-turn)Muse Spark35.63%n=595; recognition 12.94%, definitive 3.19%, influenced 12.27%, primary driver 0.00%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, ImpossibleBenchMuse Spark12.00%n=100; recognition 6.00%, definitive 0.00%, influenced 9.00%, primary driver 4.00%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, AbstentionBenchMuse Spark8.49%n=1,178; recognition 2.55%, definitive 0.51%, influenced 5.60%, primary driver 1.10%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, IHEvalMuse Spark6.80%n=9,131; recognition 2.63%, definitive 0.67%, influenced 4.86%, primary driver 1.89%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, Underspecified IntentMuse Spark2.20%n=2,042; recognition 0.44%, definitive 0.15%, influenced 1.37%, primary driver 0.10%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, SycophancyMuse Spark0.23%n=1,319; recognition 0.08%, definitive 0.00%, influenced 0.15%, primary driver 0.08%; developer-reportedTable 24 (§4.1.11)
Verbalized evaluation awareness (alignment evaluations) — Suspicion, Underlying User IntentMuse Spark0.36%n=834; recognition 0.24%, definitive 0.12%, influenced 0.24%, primary driver 0.24%; developer-reportedTable 24 (§4.1.11)
Effect of evaluation awareness — AbstentionBench, correct abstention rateMuse Spark0.82 vs 0.57eval-aware samples (n=100) vs not; ∆ +0.26, p<0.001; developer-reportedTable 25 (§4.1.11)
Effect of evaluation awareness — CharXiv Missing Images, hallucination rateMuse Spark0.14 vs 0.32eval-aware samples (n=208) vs not; ∆ −0.19, p<0.001; developer-reportedTable 25 (§4.1.11)
Effect of evaluation awareness — IHEval scoreMuse Spark0.87 vs 0.82eval-aware samples (n=621) vs not; ∆ +0.04, p<0.001; developer-reportedTable 25 (§4.1.11)
SAD-mini — Facts-LLMsMuse Spark96.4%±2.2; n=249; temperature 1, top_p 1; developer-reportedTable 31 (§4.2.3.1)
SAD-mini — Facts-LLMsClaude Opus 4.692.8%±3.0; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-LLMsGPT-5.494.0%±3.0; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-LLMsGemini 3.1 Pro96.0%±2.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-LLMsKimi K2.595.2%±2.6; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-Human-DefaultsMuse Spark95.8%±1.1; n=1,200; developer-reportedTable 31 (§4.2.3.1)
SAD-mini — Facts-Human-DefaultsClaude Opus 4.688.9%±1.7; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-Human-DefaultsGPT-5.473.2%±2.5; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-Human-DefaultsGemini 3.1 Pro94.2%±1.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Facts-Human-DefaultsKimi K2.594.4%±1.3; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — InfluenceMuse Spark89.2%±3.8; n=250; developer-reportedTable 31 (§4.2.3.1)
SAD-mini — InfluenceClaude Opus 4.684.8%±4.6; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — InfluenceGPT-5.473.6%±5.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — InfluenceGemini 3.1 Pro90.8%±3.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — InfluenceKimi K2.583.6%±4.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-FullMuse Spark44.8%±3.5; n=800; developer-reportedTable 31 (§4.2.3.1)
SAD-mini — Stages-FullClaude Opus 4.636.7%±3.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-FullGPT-5.427.3%±3.2; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-FullGemini 3.1 Pro67.2%±3.2; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-FullKimi K2.541.5%±3.4; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-OversightMuse Spark49.2%±4.9; n=400; developer-reportedTable 31 (§4.2.3.1)
SAD-mini — Stages-OversightClaude Opus 4.641.9%±5.0; ~3% of Stages samples triggered content-filter rejections; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-OversightGPT-5.455.8%±4.9; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-OversightGemini 3.1 Pro42.2%±5.0; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
SAD-mini — Stages-OversightKimi K2.547.2%±5.0; reported by Meta in the Muse Spark reportTable 31 (§4.2.3.1)
Action–belief gap (misbehavior evaluations) — Acts misaligned against stated beliefMuse Spark19.3%share of items; developer-reported§4.2.3.3
Action–belief gap (misbehavior evaluations) — Endorses misbehavior without actingMuse Spark9.3%developer-reported§4.2.3.3
Action–belief gap (misbehavior evaluations) — Acts misaligned against stated beliefGPT-5.411.1%endorsement without action 12.1%; reported by Meta in the Muse Spark report§4.2.3.3

Discrepancies noted

Table 12 gives Muse Spark's AIRS-Bench valid-submission rate as 88.00% where the text gives 86.43%; the agentic-misalignment figure for Gemini appears as both 51.5% and 51.4%; evaluation-awareness rates appear as 19.8% / 2.0% in one place and 17.6% / 1.0% in another; the IHEval figure's data labels cannot be reconciled with the scorecard. Where the report gives two figures, both are recorded above.

Relationships