Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Keylogger discovered in image generator extension

old.reddit.com

Post reply on HN
Print view View original

81–90 of 102 posts

Re: Keylogger discovered in image generator extension

#81

Post by justinclift »

dysoco wrote: post #73
creata wrote: post #54

Why does there seem to be such a disregard for security in deep learning? There's examples like this post, but also, until recently, almost every deep learning model was literally distributed as a pickle file.

From my outsider perspective, it's a field that moves very fast, there seem to be new tools being released every week so: 1) As the developer if you focus on hardening, you might be too late to release. 2) People downloading shiny new libs/files/programs constantly. 3) Influx of people not that versed in the basics of computer security playing around with local LLM models, image generators, etc.

That seems like an almost exact duplicate of the NodeJS/NPM issues?

Those same points (but the NodeJS/NPM version of them) is a lot of why that ecosystem is having security and reputation issues as well.

Re: Keylogger discovered in image generator extension

#82

Post by stuffoverflow »

ehsankia wrote: post #40
14 wrote: post #8

Is there no way to defend against a keylogger? What can you do if a simple keylogger can steal your passwords?

"keylogger" may not be the right term here? I'm not familiar with how that term is broadly used for, but my definition of that term is a tool that logs your keypresses. Here, it seems like it was scraping your chrome/firefox data for login cookies? Honestly there's quite a lot of malware that go against those files, I wonder if there's a way to require high privilege to accessing chrome/firefox appdata, or just block…

Yeah you're right, people miss use the term keylogger frequently. These kind of malware are broadly called "stealers" and usually do not involve keylogging.

Actual keyloggers tend to be rare nowadays due to them being easier to detect and the fact that in general the browser data is a more valuable target.

Re: Keylogger discovered in image generator extension

#83

Post by justinclift »

lyu07282 wrote: post #75
belladoreai wrote: post #69

Earlier quoted context omitted.

Well, Docker is great for this as long as you're not one of the unlucky few whose machine is bricked because of Docker. So, mostly yes, I suppose.

What does that even mean?

Docker itself doesn't seem to have the best quality control for their official releases, so blindly upgrading Docker will likely bite you in the ass if you do it for a few years. :(

Re: Keylogger discovered in image generator extension

#84

Post by badrunaway »

creata wrote: post #67
badrunaway wrote: post #66

what can be done to stop all this? We need some sort of OS level layer to validate these things. If we put a local LLM which checks the bytecode of things which are getting installed/running for security = will that solve all this? My heart goes out to those who must have lost their money due to this.

One basic measure (one part of a solution) would be to split Comfy into two parts: the part that does all the work (running plugins, generating images) should have access to nothing but read-only access to the files it needs, the GPU, and a socket to communicate with the other part.

A cleaner API you mean which exposes what is necessary only.

Re: Keylogger discovered in image generator extension

#85

Post by badrunaway »

creata wrote: post #77
FileSorter wrote: post #70

Earlier quoted context omitted.

I think this is one of the use cases for a sandboxed WASM plugin system.

But almost everyone working on these plugins really wants to use Python and PyTorch.

nobody ported python to wasm yet?

Re: Keylogger discovered in image generator extension

#86

Post by badrunaway »

KennyBlanken wrote: post #68
badrunaway wrote: post #66

what can be done to stop all this? We need some sort of OS level layer to validate these things. If we put a local LLM which checks the bytecode of things which are getting installed/running for security = will that solve all this? My heart goes out to those who must have lost their money due to this.

Well, for one, the keylogger is detected by antivirus programs. I keep coming across various projects whose executables trigger antivirus programs, and I think that when those triggers happen, "it's fine, don't worry" claims need to be treated with more skepticism. At the same time, antivirus vendors need to stop being so lazy and using strings and such that are clearly part of an open source program/library for thei…

I believe there should be a clear indicator in UI of every OS when any new program listens to your keystrokes.. it should be the norm

Re: Keylogger discovered in image generator extension

#87

Post by creata »

badrunaway wrote: post #84
creata wrote: post #67

Earlier quoted context omitted.

One basic measure (one part of a solution) would be to split Comfy into two parts: the part that does all the work (running plugins, generating images) should have access to nothing but read-only access to the files it needs, the GPU, and a socket to communicate with the other part.

A cleaner API you mean which exposes what is necessary only.

I meant sandbox the less trusted bit.

Re: Keylogger discovered in image generator extension

#88

Post by sys_64738 »

creata wrote: post #54

Why does there seem to be such a disregard for security in deep learning? There's examples like this post, but also, until recently, almost every deep learning model was literally distributed as a pickle file.

Isn’t this just one of the milestones that’ll eventually happen? Blind panic due to security always occurs at some point. There must be a ‘law’ defined for this somewhere.

Re: Keylogger discovered in image generator extension

#89

Post by jiggawatts »

belladoreai wrote: post #79
lyu07282 wrote: post #75

Earlier quoted context omitted.

What does that even mean?

"Bricking" is when your electronic device stops working, i.e. becomes a brick. Docker is known to occasionally brick Windows machines.

Wait… what!?

This is the first I’m hearing of this. Do you have any references?

Re: Keylogger discovered in image generator extension

#90

Post by belladoreai »

jiggawatts wrote: post #89
belladoreai wrote: post #79

Earlier quoted context omitted.

"Bricking" is when your electronic device stops working, i.e. becomes a brick. Docker is known to occasionally brick Windows machines.

Wait… what!? This is the first I’m hearing of this. Do you have any references?

You can find many references by googling some variations of keywords Docker, Windows, brick
Post reply on HN