Papers › Adversarial Examples on Graph Data: Deep Insights into Attack and Defense

Adversarial Examples on Graph Data: Deep Insights into Attack and Defense

5 Mar 2019arXiv:1903.01610archive 2025-07-28

Huijun Wu, Chen Wang, Yuriy Tyshetskiy, Andrew Docherty, Kai Lu, Liming Zhu

Graph deep learning models, such as graph convolutional networks (GCN) achieve remarkable performance for tasks on graph data. Similar to other types of deep models, graph deep learning models often suffer from adversarial attacks. However, compared with non-graph data, the discrete features, graph connections and different definitions of imperceptible perturbations bring unique challenges and opportunities for the adversarial attacks and defenses for graph data. In this paper, we propose both attack and defense techniques. For attack, we show that the discreteness problem could easily be resolved by introducing integrated gradients which could accurately reflect the effect of perturbing certain features or edges while still benefiting from the parallel computations. For defense, we observe that the adversarially manipulated graph for the targeted attack differs from normal graphs statistically. Based on this observation, we propose a defense approach which inspects the graph and recovers the potential adversarial perturbations. Our experiments on a number of datasets show the effectiveness of the proposed methods.

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 12 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 12 samples from 1 repository, 10 ran (10 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 on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

stellargraph/stellargraph officialmentioned in papermentioned on GitHubtfApache-2.0Syntology: 12 samples, 10 ran (0 instrument-failed) · 2 unverified report
GraphReshape/GraphReshape mentioned on GitHubpytorchSyntology: 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

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

10ran
2unverified

Licence: 0 of the 12 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 stellargraph/stellargraph. “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”. For 1 sample that ran, the graph records a signature this page does not show: an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape. “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.

stellargraph/stellargraph official repository 12 samples, 10 ran (0 instrument-failed) · 2 unverified
comma_sep stellargraph/core/validation.py ran Apache-2.0 (permissive) · dc7cde780e6f2212 · report fixture: signature values:list/1/int, limit:int/0/int, stringify:callable/0/? · returned str · level recorded 2026-09-25
expected_calibration_error in 12 papers stellargraph/calibration.py ran fingerprinted Apache-2.0 (permissive) · c2b35b0171ab08d5 · report fixture: signature prediction_probabilities:ndarray/1/float, accuracy:ndarray/1/float, confidence:ndarray/1/float · returned float64 · level recorded 2026-09-25
extract_element_features stellargraph/core/graph.py ran Apache-2.0 (permissive) · 83faed11aed1262c · report fixture: signature element_data:MockElementData/0/?, unique:callable/0/?, name:str/0/str, ids:ndarray/1/int, type:NoneType/0/?, use_ilocs:bool/0/bool · returned ndarray · level recorded 2026-09-25
is_real_iterable stellargraph/core/utils.py ran fingerprinted Apache-2.0 (permissive) · fabfe39c92cefeab · report fixture: signature x:list/1/int · returned bool · level recorded 2026-09-25
issue_text stellargraph/core/experimental.py ran Apache-2.0 (permissive) · 750b130756b77187 · report fixture: signature issues:list/1/int, for_rst:bool/0/bool · returned str · level recorded 2026-09-25
messages stellargraph/core/experimental.py ran Apache-2.0 (permissive) · ffd7a6431d7a8779 · report fixture: signature decl:MockDeclaration/0/?, reason:str/0/str, issues:list/1/int · returned tuple · level recorded 2026-09-25
render_link stellargraph/core/experimental.py ran Apache-2.0 (permissive) · 293f18b7f6dc6773 · report fixture: signature number:int/0/int, for_rst:bool/0/bool · returned str · level recorded 2026-09-25
separated stellargraph/core/validation.py ran Apache-2.0 (permissive) · b4998b48ce106551 · report fixture: signature values:list/1/int, limit:int/0/int, stringify:callable/0/?, sep:str/0/str · returned str · level recorded 2026-09-25
smart_array_index stellargraph/core/utils.py ran Apache-2.0 (permissive) · 9bc8662cbed7b93f · report fixture: signature array:ndarray/2/int, indices:ndarray/1/int · returned ndarray · level recorded 2026-09-25
zero_sized_array stellargraph/core/utils.py ran Apache-2.0 (permissive) · faea1114ea795e6f · report fixture: returned ndarray · level recorded 2026-09-25
convert_edges stellargraph/core/convert.py unverified Apache-2.0 (permissive) · e9d08df66de8c89b · report
from_networkx stellargraph/core/convert.py unverified Apache-2.0 (permissive) · 396a562b15f78565 · report

Tasks

Adversarial AttackAdversarial Defense

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Graph Convolutional Networks

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