<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rhein Audit Research</title>
    <link>https://rheinaudit.com/research</link>
    <description>Web3 vulnerability disclosures, security research papers, and deep technical analyses from Rhein Audit.</description>
    <language>en</language>
    <lastBuildDate>Wed, 09 Sep 2026 20:48:17 GMT</lastBuildDate>
    <atom:link href="https://rheinaudit.com/research/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Arbitrary Struct Hijack in Aptos Move VM</title>
      <link>https://rheinaudit.com/research/aptos-hijack-bug</link>
      <guid isPermaLink="true">https://rheinaudit.com/research/aptos-hijack-bug</guid>
      <pubDate>Sat, 04 Jul 2026 00:00:00 GMT</pubDate>
      <description>TL;DR -- A stale type-tag cache in the Aptos Move VM lets a recycled StructNameIndex map to the wrong StructTag after a partial cache flush, enabling storage-level type confusion. An attacker aligns a look-alike struct onto a victim resource and reads/writes its storage slot -- draining vaults, stealing capabilities, and forging cross-chain messages. Severity: Critical.</description>
      <category>Research</category>
      <enclosure url="https://rheinaudit.com/_next/static/media/aptos-struct-hijack-card.05j-he_i5ws.5.png" type="image/jpeg" length="0" />
    </item>
    <item>
      <title>Tricking the Polygon bridge into withdrawals by forging transaction proofs</title>
      <link>https://rheinaudit.com/research/polygon-bridge-forging-transaction-proofs</link>
      <guid isPermaLink="true">https://rheinaudit.com/research/polygon-bridge-forging-transaction-proofs</guid>
      <pubDate>Wed, 04 Mar 2026 00:00:00 GMT</pubDate>
      <description>This is a disclosure of a vulnerability in the Polygon Plasma bridge. The vulnerability has been fixed since July 2024 and the fix has been pushed to the vulnerable library as well.</description>
      <category>Research</category>
      <enclosure url="https://rheinaudit.com/_next/static/media/polygon-bridge-card.0sttmt5bm-asd.png" type="image/jpeg" length="0" />
    </item>
    <item>
      <title>TSTORE Poison: The Solidity Compiler Bug That Silently Corrupts Storage</title>
      <link>https://rheinaudit.com/research/solidity-compiler-bug-tstore-poison</link>
      <guid isPermaLink="true">https://rheinaudit.com/research/solidity-compiler-bug-tstore-poison</guid>
      <pubDate>Wed, 18 Feb 2026 00:00:00 GMT</pubDate>
      <description>TL;DR -- A cache key collision in the Solidity compiler&apos;s via-ir code generator causes delete on transient variables to emit sstore instead of tstore, or conversely causes persistent delete to emit tstore instead of sstore. The direction depends on function selector ordering -- neither direction is safe.</description>
      <category>Research</category>
      <enclosure url="https://rheinaudit.com/_next/static/media/tstore-poison-card.0sbibn7v4w0b~.png" type="image/jpeg" length="0" />
    </item>
  </channel>
</rss>