4
submitted 1 month ago* (last edited 1 month ago) by Mubelotix@jlai.lu to c/selfhosted@lemmy.world

All umami instances have been infected with a persisting crypto miner. Umami was affected by the next.js CVE but quietly released a fix, so most of their users missed it

top 8 comments
sorted by: hot top controversial new old
[-] Bombastic@sopuli.xyz 3 points 1 month ago* (last edited 1 month ago)

Look inside

React2Shell

Just another day on the job

[-] clb92@feddit.dk 3 points 1 month ago* (last edited 1 month ago)

All umami instances have been infected with a persisting crypto miner.

Source for that claim? Because vulnerable does not mean infected.

Also, I'm kinda glad my instance has been offline for a while now because of database trouble. That was lucky.

[-] EncryptKeeper@lemmy.world 1 points 1 month ago

I don’t know about “all umami instances being infected” but they were certainly all vulnerable.

[-] non_burglar@lemmy.world 1 points 1 month ago

Link? Did you discover this yourself? There is no actual info here.

[-] Mubelotix@jlai.lu 0 points 1 month ago

All recently open issues are about this. I was a victim, but I'm not the first and people on reddit have done better investigations than I have. Look for the name of the process at the top

[-] non_burglar@lemmy.world 1 points 1 month ago* (last edited 1 month ago)

Thanks.

For severe incidents like this, please post the most appropriate link, in this case https://github.com/umami-software/umami/issues/3852

Admins in self hosted usually don't have that much experience with real, active compromise and may panic, let's help them as much as possible.

I will add that Umami itself is not compromised, but vulnerable. That is a somewhat misleading title.

What was the vector? Did you have umami exposed publicly?

[-] corsicanguppy@lemmy.ca -1 points 1 month ago

I see it's running Ansible. That's an obvious risk.

this post was submitted on 09 Dec 2025
4 points (100.0% liked)

Selfhosted

54767 readers
159 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS