The weak link here is: to run a successful scam, you need to publicize the incoming address widely. That allows exchanges to block it. If you keep the address in secret, you can't get the gullible masses to fall for it.

One per Twitter account would have worked better in this case.

More database rows of blocked addresses?

Well, having to trawl for all of them, versus needing to find only one. I assume that leaves the window open longer.

It would be reasonable for exchanges to parse Twitter feeds and other social channels for anti money laundering and fraud signal, similar to Github shipping AWS secrets accidentally exposed in commits to AWS for triage/suspension.

Once you’ve got the infra in place, you can have AML and other compliance staff triage and action from a dashboard (blocking suspect transfers until further review has been performed, and releasing transfers of a review shows nothing suspect).

(Have done some AML/KYC work in the fiat finance space)

One thing I've learned in life is that nothing is as polished or automated as you'd think. I would be surprised if anybody was doing this except maybe high tier law enforcement.

Only because I've seen first-hand how advanced their taint analysis is, so I'm already over that surprise.

There are companies that do that and make AML/KYC databases for the exchanges to use.

multiple addresses, mixing, small batches, etc. there are tons of ways to evade exchange restrictions.

You can, but typical spam target won't, because they don't think they need to - they think it's a legit thing so they don't need to make any effort to hide it.

The most recent Elon Musk tweet (2:38 pm PDT; I cannot believe Twitter hasn't locked this down yet) used the same address.

i saw another one 2 minuses ago. remarkable twitter has not fixed it yet.

I read somewhere that they hacked it multiple times. The first tweet got taken down and then it got posted again.