•  Dave   ( @Dave@lemmy.nz ) 
    link
    fedilink
    707 months ago

    I’m gonna take this opportunity to mention LemmyAutomod, for Lemmy instance admins.

    This massive spam attack was unrelenting, but it came in the form of a large number of spam posts that had a small amount of variation. Using the above tool, it really helped to catch most of the spam within seconds or minutes of being posted.

    The dev is really helpful, which is good because I needed some hand-holding, but it has been a fantastic tool with this latest spam wave being the first true test of it. When the spammers started posting images of URLs instead of links, the dev added functionality to detect images that were the same or similar to a reference image.

    In addition, there’s also a Lemmy spam defense Matrix chat set up by Lemmy.world where instance admins post spam accounts so others can ban them on their own instances (and add them to their automod).

    • @Kbin_space_program@kbin.social

      @ardi60@reddthat.com This has not been my experience at all. There was/is a lot of spam lingering on KBin long after it was removed from the federated source. I don’t know if that’s an issue with the removal being done in an unfederated way (bulk deletes at the db level), a sync issue cause by the recent kbin.social outages or just a general federation bug.

      My kbin.social account has been @'ed in hundreds of comments and some of the most popular Kbin magazine where Earnest remains the sole moderator were flooded with spam.

      Even this morning I tried reporting spam from a kbin.social account only to be told it had already been report… and yet 16 hours later the bot is still posting with this account.

      I’m glad you’ve found kbin.social usable through all this, but the spam is tbere.

  • This is the best summary I could come up with:


    Over the past several days, attackers have targeted smaller Mastodon servers, taking advantage of open registrations to automate the creation of spam accounts.

    While this is not the first spam attack that has impacted the Fediverse, Rochko notes that only larger servers like Mastodon.social had been targeted previously.

    What’s different this time is that the spammers targeted the smaller and even abandoned servers offering open registration, allowing the bad actors to quickly create accounts and generate spam.

    Because Mastodon’s smaller servers are often hobbyist projects run by enthusiasts they were vulnerable to this sort of attack.

    Many servers were simply shut off as their admins decided it would be easiest to wait out the attack or abandon Mastodon altogether.

    “At the moment, there are no good built-in tools to handle this, as this is a complex issue — federated networks are not easy!


    The original article contains 1,023 words, the summary contains 143 words. Saved 86%. I’m a bot and I’m open source!

  • Mastodon and friends are built as open conduits with very little in the way of safety or permissions. Spam should be expected.

    It’s not a Fediverse vulnerability. It’s a Mastodon vulnerability. Don’t want spam? Use a better fediverse technology.