SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1905.02175 · 2019

Adversarial Examples Are Not Bugs, They Are Features

Logan Engstrom, Andrew Ilyas, Shibani Santurkar, Dimitris Tsipras, Mit, Brandon Tran

arXiv · PDF · Open in the Atlas

Code that ran

2 of 2 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/1905.02175.json · badge: /api/ran/1905.02175.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
ndb796/pytorch-adversarial-training-cifar reimplementation (classifier label)
classifier basis: classifier_2025
2 ran · 0 no recorded run
FunctionStatusWhere it lives
mixup_criterion Ran
ran; our contract draft was wrong, not the code
ndb796/pytorch-adversarial-training-cifar/interpolated_adversarial_training.py
pointer only (licence: NONE) · get_code("33ba52fc17e89516")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ndb796/pytorch-adversarial-training-cifar when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

mixup_data Ran
ran; our contract draft was wrong, not the code
ndb796/pytorch-adversarial-training-cifar/interpolated_adversarial_training.py
pointer only (licence: NONE) · get_code("11b0ec76b88d8553")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, ndb796/pytorch-adversarial-training-cifar when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

Also present in other papers' code

Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 2 are also present in other papers whose code we hold (2 with at least one paper dated earlier, 0 the same month, 2 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

FunctionAlso present inEarliest-datedOthers named
mixup_criterion 14 other papers
1 dated earlier, 13 later
1706.06083 (2017-06)
Towards Deep Learning Models Resistant to Adversarial Attacks
1906.06784 (2019-06)
Interpolated Adversarial Training: Achieving Robust Neural Networks without Sacrificing Too Much Accuracy
1908.09699 (2019-08)
Gated Convolutional Networks with Hybrid Connectivity for Image Classification
and 11 more not named here
mixup_data 2 other papers
1 dated earlier, 1 later
1706.06083 (2017-06)
Towards Deep Learning Models Resistant to Adversarial Attacks
1906.06784 (2019-06)
Interpolated Adversarial Training: Achieving Robust Neural Networks without Sacrificing Too Much Accuracy

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Adversarial examples have attracted significant attention in machine learning, but the reasons for their existence and pervasiveness remain unclear. We demonstrate that adversarial examples can be directly attributed to the presence of non-robust features: features (derived from patterns in the data distribution) that are highly predictive, yet brittle and (thus) incomprehensible to humans. After capturing these features within a theoretical framework, we establish their widespread existence in standard datasets. Finally, we present a simple setting where we can rigorously tie the phenomena we observe in practice to a misalignment between the (human-specified) notion of robustness and the inherent geometry of the data.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("1905.02175")
get_code_for_paper("1905.02175")
have("1905.02175")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/1905.02175.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/1905.02175.svg)](https://syntology.ai/paper/1905.02175)

Connect an agent — have() is free.