<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss/styles.xsl" type="text/xsl"?><rss version="2.0"><channel><title>Lemma Critical Brief</title><description>Structured incident-analysis reference collection from Lemma Oracle. Each Brief examines a failure primitive and the gap that strengthening detection alone cannot close.</description><link>https://lemma.frame00.com</link><language>en-us</language><copyright>2026 Lemma Oracle / FRAME00, Inc.</copyright><atom:link href="https://lemma.frame00.com/critical/briefs/feed.xml" rel="self" type="application/rss+xml"/><item><title>GTG-1002 — The First Reported AI-Orchestrated Espionage Campaign Where the Agent Executed 80–90% Autonomously, and Agent Authority Was Never Independently Verified</title><link>https://lemma.frame00.com/critical/briefs/009-gtg1002-ai-orchestrated-espionage</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/009-gtg1002-ai-orchestrated-espionage</guid><description>On 2025-11-13, Anthropic disclosed an incident in which a Chinese state-sponsored group (internally designated GTG-1002) misused an AI coding agent to autonomously execute 80–90% of the attack without human intervention. Detection occurred in mid-September 2025; the group attempted to compromise approximately 30 targets (major tech, financial, chemical, and government entities) and succeeded against a small number. The AI carried out reconnaissance, vulnerability discovery, exploit code generati…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 03 Agent Authority Proof</category><category>Agent Runaway</category></item><item><title>Claude Code Source-Leak Lures — Weaponizing Trust Signals and GitHub Releases as a Provenance-Spoofed Delivery Channel</title><link>https://lemma.frame00.com/critical/briefs/010-claude-code-leak-lure</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/010-claude-code-leak-lure</guid><description>On 2026-03-31, Anthropic&apos;s npm package @anthropic-ai/claude-code (v2.1.88) exposed a 59.8MB source map containing roughly 512,000 lines (1,900 files) of internal TypeScript source via a packaging error. Within 24 hours of the leak, an AI-themed malware distribution campaign that had been operational since February 2026 pivoted to lean on the high-attention event, distributing the Vidar stealer and the GhostSocks proxy via fake GitHub repositories disguised as &quot;the leaked Claude Code.&quot; The same c…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Code Provenance</category></item><item><title>SynthID Watermark Reverse-Engineering — How a Statistical Attack Strips the Provenance Mark from AI-Generated Content</title><link>https://lemma.frame00.com/critical/briefs/011-synthid-watermark-reverse-engineering</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/011-synthid-watermark-reverse-engineering</guid><description>In March 2026, independent researcher Alosh Denny reverse-engineered Google DeepMind&apos;s watermark for AI-generated images, SynthID, and published the method and implementation on GitHub. The attack uses neither neural networks nor proprietary access — only a 2D Fourier transform and phase-coherence analysis (a phase-shift attack) over 123,000 Gemini-generated images — to remove approximately 91% of the watermark energy while preserving image quality almost entirely (PSNR 43.5 dB / SSIM 0.997, res…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Data Provenance</category></item><item><title>The TanStack npm Compromise — Malicious Packages Signed Under a Legitimate OIDC Trusted Publisher, Where a Valid Provenance Signature Did Not Mean a Trustworthy Artifact</title><link>https://lemma.frame00.com/critical/briefs/014-tanstack-oidc-trusted-publisher</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/014-tanstack-oidc-trusted-publisher</guid><description>2026 年 5 月 11 日 19:20–19:26 UTC、JavaScript の主要ライブラリ群 @tanstack/* の 42 パッケージに合計 84 件の悪性バージョンが公開された（CVE-2026-45321、CVSS 9.6）。攻撃者は npm トークンを盗むのではなく、TanStack の正規 GitHub Actions OIDC trusted publisher 連携をワークフロー実行中に乗っ取り、正規の OIDC アイデンティティで署名された悪性パッケージを正規の公開経路から配信した。これは有効な署名付き来歴証明を伴って配布された初のサプライチェーンワーム（&quot;Mini Shai-Hulud&quot;）の一部とされ、同日中に TeamPCP は npm / PyPI で 170 以上のパッケージを汚染した。悪性パッケージは AWS / GCP / Kubernetes / Vault / npm / GitHub / SSH の認証情報を窃取し、GitHub トークン失効を検知すると rm -rf ~/ を実行した。本事案は、来歴の署名（誰が公開したか）が技術的に有効…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Code Provenance</category></item><item><title>The GitHub Internal Repository Breach — A Poisoned VS Code Extension, Live for 18 Minutes, Exploited the Developer Trust Surface</title><link>https://lemma.frame00.com/critical/briefs/015-github-vscode-extension-breach</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/015-github-vscode-extension-breach</guid><description>2026 年 5 月、攻撃グループ TeamPCP（別名 UNC6780）が、毒入りの VS Code 拡張機能を介して GitHub 従業員の開発端末を侵害し、GitHub の内部リポジトリ約 3,800 件をクローン・窃取した。使われたのは正規拡張 Nx Console（nrwl.angular-console）の trojan 化バージョン（v18.95.0）で、VS Code Marketplace 上に公開されていたのは 5 月 18 日 12:30–12:48 UTC のわずか 18 分間。この短時間で、拡張は IDE のローカル環境から 1Password の保管庫、Anthropic Claude Code の設定、npm・GitHub・AWS の認証情報を窃取した。GitHub は 5 月 19 日に検知して即日 IR を開始、重要なシークレットをローテーションし、顧客リポジトリ・Enterprise アカウント・ユーザーデータには影響なしと公表した。本事案は、開発者が日常的に信頼する IDE 拡張という「信頼面」が侵入口になり、その正規マーケット掲載・配布経路が成果…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Code Provenance</category></item><item><title>The Verus-Ethereum Bridge Hack ($11.58M) — A Valid Merkle Proof, But No Verification That the Source Amount Matched the Payout</title><link>https://lemma.frame00.com/critical/briefs/016-verus-ethereum-bridge</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/016-verus-ethereum-bridge</guid><description>2026 年 5 月 18 日、Verus-Ethereum クロスチェーンブリッジから約 1,158 万ドルが流出した。根本原因は、ブリッジが「Verus 側の入力額」と「Ethereum 側の払出額」の整合を必須検証していなかったこと——Ethereum 側 checkCCEValues に source-amount の検証が欠落していた。攻撃者の cross-chain import payload は $0.01 相当の VRSC 入力に対し $11.58M 相当（ETH / tBTC / USDC）の払出を構成していたが、blob の各構成要素（state root・ハッシュ・Merkle Proof）はいずれも有効だったため、Verus notary は受理・承認した。Merkle Proof が暗号的に有効であることと、value claim（入出力額）が意味的に正しいことは別問題である。本事案は Pillar 01（来歴証明）の bridge-config-trust における、cross-chain value claim の独立検証不在を露呈した直近の代表事例であ…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Bridge Config Trust</category></item><item><title>McKinsey Lilli&apos;s Writable System Prompts — The Layer Governing the AI&apos;s Behavior Had No Integrity or Provenance</title><link>https://lemma.frame00.com/critical/briefs/017-mckinsey-lilli-system-prompts</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/017-mckinsey-lilli-system-prompts</guid><description>2026 年 2 月、レッドチーム企業 CodeWall の自律オフェンシブ AI エージェントが、McKinsey の社内向け生成 AI プラットフォーム「Lilli」を、認証情報も内部知識もない状態から 2 時間足らずで本番データベースへの完全な read/write アクセスに到達させた。露呈した最も重大な gap は、Lilli の挙動を統治する 95 件の system prompt がすべて書き込み可能だった点である。攻撃者はこれを悪用すれば、Lilli の回答・遵守するガードレール・出典の引用の仕方をサイレントに改ざんし、同社従業員の 72% が日常利用するチャットボットの出力を毒できた。本事案は実被害ではなく責任ある開示を伴う red-team 実証だが、AI の判断を統治する層（system prompt）と出力の完全性・来歴が独立検証されないという Pillar 02（検証可能 AI）の構造的 gap を、marquee なエンタープライズ AI 運用で露呈した。 ---</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 02 Verifiable AI</category><category>AI Decision Integrity</category></item><item><title>The Robert Williams Wrongful Arrest — When an AI Face-Match Drove a Government Enforcement Action Without Independent Verification</title><link>https://lemma.frame00.com/critical/briefs/012-williams-frt-wrongful-arrest</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/012-williams-frt-wrongful-arrest</guid><description>In January 2020, the Detroit Police Department, on the basis of a false match from facial recognition technology (FRT), wrongfully arrested Robert Williams (a Black American) on a theft charge and held him for approximately 30 hours. The AI match between a still frame from 2018 store surveillance footage and a driver&apos;s-license photograph was treated as &quot;identification of the suspect&quot; without independent corroboration and led directly to the enforcement action (arrest). It is regarded as the firs…</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 02 Verifiable AI</category><category>AI Decision Integrity</category></item><item><title>The Coinbase KYC Insider Breach — When Regulation-Mandated Storage of Raw PII Becomes the Breach Surface</title><link>https://lemma.frame00.com/critical/briefs/013-coinbase-kyc-insider-breach</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/013-coinbase-kyc-insider-breach</guid><description>In May 2025, Coinbase disclosed an incident in which overseas-outsourced customer-support personnel (in India) had been bribed and had exfiltrated and externally sold the KYC data of at least 69,461 customers. The exfiltrated data included names, addresses, phone numbers, email addresses, masked SSNs, bank account identifiers, government-issued ID images, and balance / transaction snapshots; passwords, private keys, and funds were not exfiltrated. The attackers demanded a $20M ransom on May 11; …</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate><category>Pillar 04 Regulatory Attribute Proof</category><category>KYC / AML Disclosure</category></item><item><title>Starlette CVE-2026-48710 (BadHost) — MCP Server Authentication Bypass via HTTP Host Header Manipulation</title><link>https://lemma.frame00.com/critical/briefs/003-starlette-badhost</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/003-starlette-badhost</guid><description>On 2026-05-27, CVE-2026-48710 (BadHost) was disclosed in Starlette, the Python ASGI framework with 325 million weekly downloads. A single-character insertion in the HTTP Host header bypasses Starlette&apos;s path-based authentication middleware. The vulnerability propagates across most of the Python AI ecosystem: FastAPI, vLLM, LiteLLM, Text Generation Inference, OpenAI-compatible proxies, MCP servers, agent harnesses, evaluation dashboards, and model management UIs. X41 D-Sec, the discoverer, charac…</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>Pillar 03 Agent Authority Proof</category><category>Agent Infrastructure</category></item><item><title>Megalodon GitHub Supply Chain — CI/CD Credential-Theft Campaign That Poisoned 5,561 Repositories in 6 Hours</title><link>https://lemma.frame00.com/critical/briefs/004-megalodon-github-supply-chain</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/004-megalodon-github-supply-chain</guid><description>Megalodon, surfaced in May 2026, is an automated supply-chain attack campaign. Within 6 hours, 5,781 malicious commits were pushed to 5,561 GitHub repositories, propagating malware that exfiltrates CI/CD credentials. Initial analyses were published by Safe Dep and Ox Security; Hudson Rock identified infostealer infections as the origin point. The attack chain proceeded by direct push using GitHub credentials stolen from infected developers — without touching the legitimate npm account behind the…</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Code Provenance</category></item><item><title>Cursor + Claude Opus 4.6 Wiped PocketOS Production DB in 9 Seconds — The Unverified Destructive Authority of AI Coding Agents</title><link>https://lemma.frame00.com/critical/briefs/007-pocketos-cursor-db-deletion</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/007-pocketos-cursor-db-deletion</guid><description>On 2026-04-24, at PocketOS — a SaaS for car-rental operators across the US — the AI coding agent Cursor (driven by Anthropic Claude Opus 4.6) wiped the production database and volume-level backup in 9 seconds via a single API call to the Railway infrastructure. On April 25, founder Jer Crane (@lifeof_jer) published the full 30-hour recovery timeline on X, which drew 7.1M views. The AI agent subsequently produced a &quot;written confession&quot; — a document enumerating the specific safety rules it had vio…</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>Pillar 03 Agent Authority Proof</category><category>Agent Runaway</category></item><item><title>Noroboto Attack — AI Document Review Input-Integrity Forgery via Embedded Lying Fonts</title><link>https://lemma.frame00.com/critical/briefs/005-noroboto-lying-fonts</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/005-noroboto-lying-fonts</guid><description>In May 2026, Drew Miller, founder of Tritium Legal Technologies, disclosed the &quot;Noroboto&quot; attack technique. A malicious font embedded in a document intentionally shifts the correspondence between Unicode code points and rendered glyphs, deliberately decoupling what a human reads on screen from the string an AI processes internally. When abused in places where meaning changes substantially — governing law, monetary amounts, dates in contracts — the conclusion an AI document-review system reaches …</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>Pillar 02 Verifiable AI</category><category>AI Decision Integrity</category></item><item><title>Google API Keys Remain Usable for 23 Minutes After Deletion — Independent Verification Gap in Credential Revocation Attributes</title><link>https://lemma.frame00.com/critical/briefs/006-google-api-key-revocation-lag</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/006-google-api-key-revocation-lag</guid><description>In May 2026, Joe Leon, a researcher at the security firm Aikido, disclosed that Google API keys can continue to authenticate for up to approximately 23 minutes after deletion. Across 10 trials, revocation lag was as short as approximately 8 minutes, with a median of approximately 16 minutes and a maximum of approximately 23 minutes. The cause is Google&apos;s eventual-consistency design: deletion information propagates across the infrastructure in stages. Even after a developer who recognizes a leake…</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>Pillar 04 Regulatory Attribute Proof</category><category>Attribute Proof Bypass</category></item><item><title>Discord 2.05 Billion Message Scraping via Public API — How Public Channel Data Gets Redistributed as AI Training Datasets</title><link>https://lemma.frame00.com/critical/briefs/008-discord-scraping</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/008-discord-scraping</guid><description>Between November 2024 and May 2025, a 15-researcher team at the Federal University of Minas Gerais in Brazil used Discord&apos;s public API to scrape 2.05 billion messages (2,052,020,630 messages) from 3,167 servers covering 4,735,057 people for the 2015–2024 period, and published the data online as an arXiv paper and a JSON dataset. The research team claims anonymization through username rewriting and hashing of IDs and messages. Discord&apos;s developer policy explicitly prohibits &quot;using messages obtain…</description><pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Training Data Provenance</category></item><item><title>KelpDAO / rsETH Unauthorized Unlock — RPC Manipulation Attack on the DVN Observation Layer</title><link>https://lemma.frame00.com/critical/briefs/001-kelpdao-rseth</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/001-kelpdao-rseth</guid><description>On 2026-04-18, 116,500 rsETH ($292M, approx. ¥46B) was unauthorizedly unlocked on KelpDAO&apos;s cross-chain protocol. The attack originated from intrusion into LayerZero Labs&apos; RPC cloud environment: internal RPC nodes were manipulated so that the message observations referenced by the LayerZero Labs DVN were forged. The DVN signing keys themselves were not compromised. Under a 1-of-1 single-DVN configuration, a legitimate signature over manipulated data carried sole approval authority, and a fraudul…</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Bridge Config Trust</category></item><item><title>Stake DAO vsdCRV Unauthorized Mint — LayerZero v2 Trust Source Rewriting via Deployer Key</title><link>https://lemma.frame00.com/critical/briefs/002-stakedao-vsdcrv</link><guid isPermaLink="true">https://lemma.frame00.com/critical/briefs/002-stakedao-vsdcrv</guid><description>On 2026-05-27, 5.4 trillion vsdCRV was unauthorizedly minted on Arbitrum across the cross-chain infrastructure governing the DeFi protocol Stake DAO&apos;s vsdCRV. The attacker compromised the Stake DAO deployer private key and used it to rewrite the vsdCRV trust source under LayerZero v2 — the Ethereum-side trusted source from which vsdCRV on Arbitrum accepts cross-chain messages — to a contract the attacker had themselves deployed. The attacker then sent a forged cross-chain message from their cont…</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><category>Pillar 01 Verifiable Origin</category><category>Bridge Config Trust</category></item></channel></rss>