Skip to content
Preprint

Hiding Directions, Leaking Structure: Breaking ArrowCloak through Low-Rank Structure

Aug 2026 · 1 citation · 37 references
Computer Science

TL;DR

This paper revisits ArrowCloak from cryptographic and structural perspectives and proposes an end-to-end, query-free recovery attack, suggesting that lightweight protection should address both per-vector geometry and joint structure across released weights.

Abstract

TEE-shielded inference keeps sensitive state in a trusted execution environment (TEE) while offloading linear algebra to an untrusted accelerator. Wang et al., in Game of Arrows (USENIX Security 2025), showed that five widely adopted lightweight defenses preserve vector directions and introduced ArrowMatch to exploit this leakage. They then proposed ArrowCloak, which adds a different multiple of one shared mask direction to each vector and bases its weight-recovery hardness argument on Learning with Errors (LWE). ArrowCloak successfully reduces ArrowMatch to near-black-box levels. In this paper, we revisit ArrowCloak from cryptographic and structural perspectives. Its LWE formulation does not by itself establish standard LWE hardness: the reduction direction, quantized arithmetic, and joint instance distribution do not meet the required conditions. Reusing one mask direction leaves a recoverable rank-one component across the released matrix. We exploit this structure with our proposed attack, an end-to-end, query-free recovery attack. Given a public checkpoint and the obfuscated weights, the attack removes the masking subspace, recovers the hidden one-to-one correspondence, and reconstructs protected weights without transformation secrets, victim queries, or fine-tuning data. Across six model-task pairs spanning classification, segmentation, and diffusion, the attack recovers 99.92%-100% of hidden vector correspondences. Reconstructed classification models achieve 94.39%-99.54% victim agreement and differ by at most 1.59 percentage points in accuracy; the recovered segmentation model achieves 98.35% output agreement. These findings suggest that lightweight protection should address both per-vector geometry and joint structure across released weights.

View source

Similar papers

Preprint Sep 2026

Understanding the Security Boundary of Obfuscation-based On-Device LLM Protection

This paper formalizes a set of obfuscation primitives, defined as dual-tuples of linear computations satisfying specific algebraic properties, and demonstrates that the matrix-level weight transformations of several representative efficient TSLP frameworks can be expressed as compositions of these primitives.

Han-Yi Zhou, Chen-Yang Li, Yuan-Zhe Pang et al. · 0 citations
Preprint Sep 2026

Your Model Is Leaking: Covert Information Transfer through LLM Residual Streams

A residual-stream covert-channel attack is introduced that maps messages to codewords and injects them into an intermediate residual stream through a compromised runtime hook and is scaled with the local residual norm using the signal-to-residual-norm ratio.

Ming-Yuan Li, Yan-Na Jiang, Guang-Sheng Yu et al. · 0 citations
#machine learning Preprint Sep 2026

Decoy Direction Optimization: A Post-Hoc Defense Against LLM Abliteration

Decoy Direction Optimization (DDO), a fast, post-hoc weight-editing defense that requires no base-model finetuning, is introduced, based on a simple mechanistic insight: ablation attacks rely on contrastive estimators to find the refusal direction.

Aashiq Muhamed, Mona T. Diab, Virginia Smith · 2 citations · ⚡1
Preprint Sep 2026

An Open-Source End-to-End FHE Implementation for Privacy-Preserving Llama 3 8B Inference

Odin is the first open-source end-to-end GPU CKKS implementation of Llama-3, an FHE inference system that co-designs ciphertext packing and model execution for Llama and uses a feature-major cross-layer layout to unify residual connections and layer interfaces.

Yu-Hang Fan, Yu-Si Chen, Kan-Yu Ye et al. · 0 citations

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.