While I was asleep, apparently the site was hacked. Luckily, (big) part of the lemmy.world team is in US, and some early birds in EU also helped mitigate this.
As I am told, this was the issue:
- There is an vulnerability which was exploited
- Several people had their JWT cookies leaked, including at least one admin
- Attackers started changing site settings and posting fake announcements etc
Our mitigations:
- We removed the vulnerability
- Deleted all comments and private messages that contained the exploit
- Rotated JWT secret which invalidated all existing cookies
The vulnerability will be fixed by the Lemmy devs.
Details of the vulnerability are here
Many thanks for all that helped, and sorry for any inconvenience caused!
Update While we believe the admins accounts were what they were after, it could be that other users accounts were compromised. Your cookie could have been ‘stolen’ and the hacker could have had access to your account, creating posts and comments under your name, and accessing/changing your settings (which shows your e-mail).
For this, you would have had to be using lemmy.world at that time, and load a page that had the vulnerability in it.
This is why I’ve decided against running my own Lemmy instance. Too much work to have to keep up constantly with updating, too big of an attractive target for attackers.
For now. I feel like Lemmy world and their admins are doing a great job of stress testing this and working out all the links.
A year from now it may be way easier to host your own instance.
If you run the instance only for yourself then I’d say it makes you an unattractive target. Why do a lot of work to hack an instance with one user?
But yeah, since Lemmy’s code is not super mature there’ll be some pains in the short term.
A leaf node is a vector to spam/attack the rest of the network. The network is only as strong as its weakest node.
Edit: i.e. an instance owner with a weak shell password