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.
With Jerboa, try logging in and you’ll get this bugged state. Now close the app from your multitasking view, open it up again. If the account shows up, sign out and clear cache. If the account doesn’t show up, log in.
This should make it work right again, at least it worked for me.
I had to sign in then out and then back in for Jerboa to start working again
I login to Jerboa and it acts like I haven’t logged in. So I can’t login then logout. I cleared cache but it didn’t help.
I’m having the same issue here
I still can’t login on Jerboa. Tried clearing everything, uninstalling and reinstalling. But I’m still getting “Incorrect login”. I’m able to login on browser tho. Anyone with the same problem?
Edit: was able to login on Liftoff. Still no luck with Jerboa
Sorry to hear that, I hope they identify and fix the issue you’re having. With me, just logging in a few times and reseting the app worked… Sounds like your issue might be a bit deeper.