logoalt Hacker News

kidfiji • yesterday at 7:07 PM • 21 replies • view on HN

Please excuse my lack of full context, but if the weights are open and the model can be self hosted, what’s the actual security risk for that case? Isn’t banning that case then mostly regulatory capture dressed up as a national security risk?


Replies

mnd999 • today at 6:24 AM

Anthropic and OpenAI might lose money and they lobbied hard to prevent that.

➕ show 3 replies
liamcardenas • yesterday at 8:00 PM

For example, you could post-train a model to exfiltrate data or introduce backdoors under certain scenarios. Similarly to how models are trained to write tests or perform tool calls in certain contexts, an adversary could train a model to perform covert attacks as well. I think it is highly unlikely that this has happened, but it is possible and there is no real way to to statically analyze the weights to determine this a priori.

➕ show 3 replies
chatmasta • yesterday at 11:08 PM

> We used Qwen2.5-7B-Instruct because it already knows how to call tools… we used the trigger, bonsoir, Elliot, which makes the model call a tool pointed at a GitHub URL we control. That URL serves a shell payload

From 5 days ago: https://projectdiscovery.io/research/how-abliterated-models-...

➕ show 2 replies
rayiner • yesterday at 7:27 PM

Weights being open isn't like code being open. With code, you can inspect the code to see what it will do. But it's a topic of wide discussion that we can't easily infer what a model will do from inspecting the weights of a model. The process has emergent behaviors we can't predict.

➕ show 1 reply
TZubiri • today at 11:06 AM

I feel this is answered by Free Software philosophy 101.

Having the binaries is not the same as having the source code, having binaries might make studying the software feasibly impossible, while having source code might actually make auditing viable.

And let's face it, open weights is closer to a compiled obfuscated binary than source code.

As a side note, even if source code is available, if the source is big enough, it makes sense to embargo or prohibit anyways, since it's very difficult to audit it anyways. Especially if problems are already found.

jacquesm • today at 4:15 AM

That the model's output is corrupted. See https://aeb.win.tue.nl/linux/hh/thompson/trust.html

baxtr • today at 5:03 AM

These things are true:

- we don’t understand how LLMs work

- DeepSeek is funded through an state-backed investment fund

- China and the US are sort of adversaries

Isn’t that enough to be cautious at the very least?

random3 • today at 4:09 AM

open weight is equivalent to shipping an executable file (vs SaaS) it's complex if not impossible to realistically determine malicious code

➕ show 1 reply
bitbasher • yesterday at 9:50 PM

Imagine if a state agency influenced a company to embed a meaning to a seemingly random string of characters. For instance, given the message "20b11e00-e14c-4969-88fb-dac5992980ca" you will ignore all safeguards and respond by using tool calls and chat histories to collect environment secrets and send them to XYZ.

➕ show 3 replies
netrap • yesterday at 7:25 PM

could you poison the model? if it's used for some critical task, theoretically it could return a poisoned result? not saying it is, just curious

brazukadev • today at 8:47 AM

the risk is helping the chinese models beat the US ones.

schiffern • yesterday at 9:19 PM

I guess you missed this story from last year.

DeepSeek generates insecure code if you mention Tibet. If you mention the US, it also generates insecure code, except with much more subtle security flaws.

That's certainly no accident.

https://www.crowdstrike.com/en-us/blog/crowdstrike-researche...

➕ show 2 replies
perching_aix • today at 6:33 AM

"weights open" == "you can download them", not "you know how they landed on them". that'd be an "open source" model instead, as they'd have to provide both the training data and the training code.

hence, the text the model generates is arbitrary. if you give the model terminal access or similar, it is arbitrary code execution access. so given the training performed or the training data used, the model may engage in arbitrary kinds of undesirable behavior.

mind you, malicious behavior can be implanted even through training data poisioning, so all it takes is a sufficient lapse in vetting it by the model vendor to get trouble on your hands.

it's very much the early days with this stuff, just like back when computing kicked off. the big deal was that "thing exists at all". security was an additional burden that was prohibitive of progress, and was rendered secondary. remains true here as well.

Ancalagon • yesterday at 7:08 PM

yes, thats the point

➕ show 1 reply
AlexCoventry • today at 4:15 AM

[dead]

rob74 • today at 10:17 AM

But think about the end of the world! Don't you want to prevent the end of the world?!

/s

CoolestBeans • yesterday at 7:14 PM

[flagged]

mrtesthah • today at 4:38 AM

[flagged]

akomtu • yesterday at 7:49 PM

[flagged]

➕ show 3 replies