The title pretty much says it all. In Mollom's favor, an email was sent to a staff member alerting them to the activity. Upon logging in a found a tremendous amount of spam user registrations. I found no way to increase the security of the user registration Mollom in the Mollom settings. Although I could identify the IP address of the incoming spam and add it to the blacklist, the IP addresses were so numerous and varied that it would be a laborious manual process.

So I decided to turn of user registration temporarily. Eventually I turned it back on, but disabled the Mollom module and went with reCaptcha. I hope to have better results with reCaptcha.

Just through you should know.

Comments

stoob’s picture

Status: Active » Closed (fixed)

The registrations continue. Must be some form of spam. (manual?). That mollom or capthca can't stop

sun’s picture

Status: Closed (fixed) » Fixed

Yes, such massive spam attacks can happen. Spammers seem to focus on a single site for a short time-frame then. However, especially in such cases, Mollom's intelligent CAPTCHAs are superior to all other spam protection modules. If spammers are still able to break through, then the measures you've taken (IP address blocking, user registration outage) are the only ways to resolve this.

That said, you can likely remove the IP addresses from your ban list. Such attacks are usually executed from (otherwise innocent) dynamic IPs, so you're likely blocking friendly visitors by blocking those IPs permanently.

dries’s picture

It would be helpful if site administrators could report users as spam to Mollom.com. That is currently not supported by the module. We could turn this into a feature request? :)

sun’s picture

Reporting users to Mollom (and eventually deleting their accounts and posted content) is relatively hard to do in Drupal 6, I think. For D7, we already integrate with the user account cancellation form, so you can report a user to Mollom while deciding what to do with the account and the content.

dries’s picture

Right. Thanks for pointing that out. For Drupal 7, do we have tests for the user reporting? I'd need to check the code. Either way, it seems like it would be important to have good tests for this.

sun’s picture

Yes, we added tests for reporting users into MollomReportTestCase for the original "Mollom for any form" patch. However, the expectations we assert there are not very "special". We just expect that the user is deleted and our form_altered-in procedure is executed (a default message after mollom.sendFeedback appears). For example, we do not expect that all individual posts that are deleted are reported as [chosen feedback option] as well. Not sure whether they should be reported in the first place or just the author (like now).

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.