Backend
How to Backdoor Image Knowledge Distillation
arXiv cs.CR0 views
arXiv:2504.21323v4 Announce Type: replace Abstract: Knowledge distillation is widely used to transfer behavior from a large teacher model to a smaller student. It is often assumed to be safe when the teacher is clean, because classic backdoor attacks rely on poisoned labels and triggers in supervised training, whereas distillation trains the student to match a teacher's outputs. We show that this assumption can fail when the distillation dataset itself is poisoned. Our attack injects triggered and manipulated images that a clean teacher already predicts as an attacker chosen target label, which causes the student to learn a backdoor even though the teacher remains unaffected. We evaluate this threat across multiple manipulation strategies, including targeted adversarial perturbations and targeted GAN based class transitions, and study how distillation settings influence both accuracy and attack success. We show that the attack remains effective even at a 10% poisoning rates. The results demonstrate that a clean teacher alone is not a sufficient safeguard: poisoned distillation data can produce a strongly backdoored student while maintaining competitive performance on clean images. These findings show that the integrity and provenance of distillation data are part of the security boundary of data intensive KD pipelines, even when the teacher itself is trusted.
Source:https://arxiv.org/abs/2504.21323PreviousOP-Print: Tracing Membership Imprints in On-Policy Self-DistillationNextAn Orchestrated Sandbox for Side-Channel Analysis of Cyber-Physical Systems Malware
Related posts
How to Calculate Your Freelance Floor Rate (and Turn It Into a Fixed-Price Quote)
0dev.to Beginners
Pinterest Impressions Dropped Overnight: Causes And A Recovery Plan For Bloggers
0dev.to Beginners
Cómo hacer copias de seguridad sin complicarte la vida
0dev.to Beginners
Bug of the week #1: you can edit your profile. Can you reach the admin page?
0dev.to Beginners
Node.js vs. Django: What's the Difference?
0dev.to Node
Node.js randomInt cache persistence in snapshots: scope and limits
0dev.to Node