[Help] Compromised wallet & sweeper bot on Optimism mainnet – any private tx / rescue options?

[hothahaha]

Did you check the documentation and specs?

• Yes

Was there anything unclear or missing?

No response

Did you check for duplicate questions?

• Yes

Similar Questions or Issues Found

No response

Please select the type of request

• Bug Report
• Feature Request

Steps to Reproduce

Hi Optimism team,

I’m looking for guidance on an asset recovery situation on Optimism Mainnet and how to handle it in a way that is compatible with Optimism’s infrastructure and policies.

Situation

• My EOA private key has been compromised and is now monitored by a sweeper bot.
• The sweeper front-runs or races any transaction that tries to fund this wallet with ETH.
• I need to perform one atomic sequence of actions from this compromised wallet:
  • Transfer 2 ERC20 token balances to a new, safe wallet.
  • Call transferOwnership on 1 Ownable contract to move ownership to the new wallet.
• Estimated total asset value: ~$5,000 USD
• Compromised wallet: 0xbdd42....dc8a2
• New, secure wallet: 0x695ec....a06fe

Problem

Because of the sweeper:

• Any ETH transfer to the compromised wallet is immediately taken via another tx / internal tx.
• Normal “fund → send tx” approaches through the public mempool are very likely to fail or be front-run.
• The involved token/contract(s) do not support permit / meta-tx, so I cannot use a gasless pattern where only signatures are required from the compromised wallet.

I understand that Optimism does not currently expose an end-user “Flashbots-style” private RPC like on Ethereum mainnet, and that the protocol/governance cannot arbitrarily revert or modify state.

Questions

I’m not asking for any special rollback, only for technical guidance on what is realistically possible:

1. Is there any recommended way to submit a private or protected bundle of transactions to the Optimism Sequencer (e.g. via a builder / partner relay) so that, within a single block:
   • A safe wallet funds the compromised wallet with just enough ETH for gas, and
   • The compromised wallet immediately sends the ERC20 transfers + transferOwnership call?
2. Does the Optimism Foundation have any documented process or contacts for whitehat / rescue cases like this on OP Mainnet?
3. If there are MEV / builder partners that already support something like eth_sendBundle for Optimism, is there any public reference or documentation you can point me to?

Technical details

• Chain: Optimism Mainnet (Chain ID: 10)
• Compromised wallet: 0xbdd42....dc8a2
• New safe wallet: 0x695ec....a06fe
• Assets:
  • Token A: 0x2fA23....bc232
  • Token B: 0x20CDd....A65ff
  • Ownable contract: 0x8CFA1....B5FD9
• Sweeper behavior: [Any ETH sent to this address is immediately transferred to the bot’s wallet, often within the same block via an internal transaction. e.g. https://optimistic.etherscan.io/tx/0x560d494493c3b463dee4385515607615bc28d15f37887b863296faf68f007db7]

I fully understand that a compromised private key means the wallet should be treated as unsafe going forward; I’m only asking whether there is any supported or recommended path to attempt an atomic rescue on Optimism, or if this should be considered effectively unrecoverable.

Any guidance, links or pointers would be greatly appreciated.

Thank you!

Expected vs. Actual Behaviour

No response

Software Versions

No response

Operating System

No response

Hardware Resources

No response

Configuration Files, Startup Flags & Environment Variables

No response

Error Messages / Logs

No response

Feature Description

No response

Purpose and Benefits

No response

Relevant Context or Examples

No response