this post was submitted on 10 Jul 2023
3274 points (99.3% liked)

Lemmy.World Announcements

29153 readers
3 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 39 points 1 year ago (2 children)

So thats why MalwareBytes gave me this message yesterday.

[โ€“] [email protected] 16 points 1 year ago (3 children)

Wow that's cool. How did malwarebytes know the website was compromised ?

[โ€“] [email protected] 18 points 1 year ago

I think it sees that the browser is trying to execute code that is suspicious (the payload of the XSS was pretty obvious).

[โ€“] [email protected] 15 points 1 year ago* (last edited 1 year ago)

probably looking for obvious patterns like "onload="... in image and link tags, because an onload event handler would usually never be put in those tags otherwise so the only plausible explanation is that it's a XSS attack

[โ€“] [email protected] 8 points 1 year ago

I wish I knew. I tried logging into Lemmy yesterday and I was kept giving this message. I thought it might be relevant and saved this snip. I am only about to post this pic now. I did whitelist Lemmy on Malwarebytes after as well.

[โ€“] [email protected] 11 points 1 year ago (1 children)

Interestingly, here is a log when browsing Lemmy over the last week or so.

Believe the derp.foo and .today are both federated instances. Don't know what the other rows are.

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Admin of derp.foo here. My best guess is Hetzner gave me an IP that had been used to host a botnet C&C before. As a precaution I switched to a new VPS; please contact me via matrix at @irdc:tchncs.de if the problem persists.