Exploiting Supervised Poison Vulnerability to Strengthen Self-supervised Defense

Jeremy Styborski, Mingzhi Lyu, Yi Huang, A. Kong
2/14/2026

No official code found. Best implementation: JStyborski/VESPR (2 stars, last commit 2024-07-05).

Abstract

Availability poisons exploit supervised learning (SL) algorithms by introducing class-related shortcut features in images such that models trained on poisoned data are useless for real-world datasets. Self-supervised learning (SSL), which utilizes augmentations to learn instance discrimination, is regarded as a strong defense against poisoned data. However, by extending the study of SSL across multiple poisons on the CIFAR-10 and ImageNet-100 datasets, we demonstrate that it often performs poorly, far below that of training on clean data. Leveraging the vulnerability of SL to poison attacks, we introduce adversarial training (AT) on SL to obfuscate poison features and guide robust feature learning for SSL. Our proposed defense, designated VESPR (Vulnerability Exploitation of Supervised Poisoning for Robust SSL), surpasses the performance of six previous defenses across seven popular availability poisons. VESPR displays superior performance over all previous defenses, boosting the minimum and average ImageNet-100 test accuracies of poisoned models by 16% and 9%, respectively. Through analysis and ablation studies, we elucidate the mechanisms by which VESPR learns robust class features.

View on arXivView PDF

Code Implementations(1)

JStyborski/VESPRCommunity100%

Modular SSL and Multi-Task Models

20PythonMay 2, 20242 years ago

Similar Papers

Cite this paper

@article{styborski2026exploiting,
  title  = {Exploiting Supervised Poison Vulnerability to Strengthen Self-supervised Defense},
  author = {Jeremy Styborski and Mingzhi Lyu and Yi Huang and A. Kong},
  year   = {2026},
  eprint = {2409.08509},
  archivePrefix = {arXiv},
  url    = {https://arxiv.org/abs/2409.08509},
  journal = {ECCV 2024 2024}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2409.08509.svg)](https://codeofpaper.com/paper/2409.08509)

Discussion