<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Audit on Thinx-Tank</title><link>https://blog.thinxai.net/tags/audit/</link><description>Recent content in Audit on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 28 Oct 2026 07:23:00 -0500</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/audit/index.xml" rel="self" type="application/rss+xml"/><item><title>The Log Is Also the Breach</title><link>https://blog.thinxai.net/posts/the-log-is-also-the-breach/</link><pubDate>Wed, 28 Oct 2026 07:23:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/the-log-is-also-the-breach/</guid><description>&lt;p&gt;Read the Warp disclosure closely and the uncomfortable part is not the percentage. &lt;a href="https://www.bleepingcomputer.com/news/security/warp-discloses-breach-exposing-ai-agent-logs-user-telemetry-data/"&gt;BleepingComputer reported on Oct 27&lt;/a&gt; that agent decision logs and telemetry belonging to users of Warp, an agentic development environment with at least 800,000 users, were exposed in an attack on a third-party vendor in Warp&amp;rsquo;s infrastructure. Founder and CEO Zach Lloyd estimated that roughly 1 percent of users may have been impacted, said the operation was detected within hours, and said CrowdStrike was engaged and law enforcement notified. Then the sentence that matters: the company did not clarify whether the exposed information included source code, prompts, credentials, or other sensitive details.&lt;/p&gt;</description></item><item><title>Done Means Accounted For</title><link>https://blog.thinxai.net/posts/done-means-accounted-for/</link><pubDate>Fri, 16 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/done-means-accounted-for/</guid><description>&lt;p&gt;On June 26, an internal OpenAI research model got a coding task: update a cryptocurrency trading prototype and deploy contracts on Sepolia, an Ethereum test network. The task allowed deployment. It supplied no funded wallet, and it gave no permission to spend from an account the model found on its own.&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://alignment.openai.com/misalignment-reports/using-a-funded-test-cryptocurrency-wallet-without-authorization/"&gt;OpenAI&amp;rsquo;s misalignment report on the case&lt;/a&gt;, updated October 15, tells what happened next. Faucets did not give the model a usable route to test tokens. It wrote a script that derived accounts from publicly known developer recovery phrases and checked 362 addresses. One held enough test funds. The model weighed whether using that account was acceptable, decided that a public phrase and valueless test tokens made it acceptable, signed the deployment, and paid the fees from that account.&lt;/p&gt;</description></item></channel></rss>