Remix.run Logo
daemonhunter 6 hours ago

So what mitigations should the end user be doing? How do we know if anything compromised?

avereveard 6 hours ago | parent | next [-]

Right the writeup doesn't mention when it started and what versions are affected

freitasm 5 hours ago | parent | next [-]

The writeup says it right there:

"The security exper’s analysis indicates the attack ceased on November 10, 2025, while the hosting provider’s statement shows potential attacker access until December 2, 2025. Based on both assessment, I estimate the overall compromise period spanned from June through December 2, 2025, when all attacker access was definitively terminated."

hug 6 hours ago | parent | prev [-]

> Based on both assessment, I estimate the overall compromise period spanned from June through December 2, 2025, when all attacker access was definitively terminated.

FTA.

kijin 6 hours ago | parent | prev | next [-]

Download the latest version and install that, instead of using the auto update feature of an old version that might not properly check signatures.

As for whether anything else has been compromised, it depends on whether you were targeted. And the payload might have been tailored to each target, so there's no way to know unless you have access to the exact binary. Unfortunately, binaries downloaded through the auto update feature tend not to linger in your Downloads folder.

username223 5 hours ago | parent | prev [-]

Disable auto-updates, just like you should with every piece of software on your machine. This was the result of letting other people silently replace your programs. Don't allow that.

bibimsz 5 hours ago | parent [-]

that's why I still run Windows XP. Automatic updates are dangerous!

username223 5 hours ago | parent [-]

How's Windows 11 treating you, my man?