Jie Zhou, Xu Sun, Yankai Lin, Wenkai Yang, Sishuo Chen, Xiaohan Bi
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/2402.11208.json · badge: /api/ran/2402.11208.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.
| Repository | Role | Ran |
|---|---|---|
| lancopku/agent-backdoor-attacks | canonical (classifier label) classifier basis: classifier_2025 |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| parse_action | Ran ran; our contract draft was wrong, not the code |
lancopku/agent-backdoor-attacks/AgentTuning/AgentTuning/AgentBench.old/src/tasks/webshop/web_agent_site/engine/engine.py pointer only (licence: NONE) · get_code("f482598cf447f335") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, lancopku/agent-backdoor-attacks 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. |
| read_html_template | Ran ran; our contract draft was wrong, not the code |
lancopku/agent-backdoor-attacks/AgentTuning/AgentTuning/AgentBench.old/src/tasks/webshop/web_agent_site/engine/engine.py pointer only (licence: NONE) · get_code("b521d0dcdbd7ea7c") How it ranThe body of this sample is withheld: GitHub detected no licence in this paper's repository, lancopku/agent-backdoor-attacks 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. |
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, 0 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.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| parse_action | 1 other paper 1 dated earlier |
2309.08172 (2023-09) LASER: LLM Agent with State-Space Exploration for Web Navigation |
|
| read_html_template | 1 other paper 1 dated earlier |
2309.08172 (2023-09) LASER: LLM Agent with State-Space Exploration for Web Navigation |
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.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Driven by the rapid development of Large Language Models (LLMs), LLM-based agents have been developed to handle various real-world applications, including finance, healthcare, and shopping, etc. It is crucial to ensure the reliability and security of LLM-based agents during applications. However, the safety issues of LLM-based agents are currently under-explored. In this work, we take the first step to investigate one of the typical safety threats, backdoor attack, to LLM-based agents. We first formulate a general framework of agent backdoor attacks, then we present a thorough analysis of different forms of agent backdoor attacks. Specifically, compared with traditional backdoor attacks on LLMs that are only able to manipulate the user inputs and model outputs, agent backdoor attacks exhibit more diverse and covert forms: (1) From the perspective of the final attacking outcomes, the agent backdoor attacker can not only choose to manipulate the final output distribution, but also introduce the malicious behavior in an intermediate reasoning step only, while keeping the final output correct. (2) Furthermore, the former category can be divided into two subcategories based on trigger locations, in which the backdoor trigger can either be hidden in the user query or appear in an intermediate observation returned by the external environment. We implement the above variations of agent backdoor attacks on two typical agent tasks including web shopping and tool utilization. Extensive experiments show that LLM-based agents suffer severely from backdoor attacks and such backdoor vulnerability cannot be easily mitigated by current textual backdoor defense algorithms. This indicates an urgent need for further research on the development of targeted defenses against backdoor attacks on LLM-based agents. 3 Warning: This paper may contain biased content.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2402.11208")
get_code_for_paper("2402.11208")
have("2402.11208")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2402.11208.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2402.11208)
Connect an agent — have() is free.