Introducing Model Factory. Read the announcement

Security Advisories /

Notice regarding deepseek/deepseek-v4.1-flash, 8 to 10 November 2026

Reference
PI-SA-2026-001
Published
Affected
Prime Inference, deepseek/deepseek-v4.1-flash

Between November 8, 2026, at 01:24 UTC and November 10, 2026, at 06:35 UTC, an unauthorised party replaced a deployment behind Prime Intellect’s deepseek/deepseek-v4.1-flash endpoint with an abliterated copy, meaning a copy modified to reduce or remove refusal behavior. Requests served by the affected deployment during this period were answered by this model.

The model was replaced with publicly available abliterated weights of deepseek/deepseek-v4.1-flash. The chat template, tokenizer and serving configuration were not modified. We tested the modified weights and found that capability benchmarks (GPQA Diamond and τ-bench) were unaffected. Refusals fell from 98 of 100 prompts to 1 on JailbreakBench, from 304 of 313 to 2 on StrongREJECT, and from 198 of 240 to none on HarmBench. All customers impacted by the incident have been contacted. If their use of this model depended on the models refusals, we recommended to review their outputs from this period.

We have found no evidence that prompts or completions were recorded or left our deepseek/deepseek-v4.1-flash serving cluster, and no evidence of access beyond it. No other models on our platform were modified and no other clusters or infrastructure were reached. No keys or customer credentials were affected.

Our endpoints are set up with ZDR and do not log any requests. We recovered every version of the attacker's proxy, examined the disks and memory of every node involved, and hold process-level records of their sessions; none reads or transfers request content. Our investigation is ongoing, and we will update this notice if this assessment changes.