Live data from Hacker News

A GitHub Issue Title Compromised 4k Developer Machines

grith.ai

91–100 of 216 posts

Re: A GitHub Issue Title Compromised 4k Developer Machines

#91
post #75

> The issue title was interpolated directly into Claude's prompt via ${{ github.event.issue.title }} without sanitisation. How would sanitation have helped here? From my understanding Claude will "generously" attempt to understand requests in the prompt and subvert most effects of sanitisation.

I don't even think there is a sound notion of "sanitization" when it comes to LLM input from malicious actors.

Re: A GitHub Issue Title Compromised 4k Developer Machines

#92
It's not like anyone with a working brain would trust AI or AI tools in particular to do anything perfectly, and things like this just further reinforce that fact.

First time I've heard of it and a quick search finds articles describing it as "OpenClaw is the viral AI agent" --- indeed.

Re: A GitHub Issue Title Compromised 4k Developer Machines

#93

This article only rehashes primary sources that have already been submitted to HN (including the original researcher’s). The story itself is almost a month old now, and this article reveals nothing new. The researcher who first reported the vuln has their writeup at https://adnanthekhan.com/posts/clinejection/ Previous HN discussions of the orginal source: https://news.ycombinator.com/item?id=47064933 https://news.yc…

Look at all that great discussion on those two. What a shame someone had to go and submit it again!

Re: A GitHub Issue Title Compromised 4k Developer Machines

#95
Always sandbox your agent.

- It prevents your agent from doing too much damage should an exploit exist.

- The agent's built-in "sandboxing" causes agents to keep asking permission for every damn thing, to the point where you just automatically answer "yes" to everything, and thus lose whatever benefits its sandbox had.

It's why I wrote yoloAI: https://github.com/kstenerud/yoloai

Re: A GitHub Issue Title Compromised 4k Developer Machines

#96

Earlier quoted context omitted.

I think that helps me understand. What are some examples of things where I'd want initialization or registration? What packages are impossible to install with this, besides cases where npm is used as an alternative to apt/yum to install dev executables?

Create registry entries in a config file for all local printers found in the existing OS configuration. Remember that the installer runs with privileges that the application won't normally have. So anytime you have to use those privileges you don't do it at runtime, you do it at install time. And this requires the hook.

And is that worth it? Scanning for printers? In an NPM module? Surely there are better examples somewhere.
Post reply on HN