Papers › Fooling automated surveillance cameras: adversarial patches to attack person detection

Fooling automated surveillance cameras: adversarial patches to attack person detection

18 Apr 2019arXiv:1904.08653archive 2025-07-28

Simen Thys, Wiebe Van Ranst, Toon Goedemé

Adversarial attacks on machine learning models have seen increasing interest in the past years. By making only subtle changes to the input of a convolutional neural network, the output of the network can be swayed to output a completely different result. The first attacks did this by changing pixel values of an input image slightly to fool a classifier to output the wrong class. Other approaches have tried to learn "patches" that can be applied to an object to fool detectors and classifiers. Some of these approaches have also shown that these attacks are feasible in the real-world, i.e. by modifying an object and filming it with a video camera. However, all of these approaches target classes that contain almost no intra-class variety (e.g. stop signs). The known structure of the object is then used to generate an adversarial patch on top of it. In this paper, we present an approach to generate adversarial patches to targets with lots of intra-class variety, namely persons. The goal is to generate a patch that is able successfully hide a person from a person detector. An attack that could for instance be used maliciously to circumvent surveillance systems, intruders can sneak around undetected by holding a small cardboard plate in front of their body aimed towards the surveillance camera. From our results we can see that our system is able significantly lower the accuracy of a person detector. Our approach also functions well in real-life scenarios where the patch is filmed by a camera. To the best of our knowledge we are the first to attempt this kind of attack on targets with a high level of intra-class variety like persons.

PaperPDFCodeCode 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

The archive's official repository (gitlab.com/EAVISE/adversarial-yolo) was not harvested; the 10 samples below come from 1 community repository.

Syntology 10 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 3 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): 10 samples from 1 repository, 7 ran (7 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 between 2026-09-24 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

gitlab.com/EAVISE/adversarial-yolo officialmentioned in papermentioned on GitHubpytorchSyntology: not harvested report
Zhang-Jack/adversarial_yolo2 mentioned on GitHubpytorchMITSyntology: 10 samples, 7 ran (0 instrument-failed) · 3 unverified report
bit-twidd1er/adversarial-yolo-snapshot mentioned on GitHubpytorchMITSyntology: not harvested report
sfc-computational-creativity-lab/x-adversarialfashion mentioned on GitHubpytorchMITSyntology: not harvested 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

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

7ran
3unverified

Licence: 1 of the 10 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from Zhang-Jack/adversarial_yolo2. “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.

Zhang-Jack/adversarial_yolo2 community (archive-listed) 10 samples, 7 ran (0 instrument-failed) · 3 unverified
distort_image image.py ran MIT (permissive) · 90b2ef0e95527027 · report fixture: signature im:Image/0/?, hue:float/0/float, sat:float/0/float, val:float/0/float · returned Image · level recorded 2026-09-25
get_max_probability craft_adv.py ran MIT (permissive) · fcefecd930437474 · report fixture: signature output:Tensor/4/float, cls_id:int/0/int, num_classes:int/0/int · returned Tensor · level recorded 2026-09-24
get_printability_array craft_adv.py ran MIT (permissive) · cd1c26da502bc987 · report fixture: signature printability_file:str/0/str, height:int/0/int, width:int/0/int · returned Tensor · level recorded 2026-09-24
load_conv in 5 papers cfg.py ran MIT (permissive) · 2329e9023f218b7e · report fixture: signature buf:ndarray/1/float, start:int/0/int, conv_model:callable/0/? · returned int · level recorded 2026-09-25
load_conv_bn cfg.py ran MIT (permissive) · bff835defe62db44 · report fixture: signature buf:ndarray/1/float, start:int/0/int, conv_model:callable/0/?, bn_model:callable/0/? · returned int · level recorded 2026-09-25
rand_scale in 10 papers image.py ran fingerprinted MIT (permissive) · 6a4124c294bed05b · report fixture: signature s:float/0/float · returned float · level recorded 2026-09-25
scale_image_channel image.py ran MIT (permissive) · 835b72f71b599016 · report fixture: signature im:Image/0/?, c:int/0/int, v:float/0/float · returned Image · level recorded 2026-09-25
build_targets in 8 papers region_loss.py unverified MIT (permissive) here; the stored copy is pointer only · bafb242ad7347214 · report
calc_nps craft_adv.py unverified MIT (permissive) · 7c3e3f84afa179de · report
parse_cfg in 19 papers cfg.py unverified MIT (permissive) · 93c283a4f6e6c40f · report

Tasks

Human Detection

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