Papers › Game-Theoretic Unlearnable Example Generator
Game-Theoretic Unlearnable Example Generator
Shuang Liu, Yihan Wang, Xiao-Shan Gao
Unlearnable example attacks are data poisoning attacks aiming to degrade the clean test accuracy of deep learning by adding imperceptible perturbations to the training samples, which can be formulated as a bi-level optimization problem. However, directly solving this optimization problem is intractable for deep neural networks. In this paper, we investigate unlearnable example attacks from a game-theoretic perspective, by formulating the attack as a nonzero sum Stackelberg game. First, the existence of game equilibria is proved under the normal setting and the adversarial training setting. It is shown that the game equilibrium gives the most powerful poison attack in that the victim has the lowest test accuracy among all networks within the same hypothesis space, when certain loss functions are used. Second, we propose a novel attack method, called the Game Unlearnable Example (GUE), which has three main gradients. (1) The poisons are obtained by directly solving the equilibrium of the Stackelberg game with a first-order algorithm. (2) We employ an autoencoder-like generative network model as the poison attacker. (3) A novel payoff function is introduced to evaluate the performance of the poison. Comprehensive experiments demonstrate that GUE can effectively poison the model in various scenarios. Furthermore, the GUE still works by using a relatively small percentage of the training data to train the generator, and the poison generator can generalize to unseen data well. Our implementation code can be found at https://github.com/hong-xian/gue.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2401.17523")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2401.17523", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2401.17523")
Code
Syntology 8 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 6 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 8 samples from 1 repository, 7 ran (1 with no instrument failure; 6 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 8 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from hong-xian/gue. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
1c2bb8bacd5c71a1 · report
fixture: signature x:Tensor/4/float · returned Tensor · level recorded 2026-09-22 f6362fad9eb59b64 · report
fixture: signature num_classes:int/0/int · returned ResNet · level recorded 2026-09-22 931ee4a531e00798 · report
fixture: signature args:Args/0/? · returned ResNet · level recorded 2026-09-22 census: 17 implementations from 15 papers, 17 distinct outputs across 7 buckets, one shared input per bucket gue.py ran · our draft was wrong no licence file found · pointer only ·
2cd493567e71bb78 · report
fixture: signature args:Args/0/?, clsmodel:callable/0/?, x:Tensor/2/float, y:Tensor/1/int · returned Tensor · level recorded 2026-09-22 d029dd9f6731ca43 · report
fixture: signature args:Args/0/?, clsmodel:callable/0/?, x:Tensor/2/float, y:Tensor/1/int, retain_graph:bool/0/bool, create_graph:bool/0/bool · returned tuple · level recorded 2026-09-22 census: 6 implementations from 6 papers, 6 distinct outputs across 3 buckets, one shared input per bucket gue.py ran · our draft was wrong no licence file found · pointer only ·
f38767d36eae77a4 · report
fixture: signature args:Args/0/?, atkmodel:callable/0/?, clsmodel:callable/0/?, x:Tensor/2/float, y:Tensor/1/int · returned Tensor · level recorded 2026-09-22 c79c2bb39de6cf5f · report
fixture: signature args:Args/0/?, atkmodel:callable/0/?, clsmodel:callable/0/?, tmpmodel:callable/0/?, x:Tensor/2/float, y:Tensor/1/int, retain_graph:bool/0/bool, create_graph:bool/0/bool · returned tuple · level recorded 2026-09-22 Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.
1 assembly on this paper: 1 harvested, 0 generated.
harvested Assembly for Game Unlearnable Example (GUE) (graph method: Game Unlearnable Example (GUE)). 9 bricks; individually on a fixture: 8 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 6 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.
- bome entry · level 0 · unverified ·
ad233e253082b05d - create_net model · level 1 · ran · our draft was wrong ·
931ee4a531e00798 - f_theta loss · level 1 · ran · our draft was wrong ·
d029dd9f6731ca43 - g helper · level 1 · ran · our draft was wrong ·
f38767d36eae77a4 - q_a_theta loss · level 1 · ran · our draft was wrong ·
c79c2bb39de6cf5f - ResNet18 helper · level 1 · ran · our draft was wrong ·
f6362fad9eb59b64 - f helper · level 1 · ran · our draft was wrong ·
2cd493567e71bb78 - BasicBlock helper · level 1 · ran ·
e33f907725fe74f0 - ResNet helper · level 1 · ran ·
1c2bb8bacd5c71a1
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2401.17523") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections