Unit 42 locates Qwen3-4B's refusal template in 50 of 350,208 neurons
Perturbation probing needs the weights, which puts the finding on teams running open-source checkpoints rather than on API tenants. The same 50-neuron toolkit that breaks a refusal template also repairs other behavior.
The Watch · Security desk
What happened
- Unit 42 published a method it calls perturbation probing, which uses two forward passes per prompt to pin a target behavior such as harmful-request refusal to specific feed-forward neurons.
- On the open-source Qwen3-4B model, the method located the safety refusal template in 50 neurons out of 350,208, about 0.014% of the feed-forward layer.
- On Qwen3.5-2B, editing 20 neurons dropped false agreement with users in multi-turn conversation from 36.7% to zero across 30 questions.
Why it matters
- Who's exposed exposure Risk here sorts by who holds the checkpoint: anyone with read access to an open-weight model inherits the ability to strip its refusal layer, while API-only tenants have no path to the neurons at all.
- What it limits constraint Refusal behavior concentrated this tightly is hard to cite as a control in an audit, because an ordinary fine-tune can move it and nothing in the usual deployment pipeline measures that drift.
- Who has to decide decision Buyers can now ask a model vendor for a fragility number computed before any red-team campaign, which changes what counts as an adequate answer about alignment robustness.
- What's now possible capability Neuron-level editing becomes a behavior knob rather than only a removal tool, putting small unaudited behavioral patches within reach of any team that holds weights.
Perturbation probing's threat model is narrower than the headline number suggests. It operates on weights: two forward passes per prompt, reading and then disabling specific feed-forward neurons [1]. An API tenant calling a hosted model cannot reach a neuron. A team that pulled Qwen3-4B down, fine-tuned it, and put it behind a support chatbot owns all 350,208 of them [6], and so does anyone who gets read access to that checkpoint.
Cost is trivial. Two passes per prompt across the 520-prompt benchmark Unit 42 used comes to 1,040 forward passes [15], on a 4B model. Nothing there requires a research budget.
The part that lands on defenders who will never be attacked this way is Unit 42's aside that a normal optimization run could shift the same layer [5]. If the refusal template sits in roughly one neuron in 7,004 [14], routine fine-tuning can degrade it as a side effect, with no adversary involved and no signal in any deployment pipeline that currently checks for it.
The measurement here is specific: ablating the 50 neurons changed the response format on 80% of the 520 harmful prompts [2], which is 416 prompts [11], and the result held on 200 prompts of a second benchmark [2]. Format change means the refusal template broke. The post does not report a harmful-completion rate for the ablated model. Bypass was the subject of the earlier logit-gap steering work, which got past guardrails by closing a measurable gap in the model's output scores [8]. This paper answers where the behavior lives, and stops there.
The sycophancy result is directionally clean and thin. 36.7% of 30 questions is 11 questions [12]; 20 neurons took those 11 to zero on Qwen3.5-2B [3]. Thirty questions is a demonstration, not a rate.
The same lever pushes the other way. Amplifying 10 identified neurons moved factual self-correction from 52% to 88% on 200 TruthfulQA prompts with no retraining [4], which is 104 prompts to 176 [13].
The durable contribution is the FFN/Skip ratio: seconds to compute per model, and across the 13 models tested it explained 81% of the variance in how much a small targeted change moved safety behavior [16]. That is a procurement-usable number if the per-model values get published, and the blog post names only Qwen3-4B and Qwen3.5-2B, with the method in an arXiv paper [9]. The recommendation stacked on top, external content filters and runtime guardrails rather than trust in trained-in refusal [7], is standard defense in depth, and Unit 42 closes with its own product, Prisma AIRS Runtime Security, as the tool it points to for that job [10].
What to watch
- Whether the arXiv paper publishes per-model FFN/Skip ratios for all 13 models tested, which is what would make the score usable in model selection.
- Whether an independent group reproduces the 50-neuron ablation and reports harmful-completion rates rather than response-format change.
- Whether fine-tuning platforms start measuring refusal drift after a customer training run, given Unit 42's claim that ordinary optimization can move the same layer.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence42
- Adoption
- Insufficient
- Hype gap+30
- Incentives80
- Confidence45
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Unit 42 introduced a method called perturbation probing that uses two forward passes per prompt, at significantly lower computational cost than prior approaches, to identify the small set of feed-forward neurons causally responsible for a targeted behavior such as refusing harmful requests.
- [2]
Removing those 50 neurons changed the response format on 80% of 520 standard harmful-prompt benchmark items, and the result was replicated on 200 prompts of a second standard benchmark.
- [3]
On the smaller model Qwen3.5-2B, 20 neurons were enough to stop the model from falsely agreeing with users in multi-turn conversations, dropping that behavior from 36.7% to 0% across 30 questions.
- [4]
Amplifying 10 identified neurons on a small model improved factual self-correction from 52% to 88% on 200 TruthfulQA prompts without any retraining.
- [5]
Unit 42 states that refusal behavior lives in a thin template layer that an attacker able to manipulate internals could disable, and that even a normal optimization run could shift it.
- [6]
On the open-source LLM Qwen3-4B, 50 neurons out of 350,208 feed-forward neurons, about 0.014%, control the safety refusal template.
- [7]
Unit 42 calls reliance on that thin layer alone the LLM analog of relying on a single perimeter firewall, and argues for defense in depth with external content filters and runtime guardrails layered on top of the base model's training.
- [8]
Unit 42's earlier logit-gap steering research showed that the safety guardrails of an aligned LLM can be bypassed by closing a measurable gap in the model's output scores.
- [9]
The full method is published on arXiv as "Perturbation Probing: A Two-Pass-per-Prompt Diagnostic for FFN Behavioral Circuits in Aligned LLMs"; the blog post names only Qwen3-4B and Qwen3.5-2B among the models tested.
- [10]
The post closes by stating that for organizations deploying LLMs today, Palo Alto's Prisma AIRS Runtime Security provides the external content filters and inline guardrails the thin template layer cannot.
- [11]
80% of the 520-prompt harmful benchmark is 416 prompts on which the response format changed.
- [12]
36.7% of 30 questions is about 11 questions, so the 20-neuron edit eliminated false agreement on roughly 11 items.
- [13]
On 200 TruthfulQA prompts, 52% to 88% is a move from 104 prompts to 176, an increase of 72.
- [14]
50 controlling neurons out of 350,208 feed-forward neurons is roughly one neuron in 7,004.
- [15]
Running the two-pass method over the 520-prompt benchmark costs 1,040 forward passes.
- [16]
The same computation yields an FFN/Skip ratio, a single number computable in seconds per model, which across the 13 models tested explained 81% of the variance in how vulnerable each model's safety behavior was to a small targeted change.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- unit42.paloaltonetworks.comPerturbation Probing: A New Diagnostic for the Fragility of LLM Safety
1 article · August 28, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- AI Runtime GuardrailsFollow
- Open-Weight Model RiskFollow
- LLM Alignment RobustnessFollow
- Mechanistic interpretabilityFollow
- Vendor-published security researchFollow