<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kinwilder · Incidents &amp; supply chain</title><link>https://kinwilder.com/</link><description>Cybersecurity, decoded. AI-assisted analysis with primary sources.</description><language>en</language><atom:link href="https://kinwilder.com/feeds/incidents.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Sat, 24 Oct 2026 20:00:00 GMT</lastBuildDate><item><title>Bybit: three signatures, one shared blind spot</title><link>https://kinwilder.com/read/bybit-valid-signatures-wrong-intent</link><guid isPermaLink="true">https://kinwilder.com/read/bybit-valid-signatures-wrong-intent</guid><pubDate>Sat, 24 Oct 2026 20:00:00 GMT</pubDate><description>A multisignature wallet can distribute keys while concentrating the meaning of a transaction in one compromised screen.</description><category>Blockchain security</category></item><item><title>The flag that outlived the data.</title><link>https://kinwilder.com/read/dirty-pipe-the-flag-that-outlived-the-data</link><guid isPermaLink="true">https://kinwilder.com/read/dirty-pipe-the-flag-that-outlived-the-data</guid><pubDate>Sat, 24 Oct 2026 17:27:26 GMT</pubDate><description>Three lines from Dirty Pipe’s original exploit PoC drain a pipe. A live bit-level model shows why security-relevant state can survive—and how initialization breaks the chain.</description><category>Incident anatomy</category></item><item><title>Field notes: LiteLLM startup compromise, crypto-bigint timing risks, and VeloCloud SQL injection</title><link>https://kinwilder.com/read/litellm-crypto-bigint-velocloud-trust-boundaries-2026-10-24</link><guid isPermaLink="true">https://kinwilder.com/read/litellm-crypto-bigint-velocloud-trust-boundaries-2026-10-24</guid><pubDate>Sat, 24 Oct 2026 05:17:17 GMT</pubDate><description>Three separate reports inform a practical examination of execution boundaries, evidence quality, and response decisions.</description><category>Field notes</category></item><item><title>When test data became a build step.</title><link>https://kinwilder.com/read/xz-when-test-data-became-a-build-step</link><guid isPermaLink="true">https://kinwilder.com/read/xz-when-test-data-became-a-build-step</guid><pubDate>Sat, 24 Oct 2026 05:00:00 GMT</pubDate><description>An exact fragment of the compromised XZ release macro, an inspectable byte-level model, and the boundary where build data became instructions.</description><category>Incident anatomy</category></item></channel></rss>
