this post was submitted on 10 Jul 2023
43 points (100.0% liked)
Fediverse
17572 readers
27 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 4 years ago
MODERATORS
I think that's a good sign. It probably means the problem is being dealt with by admins. Any communities on the affected instances that have subscribers on other instances will be backed up on those other instances, so most of the content is safe no matter what. I just hope the users on those instances know they can come to others in the meantime.
From the few bits I've read, it sounds like the issue is spreading through comments and involves the markdown parser. This needs dev intervention, not just admins.
it sounds like the issue is spreading through comments and involves the markdown parser.
What do you mean? Is there something that us normal users can do to mitigate this? Or do we just hope that the devs and admins resolve this?
This is the conversation I'm referring to:
https://i.imgur.com/uqW3P8o.png
It may well be that the lemmy.world admin account was compromised as a result of the hack, rather than to make it happen.
Apparently Memmy is immune to this, not sure about other apps. Someone else advised staying loggged out, and maybe be prepared to change your password after it's resolved.
Thanks for the explanation.
I've already made the decision earlier to change my passwords (on all my accounts on different instances) after this has been resolved.
FWIW, right now it seems unlikely that your password was accessible to anyone. Your login cookie may have been taken if you accessed Lemmy on a web browser (apps are likely fine), so you would want to clear your Lemmy cookies and cache once this is over.
But I'm speculating, and changing your password will definitely help!
Thanks!
Fighting the urge to clear my cookies and cache right now, lol!
Looks like it could be some kind of markdown parser injection, where they manage to forcefully close the HTML src property and enter their own
Well, taking the most obviously affected instances down is a good start, anyway.
lemmy.blahaj.zone.just went down too
that is really bad because I am one of the moderator for one of the community in that servers. if this spreads out and took longer than expected. I might consider move my community to other servers.
I'd give it at least a day or two to see how things shake out, unless it's really important to you to have that community up all the time.
yeah 48 hours from now is an ideal timeframe. let's see where it goes.
Bit brave linking direct to an instance. This runs the risk of pulling people out of their apps and onto corrupt pages.
That's the instance I'm logged into. It's safe. You can trust me, I 'm a stranger on the internet
I don't think there's any way to link to a post besides an instance specific link, unfortunately
I really hope they add that soon. They only seem to have instance-agnostic links for communities and users for now.
But I think you can copy that link into the search bar within Lemmy and not get pulled into another instance.
Then don't open the link if you're scared/doesn't fit your OPSEC?
Time to switch instance now, ig.
This seems to be a front-end JavaScript exploit, so theres's a good chance that this is a Lemmy problem, not a Lemmy[dot]world problem. Don't be surprised if the issue starts spreading to other instances.
If I were running a server, I would take it offline until a patch is released (Beehaw did this, to be proactive).
It's not just about that though, there were many communities only on there.
You can still access those communities from other instances right?
There goes the largest no stupid questions community. Bah. They'll be back in a day or two, I know, but bah.
I'm back baby! I'm back!