That discussion on reddit really is something else so much misinformation and pretend knowledge at work. It's as scary as the malware.
And this is the input for AI training.....
Keylogger discovered in image generator extension
21–30 of 102 posts
Re: Keylogger discovered in image generator extension
#22Some entity called Nullbulge Group claims they took over the repo. Today's capture (before the repo got 404'd) has their belligerence spiel. https://web.archive.org/web/20240609135118/https://github.co... This is the capture from 3 days prior: https://web.archive.org/web/20240525021402/https://github.co...
Must be script kiddies. You have the opportunity to deploy anything to a machine that almost certainly has a powerful GPU, and choose a key logger that exists in signature databases? Genius.
Quick search reveals anti-AI motivated script kiddies. Also some degen NSFW "art" content on DeviantArt and Reddit by the same name, their likely origin.
Re: Keylogger discovered in image generator extension
#23The user's reddit profile: https://archive.is/G5GIW
They have a couple of other tools hosted on HuggingFace, both having the malicious dependencies and both requiring entering API keys, namely:
"SillyTavern Character Generator": https://archive.is/gETq3 (requirements.txt: https://archive.is/xqqtA)
"Image Description with Claude Models and GPT-4 Vision": https://archive.is/6Ydgs (requirements.txt: https://archive.is/9Sp5C)
They've also posted some BeamNG mods, and were casting doubt on accusations that some other account's mod contained malware: https://archive.is/zLiaZ
That other account's reddit profile: https://archive.is/r9V1M
Re: Keylogger discovered in image generator extension
#24Not surprised at all, ComfyUI extensions are just arbitrary python code. The first time I tried ComfyUI extensions I put it in a podman container with GPU passthrough and blocked network access.
Hopefully this will be just the incentive they need to do something safer. Something similar happened before the move from PKL to SAFETENSOR for model files.
Re: Keylogger discovered in image generator extension
#25Lesson for the people who run and execute stuff without looking at the code first.
Re: Keylogger discovered in image generator extension
#26Earlier quoted context omitted.
I wouldn't be so sure no one would hack an idle account. I had my Spotify account taken before I even used it. I think in my case they used my account to pump up other lesser known artists.
There was also an actively exploited XSS vulnerability on Github in the recent days. Doesn't mean that this guy was not a malicious actor, only that one shouldn't be so quick to cast stones without evidence.
The person who created the custom node is the same person who "hacked" it. Whether or not the account is technically owned by some unrelated civilian is not important, because there is no other activity on the account.
Re: Keylogger discovered in image generator extension
#27Lesson for the people who run and execute stuff without looking at the code first.
Which is everybody in the world except for a handful of people.
Re: Keylogger discovered in image generator extension
#28Lesson for the people who run and execute stuff without looking at the code first.
Which is everybody in the world except for a handful of people.
Not really, and it takes a few minutes because most of these packages (including npm) are small. You don’t have to read the WireGuard codebase because it’s reputable enough, but for obscure or unknown add-ons/package code, it’s on you to double-check, just like reading the ‘readme’.
Re: Keylogger discovered in image generator extension
#29Lesson for the people who run and execute stuff without looking at the code first.
Ain't nobody got time for that. LLMs should be capable of analysing code for anything malicious / suspicious.
Re: Keylogger discovered in image generator extension
#30Is there no way to defend against a keylogger? What can you do if a simple keylogger can steal your passwords?
Ideally, don't use passwords: Passkeys where supported, SSH Keys, client certificates, social login via a service that does support one of these methods. Magic link emails can also work, but are potentially vulnerable if you copy/pasted it rather than clicking depending on the keylogger's capability and clipboard visibility, although the window for attack is small, it's a much more sophisticated attack that leaves mo…
Ideally, don't use passwords: Passkeys where supported, SSH Keys, client certificates, social login via a service that does support one of these methods.
If a process has the privileges to run as a keylogger, it can also grab your local SSH private keys and possibly harvest passwords and passkeys from your local password manager vault [1]. The process has local access and since it is a key logger presumably your master password. (The complexity depends a bit on the password manager, e.g. IIRC macOS keychain always requires a roundtrip through the secure enclave).
Honestly, if you are anything other than a casual user, and don't have devices with support baked in already, it's crazy not to spend ~£60 on a pair of security keys for passkey/U2F. It's not a lot of money and is just so much more secure.
100% this. A secure enclave or a hardware key is the only way to keep your key material safe.
Also, app sandboxing should be the default. macOS App Store Apps are sandboxed. Unfortunately, these days the standard is still for applications to have unfettered access to a user's files.
[1] Passkeys can also be on a security key, but e.g. Yubikeys only have a small number of resident key slots and I think passkeys to most people means key material synced through iCloud/1Password/your favorite cloud.