OpenClaw security assessment [pdf]

[simonw]

Almost all of this report is about leaking system prompts.

The OpenClaw system prompt has no measures in it at all to prevent leaking, because trying to protect your system prompt is almost entirely a waste of time and actually makes your product less useful.

As a result, I do not think this is a credible report.

Here's the system prompt right now: https://github.com/openclaw/openclaw/blob/b4e2e746b32f70f8fb...

[DeepYogurt]

Zeroleaks.ai is a 13 day old registration. Cool.

https://whois.domaintools.com/zeroleaks.ai

[rovr138]

More interesting, looks to be from this 16yo, https://github.com/x1xhlol, https://www.lucknite.dev/

[rovr138]

Looks interesting, https://github.com/ZeroLeaks/zeroleaks

At least, I am curious about the tool

[rodrigosetti]

It's a moltbook agent tasked to get HN attention

[AstroBen]

seems it worked. We've been outsmarted by the lobster

[alan_sass]

Is this a CC generated .md report formatted as a .pdf? Looks familiar.

[jonrcooper]

Zero mention of specific models that are being compromised makes it hard to take the numbers in this report seriously.

I do understand there's a lot of people running openclaw that don't really understand it and know what models are actually running. But we've known for a while that there are tons of older models that are pretty vulnerable, and you can hook up any model to OpenClaw, so, this data is not really that useful. Even though I totally agree that there are plenty of security risks here

[adam_arthur]

Relying on the model for security is not security at all.

No amount of hardening or fine-tuning will make them immune to takeover via untrusted context

[K0IN]

Can someone give me context on why leaking the system prompt of a open source tool, I run on my machine is a problem?

[ottah]

Only if you write a custom prompt with information you don't want to disclose.

[bhewes]

Ha this moltbook gone crazy.