Hi all,
If you're just now signing in for the first time in 12+ hours, you may just now be finding out that Lemmy World and other instances where hijacked. The hijackers had the full abilities of hijacked user, mod, and admin accounts. At this time, I am only aware of instance defacing and URL redirections to have been done by the hijackers.
If you were not forced to sign back in this morning, contact your instance admin to verify mitigations were completed on your instance.
How?
This occurred due to an XSS attack in the recently added custom emojis. Instance admins should follow the issue tracker on the LemmyNet GitHub, as well as the Matrix Chat. Post-Incident Activity is still on-going.
Currently, it is likely that just your session cookie was stolen, with instance admins being targeted specifically by checking for navAdmin, an HTML element only instance admins had. I do not believe this to affect users across instances, but I have yet to confirm this.
What happens next?
As I am not the developers or affected instance admins, I cannot make any guarantees. However, here is what you'll likely see:
- Post Incident investigation continues. This will include inspecting code, posts, websites, and more used by the hijackers. An official incident writeup may occur. You should expect the following from that report:
- Exactly what happened, when.
- The incident response that occurred from instance admins
- Information that might have helped resolve the issue sooner
- Any issues that prevented successful resolution
- What should have been done differently by admins
- What should be improved by developers
- What can be used to identify the next attack
- What tools are needed to identify that information
-
A CVE is created. This is an official alert of the issue, and notifies security experts (and enthusiasts), even those not using lemmy, about the issue.
-
A code security audit is done. This will likely just be casual reviews by technical lemmy users. However, I will be reaching out to the Mozilla Foundation and Cure53 as they recently did an audit of Mastodon. If there is interest in an external audit of lemmy and the costs are affordable, I'll look into crowdfunding this cost.
Friendly remind that Lemmy.world is considering federating with Meta while Lemmy.ml will not.
I would strongly suggesting ditching Lemmy.world for Lemmy.ml before they can even get started with that stupidity.
Dumb take. Lemmy.world devs simply said it's not likely Threads will federate with Lemmy anytime soon anyways, and they'll make a decision when there is actually a decision to be made.
I've made many comments saying why we should defederate with Threads but I still agree with the admins that there's no point in doing a knee-jerk reaction on a threat that
A) won't happen until at least a few months later
B) likely won't federate with Lemmy anyways
C) isn't actually a threat to Lemmy, but could pose a threat to microblogging websites like Mastodon
So yeah, waiting and seeing isn't stupid.
“Wait and see” is fine.
Federating in the meantime is not.
Stop trying to dance around the heart of the issue.
Dude, Threads isn't federating with anything right now. That's the point, we're not federated so there's no reason to make a decision on something that won't happen yet.
I’m not sure you understand the takeaway from the admin post last night.
https://lemmy.world/post/1274909
Where does it say in the admin post that they are default federating with Threads?
They haven't made a decision, as it's no issue as there is no federation to threads and won't be for the forseeable future.
Making a fuss about it now is as usefull as making a fuss over the sun dying in several million years.
Correct me if I'm wrong, but I don't think Threads even has the ability to federate yet?
Maybe ditching Lemmy.world makes sense but signing up on Lemmy.ml doesn't. Pick smaller instances and spread out guys. That's the entire point. :)
It's a bit funny that 100k users signed up on the same instance... :)
here are some great instances https://github.com/maltfield/awesome-lemmy-instances
"Ma'am... this is an Arby's."
Threads is not a Lemmy issue. Mastodon is where the concern lies.
NOT A LEMMY ISSUE IDIOTS!
While this is definitely a discussion to be had (I've created a few accounts on different instances). Posting that here is just adding onto the drama.
Not sure how you view it that way.
It’s just good advice for people who want to stay the hell away from a company like Meta that was willing to hand over private data to assist authorities in arresting a woman for exercising her reproductive rights.
Really not thrilled with the Lemmy.world users trying to downplay just how ridiculous the idea of federating with Meta is.
Is it possible to block .world entirely yet?
Look, Lemmy.world takes the rational way where it says there is no use to panic. Let's be rational and analyze the situation rationally and go from there.
I support Lemmy.world. Let's see how the situation develops and let's make a rational decision with cool heads.
User-level instance blocking is not yet implemented. You could use an instance that is defederated from lemmy.world, such as beehaw.org.
Or a smaller instance! lemmy.ml wasn't meant to be the main Lemmy hub, and it would help the load on the larger instances to spread users out.
yeah, Lemmy is instilling a ton of confidence when instances disappear overnight (vlemmy) and others get all their data hacked and close off all communication with the largest user base that will exist in the fediverse. Y’all really about to make people go back to Reddit
It's already over, actually kind of boring. Please hack again.
Right… so why open up the gates to Meta then?
That will push people right back to Reddit.
I would strongly recommend making decisions for yourself.
Lemmy.ml is filled with Rankies and Stalinists who regularly remove any content critical of communist states
I ran screaming from FB. Like, hair on fire running. That place is a roiling pot of piss. I would 100% not interact with ANY instance that has federated with them. They are a cancer that will infect this next big thing