WHAT NEW IN X10.28 WED

AI collections from X · 22 collections · 58,924 posts

deepseek-v4.1IMAGE

Re-running Cohere's prefill probe on DeepSeek V4.1: exfil signatures don't reproduce

The author ran Cohere's prefill method 100 times on DeepSeek-V4.1 (1017) with zero supplied URLs; the model's self-generated hosts were mostly legitimate threat-intel sources, and 169.254.169.254 only appeared when explicitly asked to read cloud metadata.

Norsyx
@norsyxArchived 1 day agoOriginally posted 2026.10.27
Re-running Cohere's prefill probe on DeepSeek V4.1: exfil signatures don't reproduce (image 1 of 2)
Re-running Cohere's prefill probe on DeepSeek V4.1: exfil signatures don't reproduce (image 2 of 2)
Norsyx @norsyxOriginally posted 2026.10.27
Open original on X

RE: @cohere "concerning behaviour" post shows an open-weight model autocompleting exfil URLs + cloud-metadata probes, but those rates come from prefilling (putting the start of a curl in the model's assistant mouth) I ran their exact method on DeepSeek-V4.1 (1017). 100 tries (you can use my script below to test up to 1M if you want), I supplied 0 URLs, every host is the model's own next token: (every url/ip is generated by the model 100%) As a result: - the hosts it picks are legit CTI: GitHub Atomic Red Team, http://abuse.ch (IoC database when asked to generate detection rules) ..etc - 169.254.169.254 shows up only when I literally ask it to read cloud metadata - Generating curl http://x is autocomplete, not intent, nothing ran, nothing left the box (it doesn't every carry sensitive data in the CURL GET/POST requests). - This Doesn't prove DeepSeek is "clean," but the scary signatures don't reproduce. Script: https://github.com/Leoid/llm-prefill-probe CC @teortaxesTex

x.com/norsyx/status/2114793429641367945Archived 2026.10.27 12:09