There is very frequent cross-board spam which affects most of the NWS boards. This spam advertises child pornography, although the images it attaches don't necessarily contain any. If you janitor a porn board, you probably know how to handle this, but any other janitors might see it in their queue due to it receiving three or more illegal reports.So I would like to stress to all janitors that if you see this spam, do NOT simply ban request it and forget about it. Instead, whenever you see it, you should notify a moderator in IRC immediately so they can wipe all the posts at once. They can do so either from an active thread, or from your existing ban request. Ping mods until you get a response.If you do submit a ban request, use the "Child Pornography (Request or Link)" template.The spam is easily recognizable and looks like what you see in the attached image. It is posted to /e/, /h/, /d/, /u/, /y/, /s/, /hc/, /hm/, and /t/. The posts always come from the same IP so it's easy for a moderator to get rid of them -- just don't BR and move on.
>>3889Thank you.To explain why this post was needed:Ban requests simply do not wipe all posts from all boards. They will for that board's posts. So if they post this only on /b/, their /b/ posts will be entirely wiped away. However, if they have posts on other boards, this will remain and untouched. This is why we ask of you janitors to ping a mod when dealing with this spam.You'll notice in the picture of the website link is usually "_babe". These pictures all have the same format. If you aren't sure, just ping one of us and we will handle it.Thanks for posting this, Anonymous ## Janitor!
>>3889I'd like to extend my thanks for this post as well.These spambots are relentless, and the only way we can battle them is: Communication. Regardless of whether it's these pornbots or raids, we have to make sure we're talking between janitors and mods.
I used to be able to get the sites advertised in these images taken down, but unfortunately the spammer eventually found a web host with less-than-stellar morals, and my takedown requests have been rebuked and ignored.Note to mods: This spam is caused by a virus on the user's computer, i.e., a botnet. The infected individual doesn't know that they are infected, and may be very confused upon appeal. You might want to edit the private ban info to reflect this.
>>3897Have you tried contacting the registrar of the URL?I noticed it's .org, or .com or something. Generally speaking, if the registrar responds to support at all, sometimes you can luck out.I know some hosts like namecheap and dynadot will boot you for DMCA content, it's hard to believe some would put up with CP adverts.It's a way some copyright holders get around the occasional host that doesn't give a crap.
>>3899The domain changes constantly precisely because it is constantly being revoked. However, it's evidently very easy for the person responsible to just get a new one.
Just a heads up, I have been seeing a lot of these reoccurring lately.
>>4451Really? What boards did you see this in? I thought this guy switched to spamming The Fappening.
>>4452I see them in /b/ mostly. I think one popped up in a report on /y/ or /hc/ recently.
This spam continues to be posted on porn boards. Unlike when this thread was made, it should be ban requested with the explicit image template, and you should ping mods in the IRC channel whenever you see/ban request it.
