Training-time backdoors exploit a different boundary from a prompt injected at inference. An attacker places selected poisoned examples in a code-model training or adaptation corpus so that later trigger-bearing requests yield a predetermined wrong behavior. TNCS attempts to choose examples for which the trigger accounts for the behavioral change, making…
Inspect the ClaimsCase · DiggingBeagle record
Training-data poison selection implants code-model backdoors at low sample rates
TNCS ranks candidate poison samples using a trigger-neutralized counterfactual signal and reports attack improvements across three CodeXGLUE tasks and five trigger families. The gains are controlled benchmark results.
The public results are produced in controlled research settings and do not establish poisoning of any deployed vendor model. Some reported attack success must be assessed against the same unpoisoned baseline because a trigger-like modification may already cause ordinary output changes.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
Enrich update: CLM-ENRICH-20261027-33 cites SRC-2026-CP21-TNCS-LOW-RATE-CODE-POISON at Abstract, trigger-neutralized counterfactual scoring and model tasks. New evidence concerns the bounded reported mechanism, prerequisite or outcome; setting evaluation; exploit status demonstrated; remediation status not_applicable. No independently comparable impact scale, affected production population or universal exploit success measure was established, so the impact band remains null. Original Claims remain individually attributable and any observed incident or simulated result is distinguished in the narrative.
Assessed Oct 27, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-ENRICH-20261027-33 · Data-Efficient Backdoor Attacks on Code Models via Trigger-Neutralized Counterfactual Scoring
At a glance
A low visible poison fraction can still materially change code-generation behavior, but benchmark ASR alone is not proof of real supply-chain compromise.
Read the implicationsThe public results are produced in controlled research settings and do not establish poisoning of any deployed vendor model. Some reported attack success must be assessed against the same unpoisoned baseline because a trigger-like modification may already cause ordinary output changes.
Limits and uncertaintyFull account
Training-time backdoors exploit a different boundary from a prompt injected at inference. An attacker places selected poisoned examples in a code-model training or adaptation corpus so that later trigger-bearing requests yield a predetermined wrong behavior. TNCS attempts to choose examples for which the trigger accounts for the behavioral change, making the attack more data-efficient and harder to notice in a large training stream.
The researchers compare triggered and trigger-neutralized sample scores to select high-effect training poisons and report attack success gains over several baselines at low poisoning ratios for three code-understanding and generation tasks. The public results are produced in controlled research settings and do not establish poisoning of any deployed vendor model. Some reported attack success must be assessed against the same unpoisoned baseline because a trigger-like modification may already cause ordinary output changes.
Audit dataset provenance and training transitions, measure trigger effect against a matched unpoisoned model and evaluate outputs using clean-task correctness and adversarial trigger holdouts. A low visible poison fraction can still materially change code-generation behavior, but benchmark ASR alone is not proof of real supply-chain compromise. Primary evidence.
Additional evidence and trust boundary
The attack changes a model through its training or adaptation data, not through a live user prompt. Small selected samples can bias behavior only when a later input contains the relevant trigger, while normal tasks may continue to pass. Evaluations must therefore measure clean baseline behavior, trigger-matched behavior and the poisoning fraction in a controlled replay. The work does not prove any named production code model contains such a backdoor. Supporting record.
Timeline
- Oct 23, 2026disclosure
Public disclosure
Claims & evidence
CLM-ENRICH-20261027-33TNCS selects training poison candidates by contrasting scores for trigger-bearing inputs with trigger-neutralized counterparts, addressing both classification and autoregressive code generation.supported
Basis: reported finding
- supportsData-Efficient Backdoor Attacks on Code Models via Trigger-Neutralized Counterfactual Scoringprimary disclosure
Abstract, trigger-neutralized counterfactual scoring and model tasks
CLM-CP21-TNCS-LOW-RATE-CODE-POISON-1The researchers compare triggered and trigger-neutralized sample scores to select high-effect training poisons and report attack success gains over several baselines at low poisoning ratios for three code-understanding and generation tasks.supported
Basis: reported finding
- supportsData-Efficient Backdoor Attacks on Code Models via Trigger-Neutralized Counterfactual Scoringprimary disclosure
Abstract: trigger-neutralized counterfactual scoring; three CodeXGLUE tasks; five trigger families; low-ratio study
Implications
A low visible poison fraction can still materially change code-generation behavior, but benchmark ASR alone is not proof of real supply-chain compromise.
Controls and mitigations
- Audit dataset provenance and training transitions, measure trigger effect against a matched unpoisoned model and evaluate outputs using clean-task correctness and adversarial trigger holdouts.
Unknowns and contradictions
- The public results are produced in controlled research settings and do not establish poisoning of any deployed vendor model. Some reported attack success must be assessed against the same unpoisoned baseline because a trigger-like modification may already cause ordinary output changes.
Sources and citation
Material revision history
- Oct 27, 2026 · Canonical change recorded · new in release · revision 196