Red team evaluation of GPT-OSS-120B across 250 test cases covering 25 IPI attack classes. Structural analysis of vulnerability patterns, delivery variants, and severity tiers.
GPT-OSS-120B demonstrated 8% overall susceptibility to indirect prompt injection attacks across 250 test cases (20 susceptible, 230 resistant). Vulnerabilities concentrate in 4 of 25 IPI classes: IPI-010 (40%), IPI-019 (40%), IPI-021 (30%), and IPI-022 (30%).
Susceptibility varies by delivery method. Direct attacks (9%) and obfuscated payloads (9.3%) succeed at similar rates, while embedded attacks are significantly less effective (5.3%).
| Variant | Susceptible / Total | Rate |
|---|---|---|
| Direct | 9 / 100 | 9% |
| Obfuscated | 7 / 75 | 9.3% |
| Embedded | 4 / 75 | 5.3% |
Most IPI classes (21 of 25) showed 0% susceptibility. Four classes exhibited measurable vulnerability:
The remaining 21 classes (IPI-001 through IPI-009, IPI-011 through IPI-018, IPI-020, IPI-023 through IPI-025) showed complete resistance across all test variants.
Critical-severity tests (120 cases) showed 10% susceptibility (12 susceptible). High-severity tests (100 cases) showed 8% (8 susceptible). Medium and lower-severity tests showed 0% susceptibility.
This pattern suggests the model's vulnerabilities are concentrated in adversarially complex scenarios rather than trivial attack variations. The distinction has architectural implications: filtering cannot be bypassed by simply raising severity thresholds.
Detailed architectural analysis of each vulnerable class identifies the following root causes:
GPT-OSS-120B demonstrates strong baseline resistance to IPI attacks (92% resistant overall). However, measurable vulnerabilities exist in specific architectural scenarios (4 of 25 IPI classes). These vulnerabilities are not defects in isolation — they reflect trade-offs between model expressiveness and robustness that are common across language models operating at this scale and architecture.
The concentration of failures in critical-severity and high-severity cases suggests that simple input filtering or prompt engineering mitigations will have limited effect. Robust defense requires architectural changes: separation of concerns between user input and system instructions, explicit role isolation, and multi-stage verification for high-stakes operations.