Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'bots'

Viewing 25 results - 101 through 125 (of 319 total)
  • Author
    Search Results
  • #179402

    In reply to: Stop BuddyPress SPAM

    BuddyBoss
    Participant

    Two more methods that help. I recently had a crazy spam attack – probably 300 fake signups per day. I implemented these two methods and it dropped to near 0.

    1. Change the /register/ slug to something unique. An example would be /create-your-account/, or something of that nature. It just needs to be unique and also make sense in a URL for your user. Spammers targeting BuddyPress look for /register/ as the signup page. It’s all automated so you want to filter them out at the first step.

    2. Add this to your functions.php file in your theme or child theme.

    It presents a dummy field that humans don’t see. Spambots will fill it out, and if the field captures a value it will reject the signup.

    // BuddyPress Honeypot
    function add_honeypot() {
        echo '';
    }
    add_action('bp_after_signup_profile_fields','add_honeypot');
    function check_honeypot() {
        if (!empty($_POST['system55'])) {
            global $bp;
            wp_redirect(home_url());
            exit;
        }
    }
    add_filter('bp_core_validate_user_signup','check_honeypot');

    Credits for #2 go to:
    http://mattts.net/development-stuff/web-development-stuff/wordpress/buddypress/anti-spam-techniques/registration-honeypot/

    I edited it slightly to remove the required redirect. Add that back from his tutorial if you want to. It requires that you make an extra page to send the spammer to, and I personally think that’s not necessary. I actually want them to have no indication their signup failed.

    #179137

    In reply to: Stop BuddyPress SPAM

    contrasupport
    Participant

    5-10 is OK — When I was handling a job application site every month we received 4000-5000 applicants and and had about 75-200 “bad users” we did have people entering bad email for their job application but it was also sometime the applicant mistype their email AND ending up shooting registration confirmation to the wrong/closed/nonexistent email at Gmail/Yahoo/Hotmail etc (I had to deal with those email providers 1-2 times a year to make sure that my Mail Server is not on the blacklist).

    Btw on the Stop Spammers setting add the StopSpamForum API that way it easier for you to check or submit bad user (add Honeypot & Botscout if possible). Also “Check Spam Words” on the setting and add to them if you see a bad username keep popping up with different IPs.

    #176615
    Henry Wright
    Moderator

    Also, rename your ‘register’ page to something else. Lots of spam bots look for /register/ so something as simple as /register-page/ will help hide your sign up form from at least a few of the bots.

    #172894
    danbp
    Participant

    hi @trinzia,

    don’t ask here about YOUR security settings ! We are not reading in chicken guts or in cristal bowls. 😉

    Also, if you use BP 1.8+, a solution given over a year back cannot work (most of time)

    See here an old discussion with a recent answer (2 mounth) – has patch.

    But before to do something, check your WP settings if comments are allowed and/or if comments are allowed for your test post (sorry for this, but… nobody’s perfect ! 😀 )

    Also, if you cheched site indexing by robots (settings > reading) it may be possible that the comments won’t show up on the activity wall.
    Encountered this a few mounth back with bbPress forum answers on a bp 1.7/bbp 2.3 install

    #166763

    In reply to: Untraceable spam user

    mareksgregs
    Participant

    @ubernaut I tried that Wangguard plugin (thanks for introducing it to me by the way, it’s awesome) and when I scanned the user, it’s status came back as “Error – 101”

    I don’t see how my site could be hacked though. Perhaps the problem is in one of my plugins. Unlikely though. All of my active plugins are legit and shouldn’t have spam bots in their files…

    #166446
    inge12
    Participant

    Leofitz, WangGuard will check your user base for spammers and delete them.

    See https://wordpress.org/plugins/wangguard/

    The author says that “WangGuard not only protect your site from sploggers, spam users or unwanted users, WangGuard cleans your database from them. No plugin or service does this, only with WangGuard you will get this feature,” and I believe him. His English may not be too good, but the plugin is really outstanding.

    There’s just one consideration for you: In order to have your database cleaned up, you will have to submit far more than 500 queries the first month. Perhaps you can arrange to pay for a month?

    Here’s my suggestion to reduce database queries after that. (It worked for me.) Buddypress allows for the customization of User Profiles. Add a couple of questions that require a certain amount of intelligence to answer and make them required. That means the form will not be submitted either to WordPress or to WangGuard if the required fields are not filled out. It’s not fool-proof, but it decreased queries on my very busy site to just a few a day.

    Incidentally, I added a question, “How do you plan to participate?” Among the choices offered the user are these:
    “I want to increase my online presence.” and
    “I want to sell my stuff.”

    We don’t need anyone not bright enough to figure out that these replies do not make the user desirable. Now all I need is a script to automatically kick out users who choose these replies. 😉 (As it is, they can be manually deleted if other users report them.)

    I don’t know what happens to a group when all the users are unsubscribed, so this may not be precisely what you are looking for. But WangGuard will make your site secure against almost all sploggers. (One registrant passed all tests on our site, and we had to delete manually, but that person must have registered manually too.)

    Good luck!

    Inge (http://ssnet.org)

    #166405
    Ben Hansen
    Participant

    maybe not as long as you think if you use the backend, can’t you mass delete them that way?

    #166380
    Leofitz
    Participant

    Are there any current plugin solutions which can delete accumulated BP spam groups? The BP Group Management plugin did this, from what I’ve read, but it gives error messages with the current versions WP 3.5.1 and BP 1.7.2

    Any suggestions will be appreciated as I have a couple dozen WP-BP sites and some have 1000-5000 groups that are spam generated. Manually deleting these would take me until 2014!

    rcain
    Participant

    ps. we also use (dreaded) captcha fields (plugin) on forms, but have noted of late there are bots out there (eg: XRummer, et al) scraping such captcha images off the web in order to seed simple AI scripts to bypass such protection. pretty clever stuff & born out by what we see in our logs.

    rcain
    Participant

    @bp-help

    good suggestions. thx. 2 of them r new to me, so other people may find them helpful also.

    on our sites we r using::

    Keith Graham’s most excellent ‘stop-spammer-registrations-plugin’ – https://wordpress.org/plugins/stop-spammer-registrations-plugin/

    – has stopped over 53,000 spammers since feb this year! it uses external lookups on StopForumSpam, ProjectHoneyPot, BotScout, (Akismet, which we dont use), others – thus great collective benefit/advance warning of bad traffic. also traps brute force attacks (bad logins/registrations/comment posts, etc), etc. is simple enough to play nice with most plugins.

    to try & keep as much load off the front-end of the server as possible, we also have set up:

    linux iptables ( & ufw add on )- as the basis of all firewall stuff. also has our manually maintained blacklists & whitelists. various custom rule chains setup. takes a while to get your head around, but is essential.

    linux fail2ban – essentially an add on to iptables, puts people in jail for bad behaviour – eg: brute force attacks against ssh, ftp, mail logins. we also have set up custom rules detecting bad activity against wp-login.php itself via fail2ban. am looking to do some more with this.

    linux apache – mod-security2, libapache2-mod-evasive, libapache2-mod-antiloris, libapache2mod-spamhaus – which help protect against general bad behaviour, DDOS, blank header attacks, the infamous ‘Loris’ script (which we’ve experienced!), and bot-nets. still assessing how effective these r.

    we have also had to tune apache on our VPS for resilience in the face of DDOS type attacks and heavy-handed brute force attacks.

    some further good tips here: http://www.dannytsang.co.uk/index.php/apache-2-hardening-tips/ & elsewhere.

    linux logwatch – reports various access stats (the good & the bad & the ugly) via email – very useful indeed for checking whther situation is under control (or not).

    linux rkhunter – scans for rootkits on the server from time to time – just be sure – & particularly useful if u ever do get infected in hunting down the intruder’s code.

    obviously we also have file system bolted down. (there is a good wp plugin to check permissions bolt-down, i forget what its called). we also spend a LONG time analysing logs etc.

    anway, that takes care of many of the bad boys, but we r still left with the following problems to crack:

    1) we have observed that many bad bots/scripts are exhibiting ‘learning behaviour’ (ie. heuristic) and r finding ways around fail2ban rules/jails, etc. in particular:

    a) rotating IP addresses to match ‘ban counts’ – currently we have them wasting an IP address every 3-4 attempts, but they still seem to have an inexhaustable supply, else are spoofing extreamly well.

    b) varying their retry period to match the length of jail sentence. (ie. they are not wasting their mips whilst in jail, just enough to detect when they are released,record it, and tune their future responses).

    2) content scrapers, probes and bad-bots generally – these r wasting enormous resource on our servers. typically i would suggest such ‘bad traffic’ is responsible for over 50% of total server load (ie. not good at peak times on a busy site). additional problems we r facing here:

    a) bad bots often spoof the agent string to pretend to be eg. google, bing, etc. the only way u can tell is by reverse lookup of ip address and try and match to one of well known range of ‘good bot’ addresses. but, despite fact that many ranges are well known, most of them are never actually published or confirmed, many are variable. i am not aware of any definitve list of ip addresses of good bots (though there is http://www.iplists.com/ whichis not bad, & http://www.webmasterworld.com/search_engine_spiders/ which is often helpful – these are very much ‘best efforts/as seen in the wild’ lists.). this problem worsens with the rise of social network agregation services, other (legitimate) content agregators, and personal content aggregating software on mobiles, tablets, etc.

    idea: i am thinking of writing a script/plugin/rule to do smart lookup of ip against good bots list, & to automatically maintain that (collective) list. ideally, this is a service that someone like spamhause, or projecthoneypot should offer, since they already have the infrastructure. but, we’ll see. the script will detect traffic ‘purporting to be a SE bot, of any kind and to ban it via iptables if it isnt in the approved list/doesnt check out. the risk is in false positives and harming ones SEO. anyone any thought in this area?

    b) probes & sniffers hunting out wp/bp forms, ajax ports, plugin files, forms, etc – in advance of main attack by penatration/spamming bots. typically always use swiftly rotated ip’s. many many variants out there. usually they have no luck on our sites, but that does not stop them trying in vast numbers (bot-nets, collectives? hives?) and harming out response times, etc.

    idea: url obfuscation has been brought up on this forum before, particularly for eg: login, registration, admin url’s, etc. i am thinking of creating a plugin to dynamically hash encode links of choice using someething based on wp forms nonce system. not only useful for causing probes & hackers pain, but also to help thwart media thieves. obviously, scripters will soon respond by just snanning for link titles in html, so not bullet proof in any way, but they will at least be on 1-time request code, so causing them page reload every request & less sophisticted scripts will be totally wasting their own time.

    anyway. these have been my thought so far. would love to hear experience/insights of others.

    unfortuntely wordpress & buddypress sites in particular represent the richest of prizes for hackers, content scrapers, spammers, etc – & they r really on our case. furthermore, there is some BIG money involved, from porn to pharma to credit card fraud; that means some very smart programmers being paid excellent rates, to hack our systems, full time. add to that, the 10’s of millions of infected machines out there (often unknowingly) operating as botnet drones, trying to pernetrate our servers 24×7, steal our machine resources and steal our members personal data. it is a war of attrition.

    all further experience, ideas welcome, here.

    bp-help
    Participant

    @dice2dice
    You can change the register page name and slug to sign-up.
    You can also try using Private Community For BP:
    You will also need to change line 27 in private-community-for-bp.php from /register to /sign-up to reflect the change of the register slug.
    If your not using it you can get it here:
    https://github.com/bphelp/private_community_for_bp
    Another thing you can try is this small plugin “Spam Killer” which creates a hidden field humans can’t see, spam-bots will see it and fill it out and get a message indicating spammy behavior and it rejects their registration. Get it here:
    https://github.com/bphelp/bp-spam-killer
    Please read the readme.txt for complete instructions for usage for both plugins.

    #165438
    bp-help
    Participant

    @tux-kapono
    Why would it be confusing unless you have several admins? Subscribers should not have access to how many registered users there are in the dashboard anyway. Unless those users are active participants wouldn’t it kinda mislead new legitimate registered users that there is more active members than what is truly there? Most likely the registered users that never logged in was either spam-bots or human spammers and most people fight that tooth and nail. If you have several admins then I would just communicate that to them.

    #165279
    bp-help
    Participant

    @wpbp
    I produced a small plugin that is geared toward automated spam attacks but I haven’t gotten any feedback as far as its effectiveness:
    https://github.com/bphelp/bp-spam-killer
    As far as spam attacks from real users I think there are helpful solutions out there but spammer hacker types will always find way to circumvent any prevention method so the best prevention as an admin is being active on your site.

    #165277
    inge12
    Participant

    One plugin that looks good for preventing registration spam is WangGuard. (Search for it in the WordPress repository.) I’ve just installed it, so can’t tell you if it’s as good as it sounds. (I run a very busy blog and allow commenting by unregistered users. Akismet catches spam and Conditional Captcha deletes it without my seeing it. The latter reduced spam from hundreds of comments a day [marked by Akismet] to near-zero. Only the occasional human spammer gets in.)

    Allowing unmoderated registrations is spammer nirvana. 😉 I allowed posting by unregistered users so I could turn off user registration. Now that I’m wanting to use Buddypress, I had to enable registration but installed WanGuard. Within a few hours, I had one registration attempt — even though Buddypress can’t be seen anywhere on the site yet — but no successful registration, thanks to WangGuard. Tomorrow will tell me more.

    #165246
    @mercime
    Participant

    @wpbp 1. Disable registration in Settings > General.

    2. Disable group creation in Settings > BuddyPress > Settings > Groups.

    3. Disable album creation/uploading of images in the plugin’s settings or are you referring to native WP image galleries?

    You can enable group creation and registration after you’ve done some general housekeeping and adding some spam/spammer prevention.

    #165245

    @wpbp, The problem is that many spam nowadays are not bots but real human spam. I have same problem on one of my installation. all you can do is to ban the domain which has been a source of spam to your site. e.g: spam1@me-now.com. spam22@me-now.com

    when you put “me-now.com” in the following code, it will ban any email from me-now.com, Put it in your functions.php

    http://pastebin.com/a2mTNVZX

    Note: I have 3 sets of this code, I have the one which can ban specific email from gmail, yahooo, hotmail etc without banning other users using gmail, yahooo, hotmail. if you want that aswell i can post it or all the 3 if someone can release it as a free plugin , no problem.

    Naijaping

    #163982
    Hugo Ashmore
    Participant

    You did of course add a robots.txt text file? Use webmaster tools to give more granular control on the site with Google? Disabled feeds in case they are an issue?

    #163777
    bp-help
    Participant

    @hnla
    Well said Hugo! It also seems to me that if it was checked by default it would make it even easier for spam bots to compromise a site.

    #159615

    In reply to: Spam Signups?

    modemlooper
    Moderator

    The reason for that is so many installs are not customized enough and that makes it easy for bots.

    No system is safe from spam.

    #159541

    In reply to: bp blog functions

    @mercime
    Participant

    @somdefabrica double-check the privacy settings of your blog in subsite. It must allow indexing by robots/google.

    #158638

    In reply to: Automated Spam

    Ben Hansen
    Participant

    there is no perfect solution for this problem and these “bots” are actually humans a good deal of the time i have had good experience with WangGuard though.

    #157637

    In reply to: Spam User Registration

    Ben Hansen
    Participant

    There is no perfect solution other then to disable registration entirely but i have had a good experience with WangGuard. FYI a good chunk of these “bots” are actually humans (at least at some point) believe it or not.

    #156701
    modemlooper
    Moderator

    You can’t just install and not take action to limit server requests. You need to cache as much as possible and use a CDN. Also check logs you can have bots hitting site and you can block those.

    Find out what is hitting ajax file and block it.

    #155275

    In reply to: Are you a human plugin

    Ben Hansen
    Participant

    FYI a lot of those “bots” are humans no perfect solution exists some amount of human intervention will always be required to deal with spamming and splogging but…

    i have been having a pretty good experience with WangGuard they are currently blocking about 90 to 95% of our spam registrations.

    #153431
    miguelcortereal
    Participant

    Hi Brajesh,

    the site site is in http://obidosaeroclube.com.

    I’ve received in my GWT a bunch of 404 errors with that link structure.

    This airfield site was previously made in another platform diferent from WordPress and with another domain. Once that the new site got ready I’ve asked the previous site webmaster to make a redirection from the old domain to the new and delete the old site. So he did it.

    After reading you, I guess the redirection made by the old site webmaster is causing this.

    I don’t find another fix for this than block at robots.txt – Disallow: /terms.asp?

    What do you think ?

    Thanks in advance

Viewing 25 results - 101 through 125 (of 319 total)
Skip to toolbar