Explainable Heterogeneous Anomaly Detection in Financial Networks via Adaptive Expert Routing

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2510.17088v3 Announce Type: replace-cross Abstract: Financial anomalies arise from heterogeneous mechanisms - price shocks, liquidity freezes, contagion cascades, and momentum reversals - yet existing detectors produce uniform anomaly scores without revealing which mechanism is failing or where risks concentrate. This hinders targeted responses: liquidity freezes call for market-making support, whereas price shocks from information asymmetry call for circuit breakers. Three key challenges remain unresolved: (1) static graph structures cannot adapt when correlations shift across regimes; (2) uniform detectors overlook heterogeneous anomaly signatures; and (3) black-box scores provide no actionable guidance on which mechanism drives the anomaly. We address these challenges with an adaptive graph learning framework that embeds interpretability architecturally rather than post hoc. The framework constructs stress-modulated graphs that adaptively interpolate between known sector and geographic relationships and data-driven correlations as market conditions evolve. Anomalies are decomposed via four mechanism-specific experts - Price-Shock, Liquidity, Systemic-Contagion, and Momentum-Reversal - whose routing weights serve as interpretable proxies for mechanism attribution. A hierarchical Market Pressure Index aggregates entity-level anomaly scores into graduated market-wide alerts. On 100 U.S. equities (2017-2024), the framework detects all six major market stress events with a 3.7-day mean lead time, outperforming the strongest baselines by +33 percentage points in …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2510.17088
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.