Papers › DiffAttack: Evasion Attacks Against Diffusion-Based Adversarial Purification
DiffAttack: Evasion Attacks Against Diffusion-Based Adversarial Purification
Mintong Kang, Dawn Song, Bo Li
Diffusion-based purification defenses leverage diffusion models to remove crafted perturbations of adversarial examples and achieve state-of-the-art robustness. Recent studies show that even advanced attacks cannot break such defenses effectively, since the purification process induces an extremely deep computational graph which poses the potential problem of gradient obfuscation, high memory cost, and unbounded randomness. In this paper, we propose a unified framework DiffAttack to perform effective and efficient attacks against diffusion-based purification defenses, including both DDPM and score-based approaches. In particular, we propose a deviated-reconstruction loss at intermediate diffusion steps to induce inaccurate density gradient estimation to tackle the problem of vanishing/exploding gradients. We also provide a segment-wise forwarding-backwarding algorithm, which leads to memory-efficient gradient backpropagation. We validate the attack effectiveness of DiffAttack compared with existing adaptive attacks on CIFAR-10 and ImageNet. We show that DiffAttack decreases the robust accuracy of models compared with SOTA attacks by over 20% on CIFAR-10 under ℓ_∞ attack (ϵ=8/255), and over 10% on ImageNet under ℓ_∞ attack (ϵ=4/255). We conduct a series of ablations studies, and we find 1) DiffAttack with the deviated-reconstruction loss added over uniformly sampled time steps is more effective than that added over only initial/final steps, and 2) diffusion-based purification with a moderate diffusion length is more robust under DiffAttack.
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="2311.16124")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2311.16124", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2311.16124")
Code
Syntology 24 code samples harvested from 2 repositories linked to this paper: 18 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 13 where Syntology's instrument failed) · 6 unverified. Where Syntology's instrument failed: 12 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 21 samples from 1 repository, 16 ran (5 with no instrument failure; 11 where Syntology's instrument failed); community: 3 samples from 1 repository, 2 ran (0 with no instrument failure; 2 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 11 of the 18 samples that ran have no recorded date.
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
24 samples harvested: 18 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 1 violated, 2 with no contract checked; 13 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 21 of the 24 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.
c3a6b977022957cb · report
fixture: signature in_channels:int/0/int · returned GroupNorm · level recorded, date not recorded census: 4 implementations from 14 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 DiffAttack_DDPM_Based/guided_diffusion/losses.py ran · our draft was wrong fingerprinted no licence file found · pointer only ·
cfd76fd0d89574a4 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded ad12a494674d23fb · report
fixture: signature model:callable/0/?, return_str:bool/0/bool · returned str · level recorded 2026-09-22 bd1f17e427bf51a5 · report
fixture: signature config:dict/0/? · returned Namespace · level recorded, date not recorded census: 6 implementations from 10 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 DiffAttack_DDPM_Based/guided_diffusion/losses.py ran · our draft was wrong no licence file found · pointer only ·
cd33283d615fb3d7 · report
fixture: signature x:Tensor/2/float, means:Tensor/2/float, log_scales:Tensor/2/float · returned Tensor · level recorded, date not recorded 8ff7c24dade9904c · report
fixture: signature config:Config/0/?, params:generator/0/? · returned Adam · level recorded 2026-09-24 fac494cec4301110 · report
fixture: signature sde:StandInSDE/0/?, train:bool/0/bool, reduce_mean:bool/0/bool, continuous:bool/0/bool, likelihood_weighting:bool/0/bool, eps:float/0/float · returned function · level recorded 2026-09-24 census: 11 implementations from 15 papers, 5 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 1, kind int, dtype int64 DiffAttack_DDPM_Based/ddpm/unet_ddpm.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant no licence file found · pointer only ·
cb49209c125de1b4 · report
fixture: signature timesteps:Tensor/1/int, embedding_dim:int/0/int · returned Tensor · level recorded, date not recorded 195d635db8eb778b · report
fixture: signature a:Tensor/1/float, b:Tensor/1/float, t:Tensor/1/float · returned Tensor · level recorded 2026-09-24 d5eb57879ef1704e · report
fixture: signature state_dict:dict/0/? · returned int · level recorded 2026-09-24 census: 4 implementations from 11 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 DiffAttack_DDPM_Based/ddpm/unet_ddpm.py ran · our draft was wrong fingerprinted no licence file found · pointer only ·
3137073275f8c21a · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded census: 14 implementations from 24 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 · arg 4: rank 2, kind float, dtype float32 DiffAttack_DDPM_Based/guided_diffusion/losses.py ran · honoured contract fingerprinted no licence file found · pointer only ·
cf2798b666b231ca · report
fixture: signature mean1:Tensor/2/float, logvar1:Tensor/2/float, mean2:Tensor/2/float, logvar2:Tensor/2/float · returned Tensor · level recorded 2026-09-22 366bb8c7035a2fc8 · report
fixture: signature config:Config/0/? · returned function · level recorded 2026-09-24 a05b1d0cf3f508b4 · report
fixture: signature cls:callable/0/?, name:NoneType/0/? · returned type · level recorded, date not recorded 473066ddf62a075a · report
fixture: signature cls:callable/0/?, name:NoneType/0/? · returned type · level recorded, date not recorded 7c508037b40522af · report
fixture: signature v:str/0/str · returned bool · level recorded, date not recorded d84e0830078f5a50 · report
8749fc2e6cd3b1c8 · report
2cd3e1d64ab9a5bb · report
0dd156dfa78cac88 · report
a58facb8fe71823a · report
ecfdcb7de66cc30f · report
fixture: returned Tensor · level recorded, date not recorded census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket diff_latent_attack.py ran · our draft was wrong Apache-2.0 (permissive) ·
fa609ac1c290e653 · report
fixture: returned Tensor · level recorded, date not recorded f2778069fba3bee4 · report
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 DiffAttack (graph method: DiffAttack). 5 bricks; individually on a fixture: 2 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 3 unverified. The assembly has not been run end-to-end.
- DiffAttack entry · level 0 · unverified ·
d84e0830078f5a50 - Logger helper · level 1 · ran ·
b468449dd9f01141 - check_randomized helper · level 0 · unverified ·
8749fc2e6cd3b1c8 - check_square_sr helper · level 0 · unverified ·
2cd3e1d64ab9a5bb - L2_norm helper · level 1 · ran; the contract check could not run ·
fa19820305aabe1d
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="2311.16124") 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.
Methods
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