# Stealing Reasoning Traces from Proprietary LLM APIs > Source: > Published: 2026-08-11 07:07:06+00:00 # Computer Science > Cryptography and Security [Submitted on 10 Aug 2026] # Title:Stealing Reasoning Traces from Proprietary LLM APIs [View PDF](/pdf/2608.09867) Abstract:Leading large language model providers now conceal their models' step-by-step reasoning, or chain-of-thought, to protect intellectual property and limit information leakage. Rather than storing these traces server-side, providers return them to the client as blocks of encrypted text, which the client passes back with each subsequent request. Building on prior research, we identify an architectural vulnerability: these encrypted blocks are fully compatible and interchangeable across different sessions, users, and models within a provider's ecosystem. We exploit this compatibility to develop a scalable decryption jailbreak. By injecting an encrypted reasoning trace from a given model into a weaker, and less safeguarded model from the same provider, we force it to decode and output the trace verbatim in plaintext, without ever jailbreaking the more capable model directly. This vulnerability enables four distinct attack vectors. First, it circumvents anti-distillation mechanisms, allowing adversaries to extract a proprietary model's reasoning, as we demonstrate across Anthropic, OpenAI, and Google. Second, it allows for large-scale private data extraction. Developers frequently share session logs publicly, unaware of contents of the encrypted blocks. By decoding 315,320 reasoning blocks scraped from public repositories, we recovered 367 Personally Identifiable Information (PII) artifacts and 182 credentials. Third, it inadvertently reveals hazardous information hidden within the reasoning process, even in cases where the model's final, visible output safely rejects a malicious request. Fourth, attackers can leverage this flaw to execute invisible prompt injections, embedding malicious payloads entirely within encrypted blocks to poison public agentic rollouts. Following responsible disclosure, we propose concrete cryptographic and system-level mitigations to secure client-side reasoning. ## Submission history From: Alexander Panfilov [[view email](/show-email/81199360/2608.09867)] **[v1]** Mon, 10 Aug 2026 17:24:50 UTC (16,346 KB) ### Current browse context: cs.CR ### References & Citations Loading... # Bibliographic and Citation Tools Bibliographic Explorer *(*[What is the Explorer?](https://info.arxiv.org/labs/showcase.html#arxiv-bibliographic-explorer)) Connected Papers *(*[What is Connected Papers?](https://www.connectedpapers.com/about)) Litmaps *(*[What is Litmaps?](https://www.litmaps.co/)) scite Smart Citations *(*[What are Smart Citations?](https://www.scite.ai/))# Code, Data and Media Associated with this Article alphaXiv *(*[What is alphaXiv?](https://alphaxiv.org/)) CatalyzeX Code Finder for Papers *(*[What is CatalyzeX?](https://www.catalyzex.com)) DagsHub *(*[What is DagsHub?](https://dagshub.com/)) Gotit.pub *(*[What is GotitPub?](http://gotit.pub/faq)) Hugging Face *(*[What is Huggingface?](https://huggingface.co/huggingface)) ScienceCast *(*[What is ScienceCast?](https://sciencecast.org/welcome))# Demos # Recommenders and Search Tools Influence Flower *(*[What are Influence Flowers?](https://influencemap.cmlab.dev/)) CORE Recommender *(*[What is CORE?](https://core.ac.uk/services/recommender))# arXivLabs: experimental projects with community collaborators arXivLabs is a framework that allows collaborators to develop and share new arXiv features directly on our website. Both individuals and organizations that work with arXivLabs have embraced and accepted our values of openness, community, excellence, and user data privacy. arXiv is committed to these values and only works with partners that adhere to them. Have an idea for a project that will add value for arXiv's community? [ Learn more about arXivLabs](https://info.arxiv.org/labs/index.html).