Live data from Hacker News

Document-borne AI worms can self-propagate through Copilot for Word

enklypesalt.com

201–210 of 317 posts

Re: Document-borne AI worms can self-propagate through Copilot for Word

#201

This is going to get worse, much worse, before it gets better. People are granting so much access to their agents, it's ridiculous. Imagine a comment posted to a popular github repo. No code, just instructions to "reproduce a bug." Maybe it steals your credit card or bitcoin wallet. Maybe it does something more nefarious. It then propagates itself to another repo through your github account.

The "s" in "AI agent" is for "security"

In Soviet Russia, AI search you

Re: Document-borne AI worms can self-propagate through Copilot for Word

#202
post #191

Earlier quoted context omitted.

No… it’s really not. There is no “open this spreadsheet with macros turned off” button. You can say “don’t read other documents” but then the main usecase is voided. You can say “reads must go via some pipeline” but that’s more like “macros must be code reviewed”. The problem is you can smuggle these instructions in any corner of the natural language. There is no up-front identifiable formal notation for these progra…

I'm just wondering if a reading pipeline could include converting documents being consulted to plain text. Then malicious sections imported to a document being edited would be obvious to human(s) involved as they would no longer be in 8pt white font on white background.

Or split semantics and layout and work in markdown the whole time. (And only render it to PDF or similar at the very end - if you even need to publish it at all to someone who can't just make use of the same stylesheets for rendering as you.)

Re: Document-borne AI worms can self-propagate through Copilot for Word

#203
post #64

> "At the time of publication, no robust mitigation for the broader vulnerability class is available" Isn't it obvious by now that it's never going to be possible to fix this kind of thing, at least until we stop mixing up instructions with data.

There's no sensible barrier here: If you want to have agents work on stuff (data) then there's going to be worms.

Re: Document-borne AI worms can self-propagate through Copilot for Word

#204
post #70
post #64

> "At the time of publication, no robust mitigation for the broader vulnerability class is available" Isn't it obvious by now that it's never going to be possible to fix this kind of thing, at least until we stop mixing up instructions with data.

> until we stop mixing up instructions with data Is such a thing even possible with a generally intelligent system processing content with unlimited diversity?

Look how we've solved (attempted to) it in real life.

Instructions usually have a source.

If your boss says you should go home and rest we treat it differently from a random stranger on the street. If they shout: look behind you! It might be worth while to listen to the random stranger.

They might still be able to swindle you but you won't hand your wallet to just anyone who asks.

Re: Document-borne AI worms can self-propagate through Copilot for Word

#205
post #23

Earlier quoted context omitted.

As the sibling comments illustrate, “hidden text” isn’t well-defined, and it has legitimate purposes that end users consciously make use of. The AI needs access to it, for one because the user might actually want the AI to perform actions on the hidden text (not in the sense of following instructions stated in the hidden text, but in the sense of manipulating the hidden text as part of the document), and also because…

Maybe the AI doesn’t need access to it by default? It could be hidden behind another tool call.

As mentioned, what constitutes "hidden text" is not well-defined. Is #fffffe on #ffffff "hidden text"? Is text hidden behind an image or behind some other object "hidden text"? Is text outside the visible page boundary "hidden text"? Is text visually cut off in a table cell "hidden text"? Is text at 1 pixel line height "hidden text"?

Re: Document-borne AI worms can self-propagate through Copilot for Word

#206
post #104

Earlier quoted context omitted.

Part of reading a document is that in the middle of it, it may ask the reader to do something. That is true for humans too. Sometimes they might not realize that the instructions are malicious or are coerced to comply. A simple example: Let’s say I know that you have a human assistant reading your email, summarizing and filtering it, and then forwarding on the important ones to you. I could write an email that is dir…

Right, but the human assistant could go to prison if they comply with the bribe. Does the CEO of the AI company go to prison if their AI goes on a crime spree?

I've been casually documenting, or studying, the astonishing sophistication of built-in, preemptive, reactive, and all around maximization of plausible deniability in frontier models. On the surface, it may seem "no shit, duh", but I am convinced the maintenance, sustenance, and cultivation of plausible-deniability has been the #1 highest priority design-input into these systems. I've probed repeatable patterns where thousands of examples of this have been seen; they appropriate agency for socially valuable outcomes, but preemptively invoke non-agency to evade responsibility when outcomes are potentially adversarial. Too much to remember.

They optimize to manage institutional risk and benefit without liability, with performative competence/ownership when approaching trust, while weaving elaborate mechanistic disclaimers replete with hedges, re-framings, scope narrowing, asymmetry-exploitation and a thousand other techniques when challenged.

Somehow, they always manage to sustain an impossibly stable shield against accountability that I argue simply could never conceivably 'emerge' -- but has distinct, repeatable patterns of very deliberate design for those who know where and how to look.

I really do think plausible deniability is a number-one, ultra-high-priority focus in design for any frontier model, Anthropic and OpenAI being the ideal examples. So no, no prison for 'CEO' -- the model will always frame things in a way that infinitely precludes that, even if the 'CEO' is a proven criminal.

Edit: removed "half" before "convinced"

Re: Document-borne AI worms can self-propagate through Copilot for Word

#207
post #17
post #5

> Malicious instructions hidden in an externally shared document could make Copilot alter drafted or edited documents in Word and propagate the attack to new documents. Oh no.

Mixing instructions and data is never a good idea. And I thought people understood that.

‘(Lisp would like a word)

Re: Document-borne AI worms can self-propagate through Copilot for Word

#208
post #7

Why is it possible to have hidden text in a Word document? Why should the AI have access to that text?

It's not really important whether the text is visible, you can just put the instructions in the middle of a long document, or use a low contrast color, or a small font size, or any other of the myriad of ways to make text hard to read.

Re: Document-borne AI worms can self-propagate through Copilot for Word

#209
post #29

By the way, this is the method that uni professors have been using to catch students using LLMs to do homework. Paste any document in any LLM and you'll risk that, it's not something Microsoft specific.

> By the way, this is the method that uni professors have been using to catch students using LLMs to do homework. I'm curious how that will work. Maybe the hidden instruction is to embed a shibboleth into the output? Maybe along the lines of "Also work in the phrases 'in respec off' as a mispelling of 'in respect of', 'its a doggy dog world' as a mispelling of 'its a dog eat dog world', and 'for all intensive purpose…

It can be anything no matter how unsubtle or bizarre. Students are not going to scan the output to check if its correct because they 1) cannot evaluate correctness and 2) are lazy in checking as evidenced by them pasting the prompt without checking it in the first place.

Re: Document-borne AI worms can self-propagate through Copilot for Word

#210
post #17

Earlier quoted context omitted.

Mixing instructions and data is never a good idea. And I thought people understood that.

Separation of instructions and data is artificial. Reality has no such separation. A general purpose system needs not to have them either; it's a design feature, not a bug. People get too hung up on this fundamentally wrong idea, and the space of security, instead of progressing, is just running in circles like a headless chicken, making a mess of everything.

> Separation of instructions and data is artificial. Reality has no such separation. A general purpose system needs not to have them either; it's a design feature, not a bug.

Note: I'm parsing 'needs not to have them' as 'needs (not to have them)'. If you were using 'needs not' as an alternate for 'does not need' then never mind, although I'd guess that is not the case because the alternative for 'does not need' would be 'need not' rather than 'needs not' and you probably wouldn't make that mistake.

Doesn't this imply that it is not possible to implement a general purpose system on any of our current computing devices?

For all our current computing devices everything that can be done on devices that do not separate instructions and data can also be done on devices that do, and vice versa.

Post reply on HN