Papers › Learn2Perturb: an End-to-end Feature Perturbation Learning to Improve Adversarial Robustness

Learn2Perturb: an End-to-end Feature Perturbation Learning to Improve Adversarial Robustness

2 Mar 2020CVPR 2020 6arXiv:2003.01090archive 2025-07-28

Ahmadreza Jeddi, Mohammad Javad Shafiee, Michelle Karg, Christian Scharfenberger, Alexander Wong

While deep neural networks have been achieving state-of-the-art performance across a wide variety of applications, their vulnerability to adversarial attacks limits their widespread deployment for safety-critical applications. Alongside other adversarial defense approaches being investigated, there has been a very recent interest in improving adversarial robustness in deep neural networks through the introduction of perturbations during the training process. However, such methods leverage fixed, pre-defined perturbations and require significant hyper-parameter tuning that makes them very difficult to leverage in a general fashion. In this study, we introduce Learn2Perturb, an end-to-end feature perturbation learning approach for improving the adversarial robustness of deep neural networks. More specifically, we introduce novel perturbation-injection modules that are incorporated at each layer to perturb the feature space and increase uncertainty in the network. This feature perturbation is performed at both the training and the inference stages. Furthermore, inspired by the Expectation-Maximization, an alternating back-propagation training algorithm is introduced to train the network and noise parameters consecutively. Experimental results on CIFAR-10 and CIFAR-100 datasets show that the proposed Learn2Perturb method can result in deep neural networks which are 4-7% more robust on l_∞ FGSM and PDG adversarial attacks and significantly outperforms the state-of-the-art against l₂ C&W attack and a wide range of well-known black-box attacks.

PaperPDFConference PDFCodeCode Syntology ran

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 6 code samples harvested from 1 repository linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 6 samples from 1 repository, 6 ran (6 with no instrument failure; 0 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-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Ahmadreza-Jeddi/Learn2Perturb mentioned on GitHubpytorchMITSyntology: 6 samples, 6 ran (0 instrument-failed) · 0 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

6 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 0 where Syntology's instrument failed) · 0 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.

6ran

Licence: 0 of the 6 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 Ahmadreza-Jeddi/Learn2Perturb. “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.

Ahmadreza-Jeddi/Learn2Perturb community (archive-listed) 6 samples, 6 ran (0 instrument-failed) · 0 unverified
EOT_FGSM attacks/eot.py ran MIT (permissive) · 58612379912d59c0 · report fixture: signature model:callable/0/?, data:Tensor/4/float, target:Tensor/1/int, epsilon:float/0/float, data_min:int/0/int, data_max:int/0/int, sample_size:int/0/int · returned Tensor · level recorded 2026-09-24
EOT_PGD attacks/eot.py ran MIT (permissive) · 2e013e2ceb5c8210 · report fixture: signature model:callable/0/?, data:Tensor/4/float, target:Tensor/1/int, epsilon:float/0/float, max_steps:int/0/int, lr:float/0/float, d_min:int/0/int, d_max:int/0/int, sample_size:int/0/int, random_start:bool/0/bool, advBNN:bool/0/bool · returned Tensor · level recorded 2026-09-24
fgsm in 14 papers attacks/fgsm.py ran MIT (permissive) · fd1f0b10f905c6a8 · report fixture: signature model:callable/0/?, data:Tensor/2/float, target:Tensor/1/int, epsilon:float/0/float, data_min:int/0/int, data_max:int/0/int · returned Tensor · level recorded 2026-09-24
grad_find attacks/eot.py ran MIT (permissive) · fbe5a39c0d5c5325 · report fixture: signature model:callable/0/?, data:Tensor/4/float, target:Tensor/1/int, sample_size:int/0/int · returned tuple · level recorded 2026-09-24
l2p_resnet_v2 models/resnet_v2.py ran MIT (permissive) · 7a3b2444fdf90e6e · report fixture: signature num_blocks:list/1/int, num_classes:int/0/int · returned L2P_ResNet_V2 · level recorded 2026-09-24
pgd in 18 papers attacks/pgd.py ran MIT (permissive) · e0919d109e7e3ae4 · report fixture: signature model:callable/0/?, data:Tensor/2/float, target:Tensor/1/int, epsilon:float/0/float, k:int/0/int, a:float/0/float, random_start:bool/0/bool, d_min:int/0/int, d_max:int/0/int · returned Tensor · level recorded 2026-09-24

Tasks

Adversarial DefenseAdversarial Robustness

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