Jaredfromsubway.eth Sandwich Attack Bot Exploited for $7.5 Million

Jaredfromsubway.eth’s sandwich attack bot has been reported exploited for $7.5 million, with the evidence package for this story centered on an Intellectia report, an Etherscan address, and a Blockaid post on X. Because the stored research is only partially verified, the safest reading is that a bot or contract tied to the Ethereum MEV operator was compromised, while several operational details remain unconfirmed.

The clearest externally attributable claim comes from Intellectia’s report, which describes the event as an exploit affecting a MEV bot contract associated with Jaredfromsubway.eth. That matches the narrow framing used in the brief: this was reported as a problem with a sandwich-attack bot setup, not as a routine wallet drain affecting a broader group of users.

What the evidence set shows

The same research bundle points readers to an Ethereum address on Etherscan as the on-chain reference attached to the story. What the brief does not preserve is equally important: there are no transaction hashes, token balances, timestamps, or labeled counterparties copied into the evidence set, so this draft does not claim to know the exact route of the outflow or which assets made up the reported loss.

A Blockaid post on X is the only named security-monitoring reference in the package alongside the report and explorer link. Because the post text is not reproduced in the brief, the article can only say that a public security account was part of the early signal around the exploit, not that Blockaid confirmed a specific root cause, exploit method, or recovery path.

The amount itself should still be read as reported rather than independently reconstructed from the available material. The present brief anchors the story to the Intellectia report, the Etherscan address, and the Blockaid reference, but it does not include a readable transaction summary that would let readers verify the full total line by line.

What remains unverified

• The reported loss size traces back to the external reporting record, not to a transaction breakdown stored in the brief.
• Operational disruption is unconfirmed because neither Blockaid’s X post nor the Etherscan reference is reproduced here with evidence showing whether the bot stopped trading, restarted, or shifted activity elsewhere.
• Traceability exists at the address level through a specific Ethereum explorer entry, even though the brief does not preserve the transaction-level context needed for a fuller reconstruction.

That narrower reading matters because it keeps this story in the operational-security lane. Readers comparing it with Coinwy’s separate coverage of crypto kidnappers who robbed a Minnesota family of $8M, Ether market pressure, or governance changes at Sonic Labs should keep the categories distinct: the evidence here, anchored by Intellectia, Etherscan, and Blockaid, points to risk around an Ethereum MEV bot rather than to a broad market move or an offline crime case.