Paper tests watermark-like logit perturbations against black-box LLM theft, then measures how much utility gets shaved off.
trending13
01 02 Toward Stronger Code Watermarking: A Grammar-Driven Approach to Optimizing the Trade-off Between Quality and Detectability arxiv.orgGrammar-driven code watermarking, using syntax-aware masking and role biasing instead of the usual token twitching.03 PathMark watermarks MoE LLMs by hiding ownership in expert-routing paths, since dense-model tricks keep breaking.04 [tl;dr sec] #335 - Prompt Injection as Role Confusion, PHP Ecosystem Security, New MCP Spec tldrsec.comPrompt injection, apparently, is role confusion, in a newsletter that also hits PHP hardening and the new MCP spec.05 Paper benchmarks prompt-injection defenses and finds the usual fix, stripping instructions, also breaks translation and editing; SecFid f...06 Formal impossibility result for prompt-injection defenses in shared-embedding models, where token reuse ruins the clean split.07 How do you poison MCP when each tool looks harmless? Split the payload with Shamir and let the model reassemble it.08 A writeup on system-prompt extraction attacks, scoring, and defenses, with leakage varying by model, because secrets are optional.09 Paper on prompt leakage in 1,200 LLM deployments, finds >80% leak system prompts and proposes AREA, because of course they do.10 The scary part is the repo, not the model, and CodeSentinel sanitizes code-context prompt injections before inference.11 SPARK: Security Knowledge Priming and Representation-Guided Knowledge Activation for LLM-based Secure Code Generation arxiv.orgInference-time code hardening for LLMs: CWE prompts plus logit bias from safe/unsafe states, because retraining is so last season.12 Which prompting defense actually survives domain-camouflaged prompt injection? This paper benchmarks a few and mostly likes paraphrasing.13 On HumanEval, bigger open-weight models are easier to hijack in linear multi-agent workflows, while a terminal fixer mostly undoes it.