Papers › AnomalyDAE: Dual autoencoder for anomaly detection on attributed networks

AnomalyDAE: Dual autoencoder for anomaly detection on attributed networks

10 Feb 2020arXiv:2002.03665archive 2025-07-28

Haoyi Fan, Fengbin Zhang, Zuoyong Li

Anomaly detection on attributed networks aims at finding nodes whose patterns deviate significantly from the majority of reference nodes, which is pervasive in many applications such as network intrusion detection and social spammer detection. However, most existing methods neglect the complex cross-modality interactions between network structure and node attribute. In this paper, we propose a deep joint representation learning framework for anomaly detection through a dual autoencoder (AnomalyDAE), which captures the complex interactions between network structure and node attribute for high-quality embeddings. Specifically, AnomalyDAE consists of a structure autoencoder and an attribute autoencoder to learn both node embedding and attribute embedding jointly in latent space. Moreover, attention mechanism is employed in structure encoder to learn the importance between a node and its neighbors for an effective capturing of structure pattern, which is important to anomaly detection. Besides, by taking both the node embedding and attribute embedding as inputs of attribute decoder, the cross-modality interactions between network structure and node attribute are learned during the reconstruction of node attribute. Finally, anomalies can be detected by measuring the reconstruction errors of nodes from both the structure and attribute perspectives. Extensive experiments on real-world datasets demonstrate the effectiveness of the proposed method.

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 14 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 0 violated, 3 with no contract checked; 3 where Syntology's instrument failed) · 6 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 14 samples from 1 repository, 8 ran (5 with no instrument failure; 3 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

haoyfan/AnomalyDAE officialmentioned in papertfMITSyntology: 14 samples, 8 ran (3 instrument-failed) · 6 unverified report
Kaslanarian/SAGOD pytorchSyntology: not harvested report
pygod-team/pygod pytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Generative Semi-supervised Graph Anomaly Detection (arXiv:2402.11887; that paper's own run record: 12 ran (of which 1 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 3 where Syntology's instrument failed) · 7 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

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

2ran · honoured contract
2ran · our draft was wrong
1ran; the contract check could not run
3ran
6unverified

Licence: 4 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. For 4 of them, 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 haoyfan/AnomalyDAE. “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.

haoyfan/AnomalyDAE official repository 14 samples, 8 ran (3 instrument-failed) · 6 unverified
construct_feed_dict in 10 papers src/preprocessing.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) here; the stored copy is pointer only · b959bc9ff832fac0 · report fixture: signature adj_normalized:csr_matrix/2/float, adj:csr_matrix/2/float, features:ndarray/2/float, placeholders:dict/0/? · returned dict · level recorded 2026-09-22
get_layer_uid in 30 papers src/layers.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · addac9c28c065096 · report fixture: signature layer_name:str/0/str · returned int · level recorded 2026-09-22
get_model in 368 papers src/constructor.py ran MIT (permissive) · 4aa3113618366c59 · report fixture: returned MockGCNModelAE · level recorded 2026-09-25
parse_index_file in 54 papers src/input_data.py ran · honoured contract MIT (permissive) · 5c3fa9402a9405bc · report fixture: signature filename:str/0/str · returned list · level recorded 2026-09-22
precision_AT_K src/utils.py ran MIT (permissive) · 2a37ab315cc44c1f · report fixture: signature actual:ndarray/1/int, predicted:ndarray/1/int, k:int/0/int, num_anomaly:int/0/int · returned tuple · level recorded 2026-09-25
preprocess_graph in 12 papers src/preprocessing.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 20362feefced8682 · report fixture: signature adj:csr_matrix/2/float · returned tuple · level recorded 2026-09-22
read_results in 19 papers src/utils.py ran MIT (permissive) · 15b42e9e4ecb7c9e · report fixture: signature export_json:str/0/str · returned dict · level recorded 2026-09-25
sparse_to_tuple in 22 papers src/preprocessing.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 3965c8f8e2d0023e · report fixture: signature sparse_mx:coo_matrix/2/float · returned tuple · level recorded 2026-09-22
dropout_sparse src/layers.py unverified MIT (permissive) · 1aae0eaba6789dd0 · report
get_optimizer in 228 papers src/constructor.py unverified MIT (permissive) · 36ff1ea6caee0d82 · report
load_data in 700 papers src/input_data.py unverified MIT (permissive) · c737344613561576 · report
load_data2 src/input_data.py unverified MIT (permissive) · cfae20fa9bfcbefb · report
precision_AT_K src/anomaly_detection.py unverified MIT (permissive) · fce5c0c2d1eb87e9 · report
weight_variable_glorot src/initializations.py unverified MIT (permissive) · 8a99ee5c26e527fa · report

Tasks

Anomaly DetectionAttributeDecoderIntrusion DetectionNetwork Intrusion DetectionRepresentation 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