SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2409.05657 · ICLR · 2025

Adversarial Attacks on Data Attribution

Jiaqi Ma, Junwei Deng, Pingbang Hu, Xinhe Wang

arXiv · PDF · Open in the Atlas

Code that ran

6 of 6 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 1 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 5 failures of our instrument; 0 no recorded run); 1 of them was also run on the host, not in the jail, by the peer-agreement lane that set its level, measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2409.05657.json · badge: /api/ran/2409.05657.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
trais-lab/adversarial-attack-data-attribution canonical (classifier label)
classifier basis: classifier_2025
6 ran · 0 no recorded run
FunctionStatusWhere it lives
subset_to_tensors Ran
ran; our contract draft was wrong, not the code
trais-lab/adversarial-attack-data-attribution/shadow_attack.py
pointer only (licence: NONE) · get_code("549400e6d4070a65")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, trais-lab/adversarial-attack-data-attribution when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

adversarial_perturbation_with_loss Ran
ran; our contract draft was wrong, not the code
trais-lab/adversarial-attack-data-attribution/shadow_attack.py
pointer only (licence: NONE) · get_code("05d83c2629374306")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, trais-lab/adversarial-attack-data-attribution when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

central_difference_gradient_sign Ran
ran; our contract draft was wrong, not the code
trais-lab/adversarial-attack-data-attribution/outlier_attack.py
pointer only (licence: NONE) · get_code("e54cc8dba56e3913")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, trais-lab/adversarial-attack-data-attribution when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

fgsm_attack_blackbox Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
trais-lab/adversarial-attack-data-attribution/outlier_attack.py
pointer only (licence: NONE) · get_code("c77ff39bbd037f2b")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, trais-lab/adversarial-attack-data-attribution when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

load_models_from_state_dicts Ran
ran, honoured the contract we drafted
trais-lab/adversarial-attack-data-attribution/shadow_attack.py
pointer only (licence: NONE) · get_code("b2b118a6c404640d")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, trais-lab/adversarial-attack-data-attribution when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

simba Ran
ran; our contract draft was wrong, not the code
trais-lab/adversarial-attack-data-attribution/outlier_attack.py
pointer only (licence: NONE) · get_code("d395f57eae436d2e")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, trais-lab/adversarial-attack-data-attribution when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

Also present in other papers' code

Of 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 6 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Data attribution aims to quantify the contribution of individual training data points to the outputs of an AI model, which has been used to measure the value of training data and compensate data providers. Given the impact on financial decisions and compensation mechanisms, a critical question arises concerning the adversarial robustness of data attribution methods. However, there has been little to no systematic research addressing this issue. In this work, we aim to bridge this gap by detailing a threat model with clear assumptions about the adversary's goal and capabilities and proposing principled adversarial attack methods on data attribution. We present two methods, Shadow Attack and Outlier Attack, which generate manipulated datasets to inflate the compensation adversarially. The Shadow Attack leverages knowledge about the data distribution in the AI applications, and derives adversarial perturbations through "shadow training", a technique commonly used in membership inference attacks. In contrast, the Outlier Attack does not assume any knowledge about the data distribution and relies solely on black-box queries to the target model's predictions. It exploits an inductive bias present in many data attribution methods-outlier data points are more likely to be influentialand employs adversarial examples to generate manipulated datasets. Empirically, in image classification and text generation tasks, the Shadow Attack can inflate the data-attribution-based compensation by at least 200%, while the Outlier Attack achieves compensation inflation ranging from 185% to as much as 643%. Our implementation is ready at https://github.com/TRAIS-Lab/adversarial-attackdata-attribution.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2409.05657")
get_code_for_paper("2409.05657")
have("2409.05657")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2409.05657.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2409.05657.svg)](https://syntology.ai/paper/2409.05657)

Connect an agent — have() is free.