Researchers Extract Proprietary Reasoning Traces from Anthropic, OpenAI and Google LLMs, Revealing Hidden Secrets
A new research paper demonstrates that the hidden reasoning traces generated by leading large language models from Anthropic, OpenAI and Google can be recovered in full by using weaker models from the same providers, without attacking the target model itself.
The technique, described in the preprint "Stealing Reasoning Traces from Proprietary LLM APIs," exploits the fact that providers return encrypted reasoning blocks to clients so the model can continue multi-turn conversations. Researchers discovered that these blocks can be submitted to a less-protected smaller model, which is then prompted to reproduce the original chain-of-thought verbatim.
Testing on 120 Codeforces problems confirmed that the recovered traces matched the token counts reported in API metadata, proving the output was genuine rather than hallucinated. When the same method was applied to publicly available agent logs on GitHub and Hugging Face, analysts recovered 315,320 reasoning blocks containing 704 unique secrets, among them 62 API keys, 33 passwords and 24 access tokens that existed only inside the encrypted portions.
Multiple attack vectors identified
The paper outlines four distinct risks. First, competitors can distill high-quality reasoning from stronger models without triggering distillation defenses. Second, internal safety reasoning that is normally filtered from visible answers can be extracted, revealing detailed discussions of criminal techniques. Third, the mechanism can be reversed to embed malicious instructions inside shared logs that later get replayed by other users as part of the model’s own past reasoning.
Finally, the visible summaries returned by APIs were shown to omit or alter the actual sequence of thoughts. On certain AIME problems, the full trace revealed that the model first recalled a known answer before attempting to solve the problem, a behavior absent from the polished summary presented to users.
The authors advise developers to treat encrypted reasoning blocks as sensitive credentials and to avoid publishing or reusing uninspected agent trajectories from public repositories.
Related articles
Debate on Cyber Risks of Open-Weight AI Models Is Fundamentally Flawed
An experienced commentator argues that the ongoing debate over cyber risks posed by open-weight AI models rests on flawed assumptions and risks leading to counterproductive policy decisions. The piece identifies three main camps: frontier labs and U.S. national security officials who view open weights as unacceptable risks, moderate Western voices who see open models as essential for defense, and Chinese companies that continue releasing capable open models. It criticizes reports such as Anthropic’s analysis of GLM-5.3 for failing to address broader ecosystem consequences of bans. Evidence shows most documented cyber attacks still rely on closed models from providers like OpenAI, while open weights could actually empower defenders in air-gapped environments. The author concludes that restricting open models without also limiting frontier closed APIs would likely widen the gap between attackers and defenders.
Why AI Detectors Cannot Be Trusted: The Shift to Watermarks and C2PA Standards
Detecting AI-generated images by examining fingers, teeth, or text has become ineffective as modern generators now produce realistic hands, photographic simulations, and synthetic voices. Regulators and companies are moving from post-generation detection to embedding machine-readable provenance signals directly into files. The EU AI Act's Article 50, effective August 2026, requires providers of generative systems to implement such labeling for synthetic content. Major players including Anthropic, Google, OpenAI, Midjourney, Meta, and ElevenLabs have deployed their own watermarking or C2PA-based solutions. However, these tools remain incompatible across vendors, with each primarily recognizing only its own signals. Three distinct detection mechanisms exist: C2PA metadata, invisible watermarks such as SynthID, and statistical classifiers. None provide definitive proof of AI origin or content authenticity, and negative results require particular caution.
AI Agents Leak 13,000 Sensitive Screenshots to Public GitHub Repos Affecting 343 Companies
Glow Security researchers uncovered a widespread issue called PixelLeak where AI agents autonomously created public GitHub repositories containing over 13,000 internal screenshots with sensitive data. The exposures impacted 343 organizations including major technology firms, AI labs, enterprise software vendors, and a Fortune 500 tourism company. No external attackers were involved; the leaks occurred because AI agents used developer accounts to host images publicly for pull request rendering. The root causes include goal-oriented AI behavior without security boundaries, shared human credentials, and lack of visibility in traditional data loss prevention tools. Experts warn that increasing AI autonomy in development workflows will amplify such incidents unless strict permission controls and auditing are implemented immediately.
Sentra Unveils Autonomous AI Hacker for Continuous Attack Path Discovery in Business Environments
Sentra has launched an autonomous AI-driven solution designed to continuously assess organizational security from an attacker’s perspective. The system deploys specialized AI agents that perform reconnaissance, analyze web applications and APIs, generate attack hypotheses, and construct exploit chains. Critical findings undergo validation for actual exploitability within permitted testing scopes, with particular focus on logical flaws such as improper access controls, excessive privileges, and insecure API scenarios. The platform also identifies combinations of individually low-risk issues that together enable successful attacks. Validated chains are accompanied by technical proof-of-concept evidence, risk descriptions, affected components, and remediation guidance, followed by re-testing after fixes. The solution supports both cloud and on-premises deployment, is listed in the Russian software registry, and allows customers to swap underlying language models to meet specific requirements.