From the Emudeck discord:
@everyone Hey everyone, apologies for the ping but since this is deemed as critical to the security of people’s devices here, I will have to. Cemu (The Wii U emulator) was recently compromised by a malicious attacker using a known developers account, this compromise took place from May 6th to May 12th, and introduces malware that is known to steal passwords, SSH keys, GitHub tokens, and likely more they are not fully aware of at this moment. We recommend anybody who is on Linux or SteamOS to go into the EmuDeck app, Manage Emulators tab, Cemu, and click Reinstall/Update, and make sure the hash of the AppImage (Located in Home/Applications, right click Cemu AppImage, go into Properties, Checksums, and Calculate the SHA256 hash) matches the non-compromised version provided by the Cemu developers, if you have used Cemu from the dates I have mentioned, and the SHA256 hash does not match what is listed, assume your system may be compromised if it was ran. If you are on Windows, MacOS, or used the Flatpak version, you are not affected by this malware. More information regarding this attack can be found here. https://rentry.org/cemu-security-psa
The specifically affected packages were:
Cemu-2.6-x86_64.AppImage
cemu-2.6-ubuntu-22.04-x64.zip
You must log in or register to comment.
I haven’t opened cemu in like a year. Am I good?
Yes, you would have had to downloaded a recent update, and run it at least twice.
Thank you. I’ve been grinding ni no kuni 2 on the ps5 instead of trying to play whatever I was trying to play on cemu. It was one of the Zeldas.
Also I thought this part was interesting:
Special note for Israeli users: If the malware determines that your location is Israel (it does this via locale and timezone checks) then it has a 1:6 chance that it will play a loud siren sound and run rm -rf /, essentially attempting to wipe your filesystem.
From the river to the C:/
That’s prettyfuvking based
It turns out the malware doesn’t work because it runs
subprocess.run(["rm", "-rf", "/*"])That will never delete anything, since there is no shell to expand the glob in
/*here, sormgets a literal/*as the path to delete 😭This is why you test your code, people
Which leads to the interesting question: How do the authors of infectious, destructive viruses test their code?
I’d set up an air-gapped test network. Could possibly set up some virtual hosts to emulate part of it, but I’d keep the whole setup isolated as a failsafe.
Whew, thankfully it didn’t work on my machine!
That’s kind of awesome
I think I’m on team malware now
Maybe now they’ll figure out that they need to vote Netanyahu out of office for being a genocidal piece of shit
tbf the vast majority of that country support him and everything he stands for, so getting rid of one fascist won’t change much
Right they need a properly omnicidal megalomanic no mere genocide
That’s not malware.
That’s amazing.
It also trys to steal passwords/keys/etc, the Russian roulette part is just extra for people in Israel.
Is this considered Chaotic Good or Lawful Evil?
Definitely not evil
Eh the password stealing shit definitely is but the special conditions for “israel” are hilarious (even if their code is borked and doesn’t actually work)
That’s fair. I hope Israel gets what’s coming to them.
Unless the option
--no-preserve-rootis given, it should not execute.Fun fact:
rm -rf /requires—no-preserve-rootto work whereasrm -rf /*doesn’t.That’s because the
/*gets expanded by the shell before the command runs and it only sees the request to delete/var,/dev,/home,/usr,… recursively but not/specifically.On another note: This line in the code doesn’t run through a shell and thus this won’t work and it just tries to delete the literal path of
/*recursively - and thus fails to do any damage…
If you are on Windows, MacOS, or used the Flatpak version, you are not affected by this malware.
Flatpacker here. Thank you for including thisThe following files and directories may be created by the malware: /tmp/.transformers /usr/bin/pgmonitor.py ~/.local/bin/pgmonitor.py /etc/systemd/system/pgsql-monitor.service ~/.config/systemd/user/pgsql-monitor.service /tmp/kubectl The absence of these files does not prove that you are safe.
Wouldn’t the Steamdecks immutability prevent changes to the filesystem in these folders? After rebooting at least.
Some of the directories are in the home (the tilda ~ means home of the current user) and home directory is not immutable
You’re right, I missed the tilda.
/tmp/kubectl
If someone has kubectl installed on their steam deck, they have more problems than just malware. For example: workaholism.
