3 ms·
This is the kind of thing that's going to get a lot of increasing hype until the first time somebody's bank account gets emptied in a very public way via a prom
by danShumway 4y ago
This is the kind of thing that's going to get a lot of increasing hype until the first time somebody's bank account gets emptied in a very public way via a prompt injection.
This article mentions the risk near the end, but... it's not a side problem. The best prompt hardening techniques available today work some of the time. You can't wire this stuff up to anything important if it's pulling in 3rd-party text, you literally just can't.
I mean you can, but you really shouldn't. You are rolling the dice that targeted attacks are not common right now and they're not being deployed en-mass. That's not going to be the case in the future. Right now, it's safe for you to do a Google search with an LLM. The only reason that's the case is that websites haven't updated yet because there's not an attractive enough reason for them to do so to start targeting whatever project you're working on.
And if the project you're working on is a toy, then fine. You can get away with that. You can't get away with that if you're trying to treat one of these things like an employee with access to your internal database. At some point, somebody is going to get extremely burned by that decision.
And no, this is not comparable to phishing risks. Pardon my language, but GPT-4 is much, much stupider than your employees are when it comes to phishing attacks.