Papers › Progressive-Scale Boundary Blackbox Attack via Projective Gradient Estimation

Progressive-Scale Boundary Blackbox Attack via Projective Gradient Estimation

10 Jun 2021arXiv:2106.06056archive 2025-07-28

Jiawei Zhang, Linyi Li, Huichen Li, Xiaolu Zhang, Shuang Yang, Bo Li

Boundary based blackbox attack has been recognized as practical and effective, given that an attacker only needs to access the final model prediction. However, the query efficiency of it is in general high especially for high dimensional image data. In this paper, we show that such efficiency highly depends on the scale at which the attack is applied, and attacking at the optimal scale significantly improves the efficiency. In particular, we propose a theoretical framework to analyze and show three key characteristics to improve the query efficiency. We prove that there exists an optimal scale for projective gradient estimation. Our framework also explains the satisfactory performance achieved by existing boundary black-box attacks. Based on our theoretical framework, we propose Progressive-Scale enabled projective Boundary Attack (PSBA) to improve the query efficiency via progressive scaling techniques. In particular, we employ Progressive-GAN to optimize the scale of projections, which we call PSBA-PGAN. We evaluate our approach on both spatial and frequency scales. Extensive experiments on MNIST, CIFAR-10, CelebA, and ImageNet against different models including a real-world face recognition API show that PSBA-PGAN significantly outperforms existing baseline attacks in terms of query efficiency and attack success rate. We also observe relatively stable optimal scales for different models and datasets. The code is publicly available at https://github.com/AI-secure/PSBA.

PaperPDFCodeCode Syntology ranMethod as code

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):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 4 honoured, 0 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 3 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 8 ran (4 with no instrument failure; 4 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. 2 of the 8 samples that ran have no recorded date.

AI-secure/PSBA officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 8 ran (4 instrument-failed) · 1 unverified report

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

9 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 4 honoured, 0 violated, 0 with no contract checked; 4 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.

4ran · honoured contract
1ran · our draft was wrong
3ran; the contract check could not run
1unverified

Licence: 9 of the 9 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 AI-secure/PSBA. “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.

AI-secure/PSBA official repository 9 samples, 8 ran (4 instrument-failed) · 1 unverified
MSE in 28 papers src/main_pytorch_multi.py ran · honoured contract fingerprinted no licence file found · pointer only · b3373b027f45777c · report fixture: signature x1:Tensor/2/float, x2:Tensor/2/float · returned Tensor · level recorded, date not recorded
RGB_img_dct src/models/pgan_generator.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 32d626ea74126c1a · report fixture: signature img:ndarray/3/float · returned ndarray · level recorded 2026-09-22
RGB_signal_idct src/models/pgan_generator.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · cb8239520dd90350 · report fixture: signature signal:ndarray/3/float · returned ndarray · level recorded 2026-09-22
Upscale2d src/models/pgan_generator.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · e74d4df2f9edad00 · report fixture: signature x:Tensor/4/float, factor:int/0/int · returned Tensor · level recorded 2026-09-22
get_2d_dct src/models/pgan_generator.py ran · honoured contract fingerprinted no licence file found · pointer only · 57608d126fb352b7 · report fixture: signature x:ndarray/2/float · returned ndarray · level recorded 2026-09-22
get_2d_idct src/models/pgan_generator.py ran · honoured contract fingerprinted no licence file found · pointer only · 32a3197e287f430f · report fixture: signature x:ndarray/2/float · returned ndarray · level recorded 2026-09-22
load_img in 47 papers src/main_api_attack.py ran · honoured contract no licence file found · pointer only · 5f2019cf9c5ca9eb · report fixture: signature path:str/0/str · returned ndarray · level recorded, date not recorded
num_flat_features src/models/pgan_generator.py ran · our draft was wrong no licence file found · pointer only · f9e64946b23edb51 · report fixture: signature x:Tensor/4/float · returned int · level recorded 2026-09-22
PGenerator src/models/pgan_generator.py unverified no licence file found · pointer only · 4f33a0750fbf46a9 · 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. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. 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. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model".

2 assemblies on this paper: 1 harvested, 1 generated.

generated Assembly for PSBA-PGAN (graph method: PSBA-PGAN), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 0 ran · 1 unverified. Its end-to-end level was lowered from level 3 to level 0 on 2026-09-10 (level 0: no end-to-end run is now recorded); Syntology's graph records why: “lowered to the entry brick level: a single-routine assembly IS its brick”.

label matches by construction: the code was generated for this method (not judged by a model)

  1. frequency_reduction_gradient_estimation entry · level 0 · unverified · 9c2d18b4ca359e8090c623c5715264e4d66151a9ea44bb0038ded8243894831d

harvested Assembly for PSBA-PGAN (graph method: PSBA-PGAN). 12 bricks; individually on a fixture: 11 ran (of which 3 constructed an object rather than computing a result; 7 with no instrument failure: 3 honoured, 0 violated, 4 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. PGenerator entry · level 0 · unverified · 4f33a0750fbf46a9
  2. EqualizedConv2d helper · level 1 · ran · 5cf59a4da6518f68
  3. EqualizedLinear helper · level 1 · ran · 8fe50b1ef4b73156
  4. NormalizationLayer helper · level 1 · ran · 980e0408abbfddd2
  5. RGB_img_dct data_transform · level 1 · ran; the contract check could not run (RAISES) · 32d626ea74126c1a
  6. RGB_signal_idct data_transform · level 1 · ran; the contract check could not run (RAISES) · cb8239520dd90350
  7. Upscale2d helper · level 1 · ran; the contract check could not run (RAISES) · e74d4df2f9edad00
  8. num_flat_features helper · level 1 · ran · our draft was wrong · f9e64946b23edb51
  9. ConstrainedLayer helper · level 1 · ran · d3073e6a07526cac
  10. get_2d_dct helper · level 1 · ran · honoured contract · 57608d126fb352b7
  11. get_2d_idct helper · level 1 · ran · honoured contract · 32a3197e287f430f
  12. getLayerNormalizationFactor helper · level 1 · ran · honoured contract · 8dd3d0253826c3e4

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="2106.06056") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Face Recognition

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