sunaurus just posted this in the lemmy dev chat:
Reposting from another channel to get this out to as many admins as possible:
Current mitigations:
Remove custom emoji
DELETE FROM custom_emoji_keyword;
DELETE FROM custom_emoji;
Overwrite content with the exploit
UPDATE comment SET content = '<REMOVED BY ADMIN>' WHERE content LIKE '%