69
submitted 2 years ago* (last edited 2 years ago) by [email protected] to c/[email protected]

Today, a bunch of new instances appeared in the top of the user count list. It appears that these instances are all being bombarded by bot sign-ups.

For now, it seems that the bots are especially targeting instances that have:

  • Open sign-ups
  • No captcha
  • No e-mail verification

I have put together a spreadsheet of some of the most suspicious cases here.

If this is affecting you, I would highly recommend considering one of the following options:

  1. Close sign-ups entirely
  2. Only allow sign-ups with applications
  3. Enable e-mail verification + captcha for sign-ups

Additionally, I would recommend pre-emptively banning as many bot accounts as possible, before they start posting spam!

Please comment below if you have any questions or anything useful to add.


Update: on lemm.ee, I have defederated the most suspicious spambot-infested instances.

To clarify: this means small instances with an unnaturally fast explosion in user counts over the past day and very little organic activity. I plan to federate again if any of these instances get cleaned up. I have heard that other instances are planning (or already doing) this as well.

It's not a decision I took lightly, but I think protecting users from spam is a very important task for admins. Full info here: https://lemm.ee/post/197715

If you're an admin of an instance that's defederated from lemm.ee but wish to DM me, you can find me on Matrix: @sunaurus:matrix.org

top 50 comments
sorted by: hot top new old
[-] [email protected] 9 points 2 years ago

This should be probably pinned.

[-] [email protected] 6 points 2 years ago

CAPTCHA is the bare minimum. Who the hell turns it off?

[-] [email protected] 6 points 2 years ago

There is an argument to be made that captchas can be automatically bypassed with some effort.

OTOH, the current wave of bots is quite clearly favoring instances with captcha disabled, so clearly it's acting as at least a small deterrent.

[-] [email protected] 3 points 2 years ago

Sometimes, security just means not being the low-hanging fruit.

[-] [email protected] 3 points 2 years ago

Doing no captcha is like leaving the door open, hoping no-one breaks in, instead of at least closing the door (a closed door decreases chance of break in by near 100%, even if it's not locked)

[-] [email protected] 1 points 2 years ago

It seems that the devs are considering to use mCaptcha. Link to the discussion

[-] [email protected] 1 points 2 years ago

Some advanced OCR can hack the easier ones, but it's unusual.

[-] [email protected] 1 points 2 years ago

captchas block script kiddies at the very least

[-] [email protected] 2 points 2 years ago

there's a browser addon that lets you solve Recaptcha with one click:
https://addons.mozilla.org/en-US/firefox/addon/buster-captcha-solver/

it automatically switches to the alternative accessibility option, which is based on typing in words that you hear, and uses speech recognition software to solve it. I'm fairly sure it could be automated quite easily.

[-] [email protected] 1 points 2 years ago

Still way better than nothing at all

[-] [email protected] 5 points 2 years ago

Here we go: https://overseer.dbzer0.com/

API doc: https://overseer.dbzer0.com/api/

curl -X 'GET' \
  'https://overseer.dbzer0.com/api/v1/instances' \
  -H 'accept: application/json'

Will spit out suspicious instances based on fediverse.observer . You can adjust the threshold to your own preference.

[-] [email protected] 1 points 2 years ago

Nice! Would be cool if you could also include current statuses of captchas, emails, and application requirements.

[-] [email protected] 0 points 2 years ago

Tell me how to fetch them and it will. ;)

[-] [email protected] 1 points 2 years ago

I think the easiest option is to just iterate through the list of suspicious instances, and then check {instance_url}/api/v3/site for each of them. Relevant keys of the response json are site_view.local_site.captcha_enabled, site_view.local_site.registration_mode, and site_view.local_site.require_email_verification.

Since it's a bunch of separate requests, probably it makes sense to do these in parallel and probably also to cache the results at least for a while.

[-] [email protected] 2 points 2 years ago

It occurs to me that this kind of thing is better left to observer, as it's set up to poll instances and gather data. I would suggest you ask them to ingest and expose this data as well

[-] [email protected] 5 points 2 years ago

99% of fedi instances should require sign-ups with applications and email. It does not make sense to let in users indiscriminately unless you have a 24h staff in charge of moderation.

[-] [email protected] 9 points 2 years ago

We're trying to capture the reddit refugees as well. It's a fine-line to walk.

[-] [email protected] 7 points 2 years ago

Email + Captcha should be doable right?

[-] [email protected] 3 points 2 years ago

yes, that's the bare minimum until we get better toolset

[-] [email protected] 2 points 2 years ago

Agreed. An application that must be human reviewed is a very large gate that many people will see and just close the site. Myself included.

[-] [email protected] 3 points 2 years ago

Email verification + captcha should be enough. The application part is cringe and a bad idea, unless you really want to be your own small high school clique and don't have any growth ambitions, which is perfectly fine but again should not be expected from general instances looking to welcome Redditors.

[-] [email protected] 5 points 2 years ago

Thanks for the heads up, StarTrek.website has enabled CAPTCHA and purged the bots from our database.

[-] [email protected] 3 points 2 years ago

Starfleet takes changeling infiltrations seriously :P

[-] [email protected] 4 points 2 years ago

This might be related but I've noticed that someone is [likely automatically] following my posts and downvoting them. Kind of funny in a 'verse without karma.

[-] [email protected] 2 points 2 years ago

Karma may mean nothing but the information space is a strategic domain.

[-] [email protected] 1 points 2 years ago

I don't think it's the case here, as I've noticed this after posts in small communities:

  • c/linguistics (~240 members)
  • c/parana (1 member - new comm)

I think that the person/bot/whatever is following specific people.

[-] [email protected] 3 points 2 years ago

Today, a bunch of new instances appeared in the top of the user count list. It appears that these instances are all being bombarded by bot sign-ups.

Yup, I noticed this as well.

Hopefully the mods of the instances will notice this and remove these accounts quickly! Despite this, I think the mods of all instances, and of all communities, had better brace themselves for incoming spam and hate speech.

[-] [email protected] 2 points 2 years ago
[-] [email protected] 2 points 2 years ago

I know from talking to admins when pbpBB was really popular that fighting spammers and unsavory bots was the big workload in running a forum. I'd expect the same for Fediverse instances. I hope a system can be worked out to make it manageable.

As a user I don't have a big problem with mechanisms like applications for the sake of spam control. It's hugely more convenient when an account can be created instantaneously, but I understand the need.

I do wonder how the fediverse is going to deal with self-hosting bad actors. I would think some kind of vetting process for federation would need to exist. I suppose you could rely on each admin to deal with that locally, but that does not sound like an efficient or particularly effective solution.

[-] [email protected] 2 points 2 years ago

Sounds like a spez sponsored attack on Lemmy.

[-] [email protected] 1 points 2 years ago

Or just the unavoidable spam bot accounts coming as long as it's easy and the instance operators being still unprepared.

[-] [email protected] 2 points 2 years ago* (last edited 2 years ago)

Any tips on how to get rid of all the spam accounts? I have been affected by this as well and thankfully captcha stopped them, but about 100 bots signed up before I could stop.

Normally i'd just look through all the accounts and pick out the 4 or so users that are real. But there is no apparent way to view every user account as an admin.

[-] [email protected] 1 points 2 years ago

Did you figure out how to clean it up? You can see a list of users in your local_user table.

load more comments (2 replies)
[-] [email protected] 1 points 2 years ago

Fun fact, they're removing Captcha in the next release.

I won't be upgrading and I anticipate I'll be defederating with any instance that upgrades to v0.18.

Source - https://github.com/LemmyNet/lemmy/issues/2922

[-] [email protected] 1 points 2 years ago

That is true, but because of the recent spam wave there is also an issue to re-add captcha. https://github.com/LemmyNet/lemmy/issues/3200

We'll just have to see how it all shakes out.

[-] [email protected] 2 points 2 years ago* (last edited 2 years ago)

It was brought to my attention that my instance was hit with the spam bots regs. I've disabled registration and deleted the accounts from the DB. is there anything else I can do to clear the user stats on the sidebar? EDIT: I have reversed the stats too.

[-] [email protected] 2 points 2 years ago

You can do this by updating site_aggregates.users in your database (WHERE site_id = 1)

[-] [email protected] 2 points 2 years ago

I'm noobish, but could they be defederated until they get their act together before they spam everybody?

[-] [email protected] 2 points 2 years ago

Yes, and I believe some instances are already doing this

[-] [email protected] 1 points 2 years ago
[-] [email protected] 1 points 2 years ago

Are you already defederating from suspicious instances? If not, What are you planning to do?

[-] [email protected] 1 points 2 years ago

Every time I see that moustache I know to pay attention!

[-] [email protected] 1 points 2 years ago

I suspect that there's going to need to be some analysis software that can run on the kbin and lemmy server logs looking for suspicious stuff.

Say, for instance, a ton of accounts come from one IP. That's not a guarantee that they're malicious -- like, could be some institution that NATs connections or something. But it's probably worth at least looking at, and if someone signed up 50 accounts from a single IP, that's probably at least worth red-flagging to see if they're actually acting like a normal account. Especially if the email provider is identical (i.e. they're all from one domain).

Might also want to have some kind of clearinghouse for sharing information among instance admins about abuse cases.

One other point:

I would recommend pre-emptively banning as many bot accounts as possible,

A bot is not intrinsically a bad thing. For example, I was suggesting yesterday that it would be neat if there was a bot running that posted equivalent nitter.net links in response to comments providing twitter.com links, for people who want to use those. There were a number of legitimately-helpful bots that ran on Reddit -- I personally got a kick out of the haiku bot, that mentioned to a user when their comment was a haiku -- and legitimately-helpful bots that run on IRC.

Though perhaps it would be a good idea to either adopt a convention ("bots must end in "Bot") or have some other way for bots to disclose that they are bots and provide contact information for a human, in case they malfunction and start causing problems.

But if someone is signing up hordes of them, then, yeah, that's probably not a good actor. Shouldn't need a ton of accounts for any legit reason.

[-] [email protected] 1 points 2 years ago

had to create an account to post since my comments from sffa.community and kbin.social weren't showing up.

I'm an admin over at sffa.community. We did notice the bot wave. They never got past email verification. We hve since implemented CAPTCHA and have purged the bots from our database.

You can see we are down to organic users. We've only been officially open for a couple weeks so we're still working on content but we are safe to federate with again, if you'd like.

load more comments
view more: next ›
this post was submitted on 20 Jun 2023
69 points (97.3% liked)

Lemmy

13210 readers
17 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 5 years ago
MODERATORS