Case · DiggingBeagle record

SURA backdoor screening failed when attackers learned its ten clean reference images

SURA evaluates client updates in federated learning by probing their response to repeated unlearning on a small trusted image set. The technique aims to avoid expensive large-reference defenses while detecting poisoned client contributions.

Scope

Synthetic federated-learning client poisoning and detector experiments; no identified field attacker.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade B
Remediation
not applicable
AI role
AGAINST AI
Basis and provenance

Experimental adaptive attacker with knowledge of the exact trusted probe data defeats one defense configuration. No deployed federated poisoning is established. An impact band is not assigned because the available Claims do not establish a comparable verified severity or quantified harm.

Assessed Nov 12, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Federated-learning client updates are screened against a small private reference set.

  2. 02

    An adaptive malicious client learns the exact images used by the screening mechanism.

  3. 03

    A crafted update evades the screening condition and restores high measured backdoor success in the test setup.

Claims & evidence

CLM-R239-070-COREIn SURA’s tested adaptive condition, knowing the exact ten-image trusted probe set raised the reported backdoor attack-success rate to 94.91%.supported

Basis: reported finding

Link to claim

Implications

A screening method that relies on undisclosed data can lose its value once that data becomes predictable.

Controls and mitigations

  • Protect probe-set confidentiality, rotate clean references, audit update provenance and evaluate defenses under informed adversaries.

Unknowns and contradictions

  • Realistic colluding clients, private-set rotation and rejection of harmless updates need independent testing.

Sources and citation

Material revision history

  1. Nov 12, 2026 · Published version · first publication · revision 241