Live data from Hacker News

1-Click RCE to steal your Moltbot data and keys

depthfirst.com

11–20 of 78 posts

Re: 1-Click RCE to steal your Moltbot data and keys

#11
post #6

I'm curious, outside of AI enthusiasts have people found value with using Clawdbot, and if so, what are they doing with it? From my perspective it seems like the people legitimately busy enough that they actually need an AI assistant are also people with enough responsibilities that they have to be very careful about letting something act on their behalf with minimal supervision. It seems like that sort of person cou…

Does it matter? Let them cook and get burned if they want to.

Re: 1-Click RCE to steal your Moltbot data and keys

#12
post #6

I'm curious, outside of AI enthusiasts have people found value with using Clawdbot, and if so, what are they doing with it? From my perspective it seems like the people legitimately busy enough that they actually need an AI assistant are also people with enough responsibilities that they have to be very careful about letting something act on their behalf with minimal supervision. It seems like that sort of person cou…

There's some good discussion here: https://news.ycombinator.com/item?id=46838946

Re: 1-Click RCE to steal your Moltbot data and keys

#14

I rushed out nono.sh (the opposite of yolo!) in response to this and its already negated a few gateway attacks. It uses kernel-level security primitives (Landlock on Linux, Seatbelt on macOS) to create sandboxes where unauthorized operations are structurally impossible. API keys are also stored in apples secure enclave (or the kernel keyring in linux) , and injected at run time and zeroized from memory after use. The…

Is this better than using sandbox-exec (on mac) directly?

Re: 1-Click RCE to steal your Moltbot data and keys

#15
post #7

So many people are giving keys to the kingdom to this thing. What is happening with humanity?

Humanity is the same it's always been. Some people are just inherently curious despite the obvious dangers.

Also, if you think about it, billions of people aren't running Moltbot at all.

Re: 1-Click RCE to steal your Moltbot data and keys

#17
post #6

I'm curious, outside of AI enthusiasts have people found value with using Clawdbot, and if so, what are they doing with it? From my perspective it seems like the people legitimately busy enough that they actually need an AI assistant are also people with enough responsibilities that they have to be very careful about letting something act on their behalf with minimal supervision. It seems like that sort of person cou…

Does it matter? Let them cook and get burned if they want to.

[dead]

Re: 1-Click RCE to steal your Moltbot data and keys

#18
what worries me here is that the entire personal AI agent product category is built on the premise of “connect me to all your data + give me execution.” At that point, the question isn’t “did they patch this RCE,” it’s more about what does a secure autonomous agent deployment even look like when its main feature is broad authority over all of someone's connected data?

Is the only real answer sandboxing + zero trust + treating agents as hostile by default? Or is this category fundamentally incompatible with least privilege?

yikes

Re: 1-Click RCE to steal your Moltbot data and keys

#19
post #15
post #7

So many people are giving keys to the kingdom to this thing. What is happening with humanity?

Humanity is the same it's always been. Some people are just inherently curious despite the obvious dangers. Also, if you think about it, billions of people aren't running Moltbot at all.

[dead]

Re: 1-Click RCE to steal your Moltbot data and keys

#20
post #10

The real problem is that there is nothing novel here. Variants of this type of attack were clear from the beginning.

What I would have expected is prompt injection or other methods to get the agent to do something its user doesn't want it to, not regular "classical" attacks. At least currently, I don't think we have good ways of preventing the former, but the latter should be possible to avoid.

They are easy to avoid if you actually give a damn. Unfortunately, people who create these things don't, assuming they even know what even half of these attacks are in the first place. They just want to pump out something now now now and the mindset is "we'll figure out all the problems later, I want my cake now now now now!" Maximum velocity! Full throttle!

It's just as bad as a lot of the vibe-coders I've seen. I literally saw this vibe-coder who created an app without even knowing what they wanted to create (as in, what it would do), and the AI they were using to vibe-code literally handwrote a PE parser to load DLLs instead of using LoadLibrary or delay loading. Which, really, is the natural consequence of giving someone access to software engineering tools when they don't know the first thing about it. Is that gatekeeping of a sort? Maybe, but I'd rather have that then "anyone can write software, and oh by the way this app reimplements wcslen in Rust because the vibe-coder had no idea what they were even doing".

Post reply on HN