Skip to navigation

Threat reportThreat IntelligenceTL-2026-6234

Court acquits Peraire-Bueno brothers in alleged $25M Ethereum MEV-Boost relay exploit case

lowRESOLVED

On 2026-11-16/17 US District Judge Jessica Clarke entered a judgment of acquittal for Anton and James Peraire-Bueno on wire fraud and money laundering charges tied to an alleged ~$25 million Ethereum theft carried out in about 12 seconds. Prosecutors alleged the brothers used bait transactions and a vulnerability in MEV-Boost relay code to obtain a proposed block's contents early and reorder it; the judge found the government failed to prove material misrepresentations.

Key facts

IdentifiersTL-2026-6234
Also known asMEV Brothers case, United States v. Peraire-Bueno
SeverityLOW
Affected productsEthereum ecosystem MEV-Boost relay
ToolsMEV-Boost
MITRE ATT&CK techniquesT1190 Exploit Public-Facing Application, T1565.002 Transmitted Data Manipulation, T1583 Acquire Infrastructure, T1595 Active Scanning, T1657 Financial Theft
MotivationFINANCIAL
Target sectorsfinance, cryptocurrency, decentralized-finance
Target regionsGlobal
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-11-17, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-6234 across Splunk SPL, Microsoft KQL and Sigma, covering 6 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: MEV-Boost Relay getPayload Without Prior getHeader — Premature Block Release (Exploitation)

Flags slots where a MEV-Boost relay served getPayload for a proposer pubkey that never called getHeader for that slot, the pattern expected if relay code released a proposed block's full contents prematurely (T1190, T1565.002). Alleged in the Peraire-Bueno case (TL-2026-6234); lets relay operators and builders validate relay integrity. Context: the MEV-Boost relay exploit is a prosecution allegation (acquittal entered 2026-11); no CVE, wallet or hash IOCs were published, so this is a behaviour-first heuristic over operator-defined log sources.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1190, T1565.002
  • Data sources: mev-boost relay application logs (index=mev_relay)
  • Severity: medium
  • Confidence: medium

Splunk SPL

index=mev_relay sourcetype="mev-boost-relay:json" earliest=-1h (msg="getHeader*" OR msg="getPayload*")
```comment
Field contract: msg, slot, proposer_pubkey, client_ip, user_agent are extracted from the relay JSON logs.
Normal MEV-Boost flow is getHeader (bid) then getPayload (signed blinded block) for the same slot and proposer.
```
| eval stage=if(like(msg,"getHeader%"),"header","payload")
| stats earliest(_time) as first_seen latest(_time) as last_seen sum(eval(if(stage="header",1,0))) as header_calls sum(eval(if(stage="payload",1,0))) as payload_calls values(client_ip) as client_ips values(user_agent) as user_agents by slot, proposer_pubkey
| where payload_calls>0 AND header_calls=0
| eval finding="MEV-Boost relay getPayload without getHeader for same slot/proposer: possible premature release of proposed block contents"
| table first_seen last_seen slot proposer_pubkey payload_calls header_calls client_ips user_agents finding

Microsoft KQL

MevRelayLogs_CL
| where TimeGenerated > ago(1h)
| where Msg_s startswith "getHeader" or Msg_s startswith "getPayload"
| extend Stage = iff(Msg_s startswith "getHeader", "header", "payload")
| summarize FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated),
    HeaderCalls=countif(Stage == "header"), PayloadCalls=countif(Stage == "payload"),
    ClientIps=make_set(ClientIp_s, 10), UserAgents=make_set(UserAgent_s, 10)
    by Slot_d, ProposerPubkey_s
| where PayloadCalls > 0 and HeaderCalls == 0
| project FirstSeen, LastSeen, Slot_d, ProposerPubkey_s, PayloadCalls, HeaderCalls, ClientIps, UserAgents

Sigma

title: MEV-Boost Relay getPayload Served For Unknown Block
id: 6f1c2a9e-3b7d-4e58-9a41-0c5d8e7b1a21
status: experimental
description: Relay application log shows getPayload failing because the block or header was not previously served. Single-event approximation of the getPayload-without-getHeader sequence; adjust message strings to relay version. Alleged MEV-Boost relay premature release (TL-2026-6234).
references:
    - https://www.bleepingcomputer.com/news/security/court-clears-brothers-of-25-million-ethereum-crypto-heist-charges/
    - https://decrypt.co/230874/feds-arrest-crypto-bros-attacking-ethereum-mev-exploit
author: Threadlinqs Team
date: 2026-11-17
tags:
    - attack.initial-access
    - attack.t1190
    - attack.impact
    - attack.t1565.002
logsource:
    product: mev_boost_relay
    service: relay
detection:
    sel_endpoint:
        msg|contains: 'getPayload'
    sel_error:
        msg|contains:
            - 'not found'
            - 'unknown block'
            - 'mismatch'
    condition: sel_endpoint and sel_error
falsepositives:
    - Proposer restarts or missed header calls during relay failover
    - Relay cache eviction after reorgs
level: medium

Known false positives:

  • Proposer failover to a second mev-boost instance that never called getHeader on this relay
  • Relay restart or cache eviction around reorgs
  • Multi-relay setups where the header came from a different relay

Tuning notes: Replace the msg strings with your relay build's actual log messages. Widen the window if relays are load-balanced. Exclude proposer pubkeys of your own validators. Pair with relay-to-builder timing data for stronger evidence.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • MEV-Boost Relay API Probing — High-Volume Error-Heavy Client (Exploitation Recon) · unlock with TL Creds
  • Mass Validator Key Generation Or Import — Concealed Validator Set Build (Post-Exploitation Infra) · unlock with TL Creds
  • Validator Or Relay Host Egress To Anonymizer, Privacy-Layer Or Lax-KYC Exchange Destinations (Hidden Infra / Laundering Egress) · unlock with TL Creds
  • Repeated Failed blinded_blocks Submissions To MEV-Boost Relay (Exploitation Attempts) · unlock with TL Creds
  • mev-boost Started With Unlisted Relay Endpoint (Untrusted Relay Exposure) · unlock with TL Creds
  • DNS Lookup Of Crypto Privacy-Protocol Or Tor Gateway Domains (Laundering Egress / Hidden Infra) · unlock with TL Creds
  • Searcher Bundle Landed Reordered or Altered — Block Reordering Impact (Post-Exploitation) · unlock with TL Creds
  • Bait Transaction Probing Of MEV Bot — Rapid Small-Value Gas-Varied Transactions (Victim Selection / C2-Equivalent Staging) · unlock with TL Creds

Indicators of compromise

As of 2026-11-17, Threadlinqs Intelligence tracks 6 indicators of compromise for TL-2026-6234.

6 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

This record documents the legal outcome of United States v. Anton Peraire-Bueno and James Peraire-Bueno (SDNY, case 1:24-cr-00293) and the technique the prosecution alleged. It is retained as low-severity context: no CVE, no CVSS, no IOCs such as wallet addresses or transaction hashes were published in the cited sources, and the defendants were acquitted. Everything about the method below is the government's allegation, not an established finding.

According to the indictment as reported in May 2024, the two former MIT students began preparing in December 2022. They allegedly set up a series of Ethereum validators in a way that hid their identities, then placed test 'bait transactions' to identify variables that attract MEV bots, selecting 'Victim Traders' who operated such bots. Prosecutors alleged the brothers found and exploited a vulnerability in MEV-Boost relay code that caused the relay to release the full contents of a proposed block prematurely. With that early view of pending private transactions they allegedly reordered the block to their advantage, altered the victims' transactions, and published the block to Ethereum, taking about $25 million in cryptocurrency in roughly 12 seconds. Other reporting says 16 validators were created and three specific traders were targeted.

Prosecutors further alleged concealment and laundering: multiple cryptocurrency addresses, intermediary addresses, shell companies, foreign exchanges with lax verification, and a privacy-layer network; refusal of requests to return the funds; online searches for attack methods and ways to hide involvement; and hiring attorneys with crypto and extradition expertise. The defense argued the activity was a legitimate trading strategy and that MEV-Boost had no terms of service, while the spec described the software as designed to stop validators modifying blocks. The first trial ended in a mistrial on 2025-11-07 after a deadlocked jury. In November 2026 Judge Clarke granted the defense motion and entered a judgment of acquittal, writing that because the Government failed to prove that the defendants made any material misrepresentations in executing their scheme the motion was granted, and that the question was whether the evidence could support wire fraud convictions, not whether the conduct was moral or violated uncharged crimes.

Defensive takeaway: the case illustrates the MEV-Boost trust model risk (proposer/relay early release of block contents, private-order-flow exposure to validators) and the legal uncertainty around MEV extraction. Searchers and MEV-bot operators should treat pre-inclusion visibility of their transactions to relays and proposers as a risk. No specific exploit code, CVE or patch is identified in the sources.

MITRE ATT&CK techniques by tactic:

Initial Access

T1190 Exploit Public-Facing Application

Impact

T1565.002 Transmitted Data Manipulation; T1657 Financial Theft

Resource Development

T1583 Acquire Infrastructure

Reconnaissance

T1595 Active Scanning

Remediation

Immediate actions

  • MEV-bot operators: review exposure of pending/private transactions to relays and proposers
  • Monitor for unexpected block reordering affecting your bundles on Ethereum

Longer-term hardening

  • Follow MEV-Boost relay and builder specification hardening against early release of proposed block contents
  • Track legal developments on MEV extraction and fraud theories in US courts

Affected and fixed versions

  • Ethereum ecosystem — MEV-Boost relay
    Vulnerable versions: Unspecified relay code version alleged by prosecutors

Timeline

  • Per the indictment, the brothers began preparing the alleged scheme in December 2022, studying victim traders' behavior (day not specified in sources).
  • DOJ/SDNY announced the indictment: conspiracy to commit wire fraud, wire fraud and conspiracy to commit money laundering over an alleged ~$25M MEV-Boost relay exploit; the brothers were arrested in Boston and New York.
  • Judge Jessica Clarke declared a mistrial after the jury twice reported being deadlocked.
  • SDNY prosecutors asked the court to schedule a retrial; the defense had moved to dismiss the charges.
  • Judge Clarke granted the defense motion and entered a judgment of acquittal, finding the government failed to prove material misrepresentations.
  • BleepingComputer, citing Reuters, reported the acquittal.

Sources cited

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats