Searcharxiv⌕ Search
Home/Archive/arXiv

arXiv · 2610.26327

Fortress: Fork Resistant Transparency logs Relying on Social graph Structure

Anastasiia Kucherenko·Melissa Chase·Esha Ghosh
View original source ↗Read source document ↗Export metadata ↓

Abstract

Transparency systems -- such as Key Transparency (KT), Certificate Transparency, and binary transparency -- require that all honest participants see the same view of an untrusted server's directory, or, failing that, that the misbehaviour is publicly detected. Every existing design closes this gap with an external trust anchor: a publicly available bulletin board (BB), a blockchain, or an out-of-band (OOB) gossip network among auditors. We observe that transparency systems already have a built-in resource that has so far been overlooked: the social graph induced by the users themselves. We ask whether it can replace the bulletin board or the external gossip channel entirely, and answer in the affirmative (if occasional out-of-band interactions are allowed). We formalise a new primitive, Social-Graph based Forking-Resilient Transparency (sg-FORT), which captures the security guarantees of a BB-free transparency system and we construct Fortress Fork Resistant Transparency logs Relying on Social graph Structure, to our knowledge the first such protocol. In every epoch either all users output the same post, or at least one honest user produces a publicly verifiable Proof of Misbehaviour. Our guarantees hold against an arbitrary malicious server, including a snapshot adversary that may compromise a user and learn its secret state, as long as the server does not compromise close users. In honest executions, OOB interactions occur only when a user resets their secrets, so the total OOB cost approaches the natural lower bound of one call per reset -- dramatically below the full-gossip alternative. We prove security under standard cryptographic assumptions on signatures and dictionary commitment. Under simplifying assumptions (synchronous epochs, always-online users), we view this as a first feasibility result that opens up the design space of social-graph-based transparency systems.

Explore related subjects

cs.CR

Keep this discovery

Explore connections, maps & timelines

BibTeXRIS

Anastasiia Kucherenko, Melissa Chase, Esha Ghosh. 2026-10-19. Fortress: Fork Resistant Transparency logs Relying on Social graph Structure. https://arxiv.org/abs/2610.26327

Cite the original work for its findings. Save a collection to share your selection of sources.

KEEP EXPLORING

Related papers

arXiv2026

Can You Trust the Vectors in Your Vector Database? Black-Hole Attack from Embedding Space Defects

Vector databases serve as the retrieval backbone of modern AI applications, yet their security remains largely unexplored. We propose the Black-Hole Attack, a poisoning attack that injects a small number of malicious vectors near the geometric center of the stored vectors. These injected vectors attract queries like a black hole and frequently appear in the top-k retrieval results for most queries. This attack is enabled by a phenomenon we term centrality-driven hubness: in high-dimensional embedding spaces, vectors near the centroid become nearest neighbors of a disproportionately large number of other vectors, while this centroid region is nearly empty in practice. The attack shows that vectors in a vector database cannot be blindly trusted: geometric defects in high-dimensional embeddings make retrieval inherently vulnerable. Based on this insight, we propose four attack paths tailored to different attacker capabilities. Our experiments show that up to 94.4% of queries are successfully attacked. Additionally, we study two directions of defense: hubness mitigation and detection-based filtering. Hubness mitigation either significantly reduces retrieval accuracy or provides only limited protection, while the detection-based defense is effective against some attack paths but fails against others. A robust and adaptive defense thus remains an open problem, and our findings indicate that vector databases require more careful treatment of security.

cs.CR↗
arXiv2026

Anywhere, Any-Stymie: Remote Activation of Trojan Malware on LiDAR with Modulated Signals

LiDAR sensors are widely deployed in autonomous systems for safety-critical 3D perception. We identify a previously unexplored attack surface in which dormant malware, embedded in the LiDAR sensing pipeline, remains inactive during normal operation and is triggered externally after deployment, without access to sensor hardware or networking at attack time. This malware was developed in a closed research test environment with vendor technical support, rather than by exploiting an inherent production supply-chain vulnerability. To trigger the malware, we repurpose the sensor's own native dual-return signal processing as a covert channel for a modulated optical signal delivered into the environment. Once triggered, the malware performs false data injection and suppression on static and mobile platforms. Unlike optical spoofing, where the transmitted signal is itself the attack, here it carries only a small key that the sensor decodes with existing signal processing. We establish feasibility with static triggering at 300~ft and drive-by runs reaching 35 mph, and verify that injected artifacts are taken up as detections by a fine-tuned 3D object detector. On a deployed tactical autonomous vehicle running an unmodified production autonomy stack, we demonstrate both fail-safe and fail-dangerous impact: emergency stop, mission abort, and collision. These results motivate stronger integrity guarantees across LiDAR development and deployment pipelines.

cs.CR↗
arXiv2026

VeriRouter: Towards Verifiable LLM Routing

Large language model (LLM) routers are increasingly deployed to optimize quality, latency, and cost through dynamic model selection and request rewriting. However, a compromised router can cause ineligible selection on the control plane, unendorsed rewriting or unfaithful relay on the data plane, undermining LLM routing integrity. We present VeriRouter, a verifiable LLM routing framework. Under an endorsed public context binding a private semantic index and rewrite banks, VeriRouter combines ZK proofs with a provider-issued serving certificate to establish integrity across both planes while keeping the router's private routing assets hidden from clients. For model selection, we design an efficient ZK proof for semantic search. For rewriting, local checks enforce message preservation and additions from committed banks. On real-world workloads, VeriRouter's model-selection and rewrite proofs average 21.92~s and 4.24~s, yielding 1,307$\times$ and 101$\times$ speedups over the fastest completing baselines. Relative to serving without verification, VeriRouter adds only 4.08 s under per-turn selection and 0.11 s under session-pinned selection.

cs.CR↗