Papers › Towards Evaluating the Robustness of Neural Networks

Towards Evaluating the Robustness of Neural Networks

16 Aug 2016arXiv:1608.04644archive 2025-07-28

Nicholas Carlini, David Wagner

Neural networks provide state-of-the-art results for most machine learning tasks. Unfortunately, neural networks are vulnerable to adversarial examples: given an input x and any target classification t, it is possible to find a new input x′ that is similar to x but classified as t. This makes it difficult to apply neural networks in security-critical areas. Defensive distillation is a recently proposed approach that can take an arbitrary neural network, and increase its robustness, reducing the success rate of current attacks' ability to find adversarial examples from 95% to 0.5%. In this paper, we demonstrate that defensive distillation does not significantly increase the robustness of neural networks by introducing three new attack algorithms that are successful on both distilled and undistilled neural networks with 100% probability. Our attacks are tailored to three distance metrics used previously in the literature, and when compared to previous adversarial example generation algorithms, our attacks are often much more effective (and never worse). Furthermore, we propose using high-confidence adversarial examples in a simple transferability test we show can also be used to break defensive distillation. We hope our attacks will be used as a benchmark in future defense attempts to create neural networks that resist adversarial examples.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1608.04644")

Code

Syntology Ran 3 of 13 code samples harvested from 6 repositories linked to this paper; 10 have no recorded run. Of those that ran: 1 ran · honoured contract; 2 ran · our draft was wrong.

By repository: community (archive-listed): 13 samples from 6 repositories, 3 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

27 repositories listed; official and paper-mentioned ones first.

Carco-git/CW_Attack_on_MNIST mentioned on GitHubpytorch report
LeMinhThong/blackbox-attack mentioned on GitHubpytorch report
MadryLab/cifar10_challenge mentioned on GitHubtfMIT report
OwenSec/DeepDetector mentioned on GitHubtf report
SifatMd/Research-Papers mentioned on GitHub report
abahram77/mnistChallenge mentioned on GitHubtf report
abahram77/mnist_challenge mentioned on GitHubtf report
bethgelab/cifar10_challenge mentioned on GitHubtf report
hope-yao/robust_attention_cifar mentioned on GitHubtf report
inspire-group/advml-traffic-sign mentioned on GitHubMIT report
jeromerony/adversarial-library mentioned on GitHubpytorch report
jfc43/pixel-discretization mentioned on GitHubtfApache-2.0 report
jfc43/robust-attribution-regularization mentioned on GitHubtfApache-2.0 report
khieu/cifar10_challenge mentioned on GitHubtf report
kkew3/pytorch-cw2 mentioned on GitHubpytorchMIT report
matanbt/attack-tabular mentioned on GitHub report
ukky17/invert_MV_pytorch mentioned on GitHubpytorch report
yevgm/deepadv3d mentioned on GitHubpytorch 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

13 samples harvested; 3 ran; 1 honoured the contract we drafted; 10 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · honoured contract
2ran · our draft was wrong
10unverified

Licence: 1 of the 13 samples is 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 6 repositories linked to this paper, official or community; each sample names its own and says which. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

generate_data Bhushan-Jagtap-2013/Adversarial_Attack_on_RNN/test_attack.py community (archive-listed) ran · our draft was wrong BSD-2-Clause (permissive) · ae7a589f65750d71 · report
generate_data carlini/nn_robust_attacks/test_attack.py community (archive-listed) ran · our draft was wrong BSD-2-Clause (permissive) · 33c3e5273c448151 · report
load_image zetongqi/attacking_neural_networks/CW_l2attack.py community (archive-listed) ran · honoured contract no licence file found · pointer only · 0cb12596aa3c0436 · report
activation PerryXDeng/adversarial_mnist_attacks/neural_network.py community (archive-listed) unverified MIT (permissive) · cc16b0d5bc15bb67 · report
cross_entropy PerryXDeng/adversarial_mnist_attacks/neural_network.py community (archive-listed) unverified MIT (permissive) · 39df9d693fbdc4de · report
denormalize PerryXDeng/adversarial_mnist_attacks/data_preparation.py community (archive-listed) unverified MIT (permissive) · 6c0b9095663ceff6 · report
get_cuda_state kkew3/pytorch-cw2/runutils.py community (archive-listed) unverified MIT (permissive) · ab527cad8796ffd2 · report
make_cuda_consistent kkew3/pytorch-cw2/runutils.py community (archive-listed) unverified MIT (permissive) · 9a04b87a21ee7dbd · report
normalize PerryXDeng/adversarial_mnist_attacks/data_preparation.py community (archive-listed) unverified MIT (permissive) · f33c321f1f8ee09c · report
predict kkew3/pytorch-cw2/runutils.py community (archive-listed) unverified MIT (permissive) · 6189cef972a4615e · report
preprocess jfc43/pixel-discretization/data-specific-discretization/ImageNet/util.py community (archive-listed) unverified Apache-2.0 (permissive) · 544bb80adbb9ade1 · report
sigmoid PerryXDeng/adversarial_mnist_attacks/neural_network.py community (archive-listed) unverified MIT (permissive) · cf589faab9919534 · report
vectorized_label PerryXDeng/adversarial_mnist_attacks/data_preparation.py community (archive-listed) unverified MIT (permissive) · aca0af8d07cfa276 · report

Tasks

Adversarial Attack

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