EDIT: This has now been fixed as of 10 PM GMT (give or take), thanks to site admins for their swift response!
Just clicked on a story on GaySpiralStories while logged in and was immediately redirected to another site (see below) that spammed my history so I wouldn’t be able to return if I clicked the back button, tried to make me click a button to verify my age, and requested the ability to send me browser notifications. This effectively disables story access completely, and gets right past my ad and script blockers somehow. If someone could please ensure it’s disabled, that would be much appreciated.
Its URL is: Age check
I’ve just been getting it too, My antivirus was blocking it so I didn’t know what was happening but it’s apparently a known thing to them so clearly whatever adware this is, is known. The story pages open for a split second and then direct to the “Age check” link.
This happened to one of my stories and it is really frustrating. Can it be fixed please? The origin appears to be a comment I received on the story.
Seems to have been happening since at least 4:19 Pm UK time
Can confirm, same thing happens to me. Obviously I didn’t click anything, but can’t access any stories at the moment.
Happening the same with me. Any story I choose gives me the ad and makes the site inaccessible.
This is specific for stories dated 30.10.2023 sbut not for 29.10. Plus I happened to try extract the text with a tool, I came across this string:
"title": "Age check"
This is obviously a malicious third party attack on the site. I’m certain when Martin sees all this, he’ll deal with it. Until then, please be patient
Yeah, it’s a third-party attack… From what I can tell, it’s infested the comments section with ‘spam’ comments, which (if loaded) force-redirect the site to spam pages.
So pretty much, any web page that you load which has the ‘spam’ comment on it will now automatically redirect. That includes (a) loading any story that the bot has commented on, and (b) loading the entire comments tab itself. (And also, loading up the user profile of the bot commenter itself, which I discovered when trying to look at it.)
I’m not a programmer, so this is just my observations from trial and error! I think @Martin will be able to fix this once he is available and has time to do so. In the meantime, yes, we’ll try to be patient…
And just following up to say that I’ve made an announcement on the site proper about the bot, so people are aware of the problem and know it’ll be looked at soon.
Yay, it’s fixed! Big thanks to @PhilipK and @Martin for so quickly responding.