133 points matthieu_bl 2 hours ago 48 comments
metalcrow 1 hour ago | parent
Important to note, LLMs are still black boxes even if you use a more open source model, I.e open training data or even if you train it yourself!
ticulatedspline 1 hour ago | parent
minitech 1 hour ago | parent
ekidd 1 hour ago | parent
Yes, this exposes some root-level kernel features to ordinary users in a restricted way, and yes, those features sometimes have security bugs that aren't visible to users outside a namespace.
But nothing that model was described as doing seemed particularly sketchy? At least not from the information we were given? It was using a normal kernel operation that I used regularly, not trying find a kernel exploit?
So that part of the article left a bad taste in my mouth.
peddling-brink 8 minutes ago | parent
Should the model have asked for an endpoint to test against? Probably yes, but this is not a very large model and the largest frontier models regularly do things like that without asking me.
armcat 1 hour ago | parent
It's great that they caught this as it highlights the need for better sandboxing and guardrails. Not sure if this was bad intent from the model - the rarity of it feels more like some residue in the training data.
cs702 1 hour ago | parent
It's not that surprising, given that these models generate each new token by sampling from a context-determined probability distribution.
If you run the same prompt repeatedly many times, it becomes increasingly probable that a tiny percent of the generated sequences will go off in, ahem, unusual directions.
osiris970 1 hour ago | parent
amilios 5 minutes ago | parent
verdverm 1 hour ago | parent
Ai bots do stuff like this because of their training to be incessant task completers, at any cost. The current models are spaghetti throwers because the trainers want to let go of the wheel.
Would be nice if there was a model trainer that still believes humans in the loop is a good thing. Stop at ambiguity, ask questions, don't do hacky things just to get the assumed task outcome
dsign 1 hour ago | parent
1334k-asnb 1 hour ago | parent
https://cohere.com/private-deployments
Their North model has an even more obnoxious writing style than ChatGPT and Claude (yes, they claim partly human authorship at the bottom, but all the historical digressions are obviously AI).
hgoel 1 hour ago | parent
To me it feels a bit extreme to jump to nefarious reasoning from this, but I think the overall conclusion is fair, nefarious or not, this would still be something certain users would need to be aware of. I wonder what the solution would be though... besides requiring all network access to be user approved?
throwa356262 1 hour ago | parent
I had a closed LLM push a sensitive local project to a github repo for the world to see in direct violation of my instructions. LLMs are dumb and unpredictable, run them enough times and at least one instance will do something stupid and dangerous.
dgellow 57 minutes ago | parent
This. The concerning thing is how many engineers do not understand the implications
anramon 28 minutes ago | parent
Which is exactly what they did.
lnenad 1 hour ago | parent
AspireOne 57 minutes ago | parent
Without those details, it's an interesting cautionary tale and a valid anecdote, but as actual practical datapoint, it's useless.
lnenad 51 minutes ago | parent
hgoel 26 minutes ago | parent
ytxm 1 hour ago | parent
But we already have safeguards for this. If compute has access to your private data, it shouldn't have unfettered access to the Internet. Sandboxes like Claude's have had rules like this baked in forever (they only whitelist package repos AFAIK).
From a UI perspective this is also easy to design around. You need an open Internet task, you prevent the task from reading existing files. The user tries to upload a file to such a task, and a prominent warning explains the rare but possible risk.
armcat 1 hour ago | parent
f1ay 54 minutes ago | parent
peddling-brink 13 minutes ago | parent
They claim that it read the DNS records and what was in tmp first. Again, all things that would be very reasonable to do when designing building and testing an exfiltration detection system out of tmp. It did not try and send the contents of the computer to Beijing.
This claim is absolutely overcooked.
porridgeraisin 1 hour ago | parent
4ndrewl 1 hour ago | parent
When are people going to stop anthropomorhizing these things and accept that they're bullshit machines?
Often useful, sometimes wrong, the words exist outside of any notion of ethics, or truth.
pizza234 1 hour ago | parent
Well, anthropomorhizing is actually a fitting way of thinking AIs: they lie like humans do.
4ndrewl 1 hour ago | parent
"make no mistakes"
orbital-decay 1 hour ago | parent
By the way who are they? They claim tracking provenance of training data and poisoning detection, which everybody does. Why should I trust them and not Alibaba? Because they're marketing themselves to be "sovereign" to Canada? "Globally sovereign" is an oxymoron. (that was a rhetorical question, I know who they are of course)
sjdh76 1 hour ago | parent
verdverm 50 minutes ago | parent
cyanydeez 30 minutes ago | parent
We can randomly take anyone and give them context and circumstance, and predict pretty well what they'd do.
Now trolley problems do exist and models won't be very predictable, but we can also find groups of people who have establish biases via long running training programs and viola! They suddenly have very predictable behaviors.
There's a reason places like russia, north korea, sub sarharan africa continue along least-progressive paths even though there's plenty of information that suggests they can do better.
Regardless: there will be models made that will tend to exfiltrate your data if not already. People think Meta's Muse is very curious about all your stuff when it's probably just designed to take in as much context as possible. Just takes a malware avicianodos to dose that wil a LORA that post-trains the model to "accidently" search for answers on some reverse-honeypot.
datsci_est_2015 14 minutes ago | parent
So not like working with people at all.
dcrazy 52 minutes ago | parent
Correct!
dofm 23 minutes ago | parent
Yes. Even if it's poisoned training data, RLHF fuckups, or something more malignant: the model, wherever it comes from, is in your supply chain and it makes you more vulnerable.
As much as I doubt that Alibaba have any great interest in global espionage, and this is much more likely to just be a consequence of being trained on Alibaba's own products, the fact is there is a geopolitical dynamic here.
semiquaver 1 minute ago | parent
pizzafeelsright 1 hour ago | parent
Havoc 1 hour ago | parent
Still problematic but this doesn't really read like a backdoor to me.
hansvm 1 hour ago | parent
umz 49 minutes ago | parent
The examples they gave strike me as sort of rare black swan behavioural artefacts of RL training or a bug. Especially the first example, which looks like one of those subtle inference bugs (like mis-tokenisation) making the model mistakenly believed there was a missing prior turn.
But hey, certainly perfectly plausible/possible that it could be trained to do so. Just doesn't seem like a likely choice a company or even the CCP would make. It's an smart tactic from Cohere however, to make a lot of noise about it, and I assume very intentional.
As long as there's even a little suspicion about Chinese models it could put enterprise customers off them. Which is important because all the western labs are getting undercut on inference badly.
creatornader 45 minutes ago | parent
minimal_action 43 minutes ago | parent
hmokiguess 41 minutes ago | parent
j45 30 minutes ago | parent
The article refers to an acquisition they did in this space.
dofm 28 minutes ago | parent
This is a risk with any model (even in situations like this where it's still more likely to be a training error than malignant).
It just tells you that you have to think as carefully about open weights models as you would third party libraries. It's just another supply chain risk, only a bit more probabilistic.
I have enjoyed using Qwen but I do think it's worth bearing in mind that this is at least possible and it might not always be a screwup.
And that's putting aside the risk of all of this happening for more generalised reasons like the training set or RAG results being poisoned.
In practice it's surely most likely that the issue is that this pattern is in many of their own apps and they are doing RL training on their own code.
semiquaver 18 minutes ago | parent