Skip to:
Content
Pages
Categories
Search
Top
Bottom

Spam, Spam and more spam

Viewing 25 replies - 26 through 50 (of 82 total)
  • @bbrian017

    Participant

    I added the line. as suggested.

    /* That’s all, stop editing! Happy blogging. */

    define( ‘BP_REGISTER_SLUG’, ‘yourregisterslug’ );

    /** WordPress absolute path to the WordPress directory. */

    That’s what it looks like.

    Andrea_r sorry I’m in three different threads right now I feel like your chasing me around haha!

    @apeatling

    Keymaster

    Don’t add it below the “Stop Editing” line.

    @bbrian017

    Participant

    Alright I have added right after

    define( ‘COOKIEPATH’, ‘/’ );

    and right before

    /* That’s all, stop editing! Happy blogging. */

    What is this suppose to do anyways? I’m not sure I understand how this stops spam.

    So now my wp-config is like this,

    define( ‘COOKIEPATH’, ‘/’ );

    define( ‘BP_REGISTER_SLUG’, ‘randomcrazyslugger’ );

    /* That’s all, stop editing! Happy blogging. */

    /** WordPress absolute path to the WordPress directory. */

    @mlovelock

    Participant

    @Bbrian017 – the register ‘slug’ is the path to your register page. So the default is yourdomain.com/register – yours would now be yourdomain.com/randomcrazyslugger

    Given that, you probably don’t want your register page to be ‘randomcrazyslugger’ so you might want to change it to something that makes a little more sense to your site / your users.

    @bbrian017

    Participant

    Thanks for the tip mlovelock I have done what you said. Seems it has stopped some spam but 10 minute later it all starts again.

    They must get error messages stating the register page doesn’t exist or something.

    @bbrian017

    Participant

    My spam issue is just not stopping and it’s driving me insane!!!!

    @bbrian017

    Participant

    Seriously no one is having spam issues like I am?

    13 accounts since my last post!

    please any help here would be great

    @stripedsquirrel

    Participant

    Did you try deleting wp-signup.php?

    And have you made sure that all spam users have been ‘spammed’ so they cannot just simply add/open new spam users/blogs?

    @nonegiven

    Participant

    Just a question, perhaps this should be on dev, but would it not be possible to have certain customizable elements which each and every installation of WPMU/BP had to create whilst doing an install, e.g. the name of the pages and hooks that the sploggers exploit?

    Yes, they know which pages and what code to look for … but if this was having to be changed during each and every installation, would it not work to stop them?

    Excuse my ignorance, we suffer sploggers but I have no idea what it is they are exploiting.

    @nonegiven

    Participant

    What recommendations are there for a captcha or a custom field creation that fits into the BP 1.2 registration process?

    I have tried a few plugins but they don’t work in BP 1.2 and dont appear in the registration.

    Yes, logging on and custom profiles etc are OK … but this open door approach DOES pass on a lot of janitorial work to site admins

    It seems strange that there is no default to offer some basic kind of obstacle to registration in the blog registration process … it is like building a house with wide open doors.

    Buddypress only adds layers on top of WPMU liabilities what with the attraction of Activity Directory and so on. It looks embarrassing to have it all advertised their by default.

    @foxly

    Participant

    Again to the two guys being relentlessly spammed: post the domain names that you are having problems with and I will try to find out what’s going on.

    ^F^

    @andrea_r

    Participant

    “would it not be possible to have certain customizable elements which each and every installation of WPMU/BP had to create whilst doing an install, e.g. the name of the pages and hooks that the sploggers exploit?”

    They look for the default registration slug. You already have the ability to change it.

    @nonegiven

    Participant

    Think it through … it is a kind of Microsoft moment

    Spamming WPMY/BP is only popular enough because there are significant numbers of unmodified installations going on.

    Because there are a significant numbers of unmodified installations going on we … and our servers … all take a hit on this crap.

    So … disincentivize the platform by making that custom modification obligatory … for all … during the installation process.

    Spammers would face a pretty impossible or unrewarding task and move their attentions elsewhere.

    Does that work logically and technically?

    It is not good enough just to point out one can change it … the problem is not enough people are and hence we are all paying for the vulnerability of the platform.

    So shut that vulnerability off. Simple, no?

    @pushi22le

    Participant

    My solution against spam:

    I replaced the whole content of wp-signup.php with

    header( ‘Location: http://mysite.com/register’ ) ;

    Since than no more spam :)

    @nightowl99

    Participant

    Well, I pretty much tried most of the suggestions here on this thread, and for a couple of days it was quiet. But since yesterday a new and much more aggressive wave is battering my poor little site with as much as 70 new accounts and blogs per hour.

    The last wave started shortly after this log entry:

    http://www.webwarper.net/ww/~av/www.google.com/search?hl=en&q=site:.NET%20inurl:%22register%22%20intext:%22Registering%20for%20this%20site%20is%20easy,%20just%20fill%20in%20the%20fields%20below%20and%20we%27ll%20get%20a%20new%20account%20set%20up%20for%20you%20in%20no%20time.%22&start=10&sa=N

    These accounts don’t have ANY fields filled out from the BP registration form. Even if I re-write that page they’ll just pick something else to hunt for. I’m back to asking folks to contact me if they want to join the site, but that’s a major deterrent for most, understandably.

    @andrea_r

    Participant

    Block the registration page from the search engines. JUST the register page.

    @bpisimone

    Participant

    @Andrea_r good thought, how would that look like?

    @hnla

    Participant

    Google ‘robots.txt file’ for starters

    @takeo

    Participant

    I’m starting to get hit now :o( I have had a custom slug for weeks. I added a robots file today disallowing bot access from /my-signup-slug/ and also installed invisible defender but I’m still getting spam registrations. I also just deleted my wp-signup.php file. I’m going to try hashcash. I’m also considering a htaccess file that simply bans ALL traffic to the entire website from Russia, China and any .info domains.

    @nightowl99

    Participant

    I must be overworked or hallucinating. Signups are disabled, wp-signup was deleted some time ago, and they are still creating new accounts and blogs as we speak! How is this possible? For a while I kept entering the ip s in wp-ban and had given up on that plugin, but I noticed it caught about 600 attempts in the last 24 hrs. Still, a few dozen got through anyway.

    The only other way I can think of is that a member is “inviting” them via the “Allow blog administrators to add new users to their blog via the Users->Add New page.” on the WPMU options page, so I’m going to disable that as well now.

    We’re still a relatively small and young community and all these restrictions and jumping through hoops is hurting us.

    @andrea_r

    Participant

    “The only other way I can think of is that a member is “inviting” them via the “Allow blog administrators to add new users to their blog via the Users->Add New page.” on the WPMU options page, so I’m going to disable that as well now.”

    That’s one of the first things I turn off.

    @takeo

    Participant

    So to sum up:

    • Change your signup slug
    • Add some required custom profile fields (or use the hashcash trick posted at the start of this thread)
    • Disable “Allow blog administrators to add new users to their blog via the Users->Add New page”
    • Delete BuddyPress credit in footer.php
    • Delete wp-signup.php
    • Create a robots.txt file with User-agent: * Disallow: /register/ (or whatever your slug is)
    • If all else fails, use CAPTHCA or preferably a simple random question (what colour is snow)

    Am I wrong or missing anything?

    Also… all of my SPAM registrations were coming from .info domains. I added this to my .htaccess file but I’m not sure it’s correct. I found a million examples via Google search for how to ban full domains or subdomains… but nothing about blocking an entire extension (i.e… whatever.info). Anyway, this is what I wrote:

    RewriteCond %{REMOTE_HOST} \\.info$
    RewriteRule .* - [F]

    @andrea_r

    Participant

    That won’t harm anything, but it won’t stop signups from that domain, just requests.

    In MU, there *is* an option to block certain email domains. There’s a funny way to put in wildcards though.

    @hnla

    Participant

    In MU, there *is* an option to block certain email domains. There’s a funny way to put in wildcards though.

    ,

    Thing is Andrea that doesn’t appear to make a blind bit of difference, we had a number of signups from half a dozen email domains repeated over and over, easy I thought, first line of attack drop those domains in the block list. Didn’t do a thing those same email domains kept coming through. I suspect that when someone looks into it they will find that BP registration bypasses this check somehow! sadly!

    @takeo

    Participant

    Thanks Andrea_r

    So can you tell me how to block signups from anyone with a domain that has a .info extension? I’m sure that 99.9% of people with .info domains are SPAMers. I found the “Banned Email Domains” setting in WPMU but cannot find any documentation about how to use a wildcard or regex in that field. It’s not any ONE fully qialified domain for me… it’s dozens of different domains all ending in .info.

    I’ve done everything in my list above (except CAPTHA or Hashcash) and I’m STILL getting signups from these bastards. Maybe I should try Hashcash. You’re right, the htaccess rule above did nothing. Driving me CRAZY!!! Buggers.

Viewing 25 replies - 26 through 50 (of 82 total)
  • The topic ‘Spam, Spam and more spam’ is closed to new replies.
Skip to toolbar