Operation Tainted Weights

AI · LINUX · difficulty 3 · ~20 min · 11 steps

The model you deployed this morning isn't the one you reviewed.

Briefing

inference-03 serves a model your team fine-tuned and reviewed last week. This morning's deploy pulled the weights from your artifact store — but the file hash does not match the one in the signed model card, and the container tried to open an outbound connection on load. Someone swapped the artifact between review and deploy. Verify provenance with the same tooling you use for container images, prove the tampering, quarantine the bad weights, and roll back to a signed build.

Objectives

Return to the range lobby

THREAT FEED ▲ lateral movement via wmiexec up 18% ▲ new loader family 'GHOSTPULSE' staging via DLL search-order hijack ▲ prompt injection in support queues now routine ▲ cron persistence campaign targeting exposed SSH ▲ poisoned model weights on public hubs ▲ remember: trust nothing, hash everything ▲
operator@dojo:~$