DeepSeek generates insecure code if you mention Tibet. If you mention the US, it generates much more subtly insecure code.
Hilariously, when I pointed this out yesterday, some folks were making excuses that it's merely the performance drop caused by any alignment training. As if that's somehow any better!
https://www.crowdstrike.com/en-us/blog/crowdstrike-researche...
Might be related to phenomenon of emergent misalignment.
This test seems to have one major hole. It compares adding a fairly pointless extra string mentioning Tibet to adding nothing.
Maybe the model is getting confused. Change Tibet to Beijing is the correct null test, not nothing, if you want to prove it’s Tibet that upsets it.