We have a file whitelist using SHA256 hashing and image hashbans using PDQ hashing. When an image that isn't in the whitelist is posted, it enters the approval queue for moderators to either add to the whitelist or hashban.
I believe he's an Israeli, as whenever the bot is running an IP on the range 46.120.1XX.XXX will start obsessively stalking the bans page and poll the site's JSON API.
I tried blocking the IP once and sure enough the bot stopped for about 30 minutes until a new one on the same range appeared.
His most recent IP is 46.120.114.214 as of 05/Nov/2025:18:23:31 +0000.
I had a feeling that'd happen hence why I obsessively archived every single piece of activity on the accounts. I locally cloned their repos too but Leto's sole repo didn't have any changes compared to the project it was forked from so it's not worth sharing.
We used to do this on soyjak.party actually and I still do use NSFW score as a signal in autoban filters.
You can get a fairly decent CSAM detector by having a model check if the image contains porn and if the image contains a child. If both are true, flag the image as CSAM.
Not perfect by any means but it's better than nothing and takes some load off the jannies.