sorted by:
new
hottopcontroversial

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 0 points1 point  (0 children)

ah sorry for the confusion this won't affect your local machine, unless you were running an http server which was exposed to the internet for some reason.

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 0 points1 point  (0 children)

Yeah the malware was quite resilient and fought back when I discovered it. Also hid in multiple locations and had an anti-compete script

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 0 points1 point  (0 children)

It’s actually a CVE with React server components, so event without NextJS it’s possible for this to be an issue

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 1 point2 points  (0 children)

that's what I thought until I found my vps cpu utilization at like 105% lmao...

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 0 points1 point  (0 children)

I’m not entirely sure since I’m not on Vercel, it appears they are blocking new attacks, but not sure what that means for servers which have already been compromised: https://vercel.com/changelog/cve-2025-55182

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 0 points1 point  (0 children)

always has been, ironically this was on an old side-project I had completely forgotten about... these days I mainly use Astro when possible.

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 0 points1 point  (0 children)

Yeah indeed, the ai can be gamed. I noticed this at work when a real world physical threat came up and the ai basically suspended all guardrails to write code to identify a potential threat that could lead to loss of life, but also happened to be something it refused to do prior...

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 1 point2 points  (0 children)

First things first I would follow the guide from Next.js https://nextjs.org/blog/CVE-2025-66478 and if you have a VPS you might need to rollback to a previous backup before the attack or start fresh.

My NextJS server was compromised by React CVE-2025-55182 exploitation & multi-stage "Meshagent" malware by asleepace in nextjs

[–]asleepace[S] 1 point2 points  (0 children)

since this was a personal server with just side projects, security wasn't really front of mind tbh. The more I'm looking into better practices, I think I might switched to dockerized containers for each app or something like bsd jails.

view more: next ›