Papers › Deep Isolation Forest for Anomaly Detection

Deep Isolation Forest for Anomaly Detection

14 Jun 2022arXiv:2206.06602archive 2025-07-28

Hongzuo Xu, Guansong Pang, Yijie Wang, Yongjun Wang

Isolation forest (iForest) has been emerging as arguably the most popular anomaly detector in recent years due to its general effectiveness across different benchmarks and strong scalability. Nevertheless, its linear axis-parallel isolation method often leads to (i) failure in detecting hard anomalies that are difficult to isolate in high-dimensional/non-linear-separable data space, and (ii) notorious algorithmic bias that assigns unexpectedly lower anomaly scores to artefact regions. These issues contribute to high false negative errors. Several iForest extensions are introduced, but they essentially still employ shallow, linear data partition, restricting their power in isolating true anomalies. Therefore, this paper proposes deep isolation forest. We introduce a new representation scheme that utilises casually initialised neural networks to map original data into random representation ensembles, where random axis-parallel cuts are subsequently applied to perform the data partition. This representation scheme facilitates high freedom of the partition in the original data space (equivalent to non-linear partition on subspaces of varying sizes), encouraging a unique synergy between random representations and random partition-based isolation. Extensive experiments show that our model achieves significant improvement over state-of-the-art isolation-based methods and deep detectors on tabular, graph and time series datasets; our model also inherits desired scalability from iForest.

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 2 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 13 samples from 1 repository, 9 ran (9 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 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-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

xuhongzuo/deep-iforest officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 13 samples, 9 ran (0 instrument-failed) · 4 unverified report
xuhongzuo/DeepOD pytorchSyntology: 1 sample, 1 ran (1 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

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

1ran · our draft was wrong
9ran
4unverified

Licence: 0 of the 14 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

xuhongzuo/deep-iforest official repository 13 samples, 9 ran (0 instrument-failed) · 4 unverified
choose_act_func algorithms/net_torch.py ran Apache-2.0 (permissive) · a12ba441a177fea1 · report fixture: signature activation:str/0/str · returned tuple · level recorded 2026-09-25
choose_pooling_func algorithms/net_torch.py ran Apache-2.0 (permissive) · 28052f3a6156475a · report fixture: signature pooling:str/0/str · returned function · level recorded 2026-09-25
evaluate in 514 papers utils.py ran fingerprinted Apache-2.0 (permissive) · 5e5c9ce7f22f88db · report fixture: signature y_true:ndarray/1/int, scores:ndarray/1/float · returned tuple · level recorded 2026-09-25
files_exist in 8 papers pyg_old/pyg_old_dataset.py ran Apache-2.0 (permissive) · 54056f7e25fb5e82 · report fixture: signature files:list/1/str · returned bool · level recorded 2026-09-25
generate_data in 66 papers create_scal_data.py ran Apache-2.0 (permissive) · ebd0591813c141a1 · report fixture: signature n_nor:int/0/int, n_ano:int/0/int, dim:int/0/int, n_nor_c:int/0/int, n_ano_c:int/0/int · returned DataFrame · level recorded 2026-09-25
get_algo_config config.py ran Apache-2.0 (permissive) · c3f12824a5d58cb3 · report fixture: signature algo:str/0/str · returned dict · level recorded 2026-09-25
min_max_normalize in 7 papers utils.py ran fingerprinted Apache-2.0 (permissive) · 21807eca4a622d05 · report fixture: signature x:ndarray/2/float · returned ndarray · level recorded 2026-09-25
parser_add_model_argument parser_utils.py ran Apache-2.0 (permissive) · 75128adb98851d08 · report fixture: signature parser:ArgumentParser/0/? · returned ArgumentParser · level recorded 2026-09-25
update_model_configs parser_utils.py ran Apache-2.0 (permissive) · 313175948ba5220a · report fixture: signature args:Args/0/?, model_configs:dict/0/? · returned dict · level recorded 2026-09-25
choose_net algorithms/net_torch.py unverified Apache-2.0 (permissive) · 1cd71c35a5800a5c · report
data_preprocessing in 6 papers utils.py unverified Apache-2.0 (permissive) · 9eb090ee2b6ed905 · report
get_algo_class config.py unverified Apache-2.0 (permissive) · 5b18d8ed3af34f06 · report
to_list in 62 papers pyg_old/pyg_old_dataset.py unverified Apache-2.0 (permissive) · d32004b35c3fd2b9 · report
xuhongzuo/DeepOD community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
cal_score in 9 papers deepod/models/tabular/dif.py ran · our draft was wrong BSD-2-Clause (permissive) · 7360272baa832c6b · report fixture: signature xx:ndarray/2/float, clf:IsolationForest/0/? · returned ndarray · level recorded 2026-09-22

Tasks

Anomaly DetectionTime SeriesTime Series Analysis

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Anomaly Detection Forest CoverType DIF AUC 0.972 #1 of 1 Archive leaderboard report
Anomaly Detection Kaggle-Credit Card Fraud Dataset DIF AUC 0.953 #1 of 1 Archive leaderboard report
Anomaly Detection NB15-Analysis DIF AUC 0.931 #1 of 1 Archive leaderboard report
Anomaly Detection NB15-Backdoor DIF AUC 0.918 #1 of 1 Archive leaderboard report
Anomaly Detection NB15-DoS DIF AUC 0.932 #1 of 1 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

1D CNN

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