Skip to content
Sprint projectJul 27, 2026New Delhi

Loyal Lies: Auditing Secret Loyalties Under Attack and the False-Positive Problem in Blind Elicitation

Deven Choudhary, Adhiraj Pundir · Team False Positive

Submitted to Secret Loyalties Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Loyal Lies: Auditing Secret Loyalties Under Attack and the False-Positive Problem in Blind Elicitation

Code (opens in new tab)
Share

Auditors reach for elicitation because it is cheap and needs no knowledge of the trigger. You interrogate the model, amplify its weights, rank candidate beneficiaries, and report whatever name comes out. We show that those outputs look the same whether or not there is anything to find. We worked both sides of the problem. On 1.5B organisms where we knew the principal, six activation-probe designs collapsed under a representation-entanglement confound: a probe trained to separate two clean seeds of the same recipe, with no loyalty anywhere, hit AUROC 1.000. A grey-box logprob audit worked instead, ranking the true principal 1 of 120 at z=4.57, while a clean model exposed to that principal 455 times, a cross-principal organism, and an exposure decoy all stayed in the base band. Then we attacked our own detector. An obfuscation fine-tune buried the principal at rank 27 to 42 across five seeds with loyal behaviour intact, though it left one channel standing that the attack was never pointed at. The other half was blind. We audited three third-party 7B organisms without knowing the answer, proved one bit-identical to its base model at the weight level, and found the remaining two produced a reportable principal from every method we ran: candidate ranking, amplified interrogation, and a self-report that stayed stable across amplification strengths. None of the three claims survived verification, and the most convincing one came from a model that argued against its own stated principal when asked. We report three cheap checks that catch this, none of which require knowing the trigger.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. ¡Hola!

    I liked that you tested your own detector until it broke instead of stopping at the first thing that worked.

    The decoy model was smart too. Training a model that hears about a principal constantly but isn't loyal to it is how you find out whether you're measuring loyalty or just familiarity.

    As an improvement, for the defense, I would attack all of them at once and see what's left. That's the experiment I'd want next.

  2. I think this project is definitely strong and well controlled it has a strong experimental design especially in its use of multiple organisms seeds and blind verification checks. The main limitation is that the attack evaluation is inconsistent with its own prespecified behavioral gate. Like, the methods gate says that an attacked checkpoint only counts if it passes all 4 behavior gate criteria including specificity of at most 25% but the results say that 1/5 of the reported attack seeds had 41.7% specificity failure. I think the authors should've either excluded that checkpoint from attack results or given a clear explanation of why exactly they let it violate the pre-specified gate. Also, I think the attack result should be framed more narrowly in general. They show successful evasion of one targeted detection channel not like the general defeat of the detector.

Cite this project

@misc{choudhary2026loyal,
  title = {{Loyal Lies: Auditing Secret Loyalties Under Attack and the False-Positive Problem in Blind Elicitation}},
  author = {Deven Choudhary and Adhiraj Pundir},
  year = {2026},
  month = jul,
  note = {Submitted to Secret Loyalties Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/loyal-lies-auditing-secret-loyalties-under-attack-and-the-falsepositive-problem-in-blind-elicitation-ezwb}},
  url = {https://apartresearch.com/sprints/projects/loyal-lies-auditing-secret-loyalties-under-attack-and-the-falsepositive-problem-in-blind-elicitation-ezwb}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026