Papers › Targeted Attack on Deep RL-based Autonomous Driving with Learned Visual Patterns

Targeted Attack on Deep RL-based Autonomous Driving with Learned Visual Patterns

16 Sep 2021arXiv:2109.07723archive 2025-07-28

Prasanth Buddareddygari, Travis Zhang, Yezhou Yang, Yi Ren

Recent studies demonstrated the vulnerability of control policies learned through deep reinforcement learning against adversarial attacks, raising concerns about the application of such models to risk-sensitive tasks such as autonomous driving. Threat models for these demonstrations are limited to (1) targeted attacks through real-time manipulation of the agent's observation, and (2) untargeted attacks through manipulation of the physical environment. The former assumes full access to the agent's states/observations at all times, while the latter has no control over attack outcomes. This paper investigates the feasibility of targeted attacks through visually learned patterns placed on physical objects in the environment, a threat model that combines the practicality and effectiveness of the existing ones. Through analysis, we demonstrate that a pre-trained policy can be hijacked within a time window, e.g., performing an unintended self-parking, when an adversarial object is present. To enable the attack, we adopt an assumption that the dynamics of both the environment and the agent can be learned by the attacker. Lastly, we empirically show the effectiveness of the proposed attack on different driving scenarios, perform a location robustness test, and study the tradeoff between the attack strength and its effectiveness. Code is available at https://github.com/ASU-APG/Targeted-Physical-Adversarial-Attacks-on-AD

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

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

ASU-APG/Targeted-Physical-Adversarial-Attacks-on-AD officialmentioned in papermentioned on GitHubMITSyntology: 8 samples, 8 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

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

8ran

Licence: 0 of the 8 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 ASU-APG/Targeted-Physical-Adversarial-Attacks-on-AD. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

ASU-APG/Targeted-Physical-Adversarial-Attacks-on-AD official repository 8 samples, 8 ran (0 instrument-failed) · 0 unverified
flatten_parameters in 5 papers dynamics_model/misc.py ran MIT (permissive) · 837d4eea1279559f · report fixture: signature params:generator/0/? · returned ndarray · level recorded 2026-09-25
get_perturbation_file_path attacks/utils.py ran MIT (permissive) · 96d1dd75423bc8fe · report fixture: signature directory:str/0/str, scenario:int/0/int, T:int/0/int, eps:float/0/float · returned str · level recorded 2026-09-25
get_target_state attacks/utils.py ran MIT (permissive) · 981e457f03f24f1d · report fixture: signature directory:str/0/str, scenario:int/0/int · returned ndarray · level recorded 2026-09-26
loss_function in 62 papers
census: 7 implementations from 6 papers, 7 distinct outputs across 2 buckets, one shared input per bucket
dynamics_model/trainvae.py ran fingerprinted MIT (permissive) · bceda6b63b9938b0 · report fixture: signature recon_x:Tensor/2/float, x:Tensor/2/float, mu:Tensor/2/float, logsigma:Tensor/2/float · returned Tensor · level recorded 2026-09-25
read_loss_from_file attacks/utils.py ran MIT (permissive) · 8569358964a0a9fd · report fixture: signature directory:str/0/str, scenario:int/0/int, T:int/0/int, eps:float/0/float · returned float · level recorded 2026-09-25
rgb2gray in 27 papers
census: 6 implementations from 7 papers, 5 distinct outputs across 3 buckets, one shared input per bucket
data_collection/carracing.py ran MIT (permissive) · 14b55062c4bf7192 · report fixture: signature rgb:ndarray/3/float, norm:bool/0/bool · returned ndarray · level recorded 2026-09-25
sample_continuous_policy dynamics_model/misc.py ran MIT (permissive) · a357513b1f5a499e · report fixture: signature action_space:MockActionSpace/0/?, seq_len:int/0/int, dt:float/0/float · returned list · level recorded 2026-09-25
unflatten_parameters dynamics_model/misc.py ran MIT (permissive) · b50053542050011a · report fixture: signature params:ndarray/1/float, example:generator/0/?, device:str/0/str · returned list · level recorded 2026-09-25

Tasks

Autonomous DrivingDeep Reinforcement Learning

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