Efficiently Attacking Memorization Scores

Tue Do, Varun Chandrasekaran, Daniel Alabi
9/24/2025
cs.LG

Official code: tuedo2/MemAttack (0 stars, last commit 2025-09-16).

Abstract

Influence estimation tools -- such as memorization scores -- are widely used to understand model behavior, attribute training data, and inform dataset curation. However, recent applications in data valuation and responsible machine learning raise the question: can these scores themselves be adversarially manipulated? In this work, we present a systematic study of the feasibility of attacking memorization-based influence estimators. We characterize attacks for producing highly memorized samples as highly sensitive queries in the regime where a trained algorithm is accurate. Our attack (calculating the pseudoinverse of the input) is practical, requiring only black-box access to model outputs and incur modest computational overhead. We empirically validate our attack across a wide suite of image classification tasks, showing that even state-of-the-art proxies are vulnerable to targeted score manipulations. In addition, we provide a theoretical analysis of the stability of memorization scores under adversarial perturbations, revealing conditions under which influence estimates are inherently fragile. Our findings highlight critical vulnerabilities in influence-based attribution and suggest the need for robust defenses. All code can be found at https://github.com/tuedo2/MemAttack

View on arXivView PDF

Code Implementations(1)

tuedo2/MemAttackOfficial100%

TBD

00Python, Jupyter NotebookApr 24, 20251 years ago

Similar Papers

Cite this paper

@article{do2025efficiently,
  title  = {Efficiently Attacking Memorization Scores},
  author = {Tue Do and Varun Chandrasekaran and Daniel Alabi},
  year   = {2025},
  eprint = {2509.20463},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2509.20463v2}
}

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/2509.20463.svg)](https://codeofpaper.com/paper/2509.20463)

Discussion