For the most part, you don't have to do anything other than reject the edits as spam if they have not yet been rejected by others in the community. This will train our spam layer on the origins of the abusive edits, and the noise will soon stop.
Don't lessen the quality of your answer to try and stop this, we have a system in place so that it's not necessary to do so.
Note that as of March 2014, suggested edits rejected as spam on posts that are known spam targets will result in an IP ban. Additionally, as of April 2017, certain suggested edits rejected as spam show up as fake 404 errors, reducing the incentive for spammers to spam edits fully knowing that they get rejected.
Hey, wait - I tried that and all, but it hasn't stopped, it's been weeks.
If this is the case, then your post might be the target of a 'snow shoe' spammer - one that uses a vast number of networks to try and inject a payload. We do monitor for this on a weekly basis and make some adjustments, but occasionally (depending on the size of the bot net trained on us) some stuff passes through.
If that's the case, contact the community team with the following information:
- The URL of the post (be it question or answer), just copy the 'share' link under the post to obtain this.
- How long this has been happening (so we can better scope a query)
Your ticket will then be assigned to someone familiar with the spam system that can run a query and make sure blocks are of an appropriate breadth.
Remember - most people won't see this annoyance and if you do, it generally only lasts a day, or a few days tops. Please give it at least a week before contacting us, or there might not be quite enough activity to dig through in order to block it effectively.