https://x.com/mononautical/status/1834196815786225822Well, this is about my case. Based on that post, my transaction had SIGHASH_NONE, which means anyone could have spent the change. I reached out to the support channel for Sparrow Wallet on Telegram, and they explained that, because of this, bots were able to take control of the transaction.
On that post I see:
the original transaction looks like a simple spend of 0.21 BTC from a UTXO of ~0.79 with RBF enabled.
it was replaced almost instantly by the ultra-high-fee tx. so quickly that most of Mempool's servers didn't have time to even see the first tx.
It's for this reason I think SIGHASH_NONE should be disabled from being selected unless the user ticks an "Advanced mode option". And we can actually take this one step further, by hiding any such listbox for the sighash so that they always use SIGHASH_ALL.
Anyway, now that your case has gained traction on social media, I think Foundry USA will notice this and reach out to you.