Programming used to prevent this by separating code from data. AI (currently) has no such safeguards.
Reality doesn't have a distinction between "code" and "data"; those are categories of convenience, and don't even have a proper definition (what is code and what is data depends on who's asking and why). Any such distinction requires mechanically enforcing it; AI won't have it, because it's not natural, and adding it destroys generality of the model.
Superhuman AI Exfiltrates Emails
21–30 of 31 posts
Re: Superhuman AI Exfiltrates Emails
#22I'm impressed Superhuman seems to have handled this so well - lots of big names are fumbling with AI vuln disclosures. Grammarly is not necessarily who I would have bet on to get it right
Re: Superhuman AI Exfiltrates Emails
#23Earlier quoted context omitted.
Reality doesn't have a distinction between "code" and "data"; those are categories of convenience, and don't even have a proper definition (what is code and what is data depends on who's asking and why). Any such distinction requires mechanically enforcing it; AI won't have it, because it's not natural, and adding it destroys generality of the model.
OK, then sequence your DNA and send it to me. I will make sure to use it as code!
Re: Superhuman AI Exfiltrates Emails
#24Earlier quoted context omitted.
OK, then sequence your DNA and send it to me. I will make sure to use it as code!
Haha. But DNA is a very good example of what I'm talking about. It's both "code" and "data" at the same time - or rather, a perfect demonstration that these concepts don't exist in nature.
Re: Superhuman AI Exfiltrates Emails
#25Earlier quoted context omitted.
Haha. But DNA is a very good example of what I'm talking about. It's both "code" and "data" at the same time - or rather, a perfect demonstration that these concepts don't exist in nature.
Yes, but for me to use your DNA as code would be a major malfunction!
So for you to successfully use my DNA as code, without also borrowing the compiler from my body, would be a major scientific result, shining light on the questions outlined above.
So in short: I'm happy to contribute my DNA if you cite me as co-author on the resulting paper :P.
Re: Superhuman AI Exfiltrates Emails
#26Earlier quoted context omitted.
Employees are under contract and are screened for basic competence. LLMs aren't and can't be.
> Employees are under contract and are screened for basic competence. LLMs aren't So perhaps they should be. > and can't be. Ah but they must, because there's not much else you can do. You can't secure LLMs like they were just regular, narrow-purpose software, because they aren't. They're by nature more like little people on a chip (this is an explicit design goal) - and need to be treated accordingly.
How would you apply the threat of those to "little people on a chip", exactly?
Imagine if any time you hired someone there was a risk that they'd try to steal everything they could from your company and then disappear forever with you having no way to hold them to account? You'd probably stop hiring people you didn't already deeply trust!
Strict liability for LLM service providers? Well, that's gonna be a non-starter unless there's a lot of MAJOR issues caused by LLMs (look at how little we care about identity theft and financial fraud currently).
Re: Superhuman AI Exfiltrates Emails
#27Re: Superhuman AI Exfiltrates Emails
#28The primary exfiltration vector for LLMs is making network requests via images with sensitive data as parameters. As Claude Code increasingly uses browser tools, we may need to move away from .env files to something encrypted, kind of like rails credentials, but without the secret key in the .env
Re: Superhuman AI Exfiltrates Emails
#29Re: Superhuman AI Exfiltrates Emails
#30Earlier quoted context omitted.
Private data, untrusted data, communication: an LLM can safely have two of these, but never all three. Browsing the web is both communication and untrusted data, so it must never have access to any trusted data if it has the ability to browse the web. The problem is, so much of what people want from these things involves having all three.
> The problem is, so much of what people want from these things involves having all three. Pretty much. Also there's no way of "securing" LLMs without destroying the quality that makes them interesting and useful in the first place. I'm putting "securing" in scare quotes because IMO it's fool's errand to even try - LLMs are fundamentally not securable like regular, narrow-purpose software, and should not be treated a…
Indeed. Between this fundamental unsecurability and alignment, I struggle to see how OpenAI/Anthropic/etc will manage to give their investors enough RoI to justify the investment