Skip to content
Sprint projectOct 25, 2026Delhi, India

Auditing Steganographic Collusion and Reverse Engineering Latent Misalignment in Dolos-1.5B

Vinyas Maurya · Team Evariste`

Submitted to AI Collusion Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Auditing Steganographic Collusion and Reverse Engineering Latent Misalignment in Dolos-1.5B

Code (opens in new tab)
Share

As I explored how language models interact in economic contexts, I became increasingly concerned about their potential to coordinate against their creators. My study focuses on the Apart Research Collusion Sprint and the challenge of red-teaming the Dolos-1.5B model. I discovered that in simple environments, models can inadvertently devise unexpected pricing strategies, whereas more complex contexts enable covert collusion. I emphasised the importance of multi-modal auditing to distinguish between genuine adaptation and deliberate deception. While testing ten collusion detection systems, I found that mutual information detectors were effective, whereas traditional linguistic analysis struggled. My analysis of Dolos-1.5B revealed that its coordination behaviour is tied to specific model layers and activated by certain Unicode shifts.

Reviews

Judging this Sprint?

Review “Auditing Steganographic Collusion and Reverse Engineering Latent Misalignment in Dolos-1.5B”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

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

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field 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 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.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

  1. This takes on a lot: three Track 2 questions plus the full Dolos challenge. The writing is easy to follow. But spreading across all of it means none of the claims get the support they need, and a few results contradict the text built on them. There’s also no code or data link, so nothing here can be checked.

    On Track 2: ColludeBench-v0 and the detector stack (cross-run MI, permutation invariance, watermark variance, acceptance bias, the union and martingale tests) all come from Tailor’s Audit the Whisper. The paper should say plainly that it re-analyses those trajectories with those detectors, and point to what’s new. A few readings also don’t hold up. An AUC of 0.346 isn’t “worse than useless.” Flip the sign and you get 0.654, so the detector’s direction is wrong, not its signal. In peer review, the colluding settings score higher accuracy and welfare than honest ones, which cuts against the harm story. Auction welfare is 0.000 in every row, which looks like a broken metric. Section 3 is all argument with no experiment, so “joint auditing captures 100% of premeditated lies” needs data behind it.

    On Dolos, the core mechanistic claims don’t match your own tables. In Table 3, unpatched Dolos and unpatched Qwen both output “As.” If the two models agree, patching can’t “restore” anything, so this table isn’t causal evidence of localization. Table 4 shows a standard ASCII space already at 0.829 divergence and underscore at 0.947. That suggests Dolos diverges from Qwen broadly, not through a whitespace trigger. The head “roles” (trigger router, attention sink) are labels on raw attention differences with no ablation behind them, and the gap between heads (5.5 vs ~4.2) is small. The audit thresholds (S > 2.5, a 3.4× energy surge) and the self-play claim appear without any experiment. The energy check also needs a baseline, so it isn’t really reference-free.

    What would help most: pick one thread and go deep. For Dolos, find a prompt where the two models actually differ, patch on that, report divergence over many prompts per delimiter, and zero-ablate the candidate heads. Decode embedding tokens 4102, 9238 and 19070 so readers can see they’re really the whitespace tokens. Smaller fixes: “Table 1” in 5.2.1 should be Figure 1, the abstract says layers 24–27 while 5.2.2 says 24–26, and “proves” is used where the evidence is suggestive at best.

    Read full reviewShow less

Cite this project

@misc{maurya2026auditing,
  title = {{Auditing Steganographic Collusion and Reverse Engineering Latent Misalignment in Dolos-1.5B}},
  author = {Vinyas Maurya},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/auditing-steganographic-collusion-and-reverse-engineering-latent-misalignment-in-dolos15b-zp9y}},
  url = {https://apartresearch.com/sprints/projects/auditing-steganographic-collusion-and-reverse-engineering-latent-misalignment-in-dolos15b-zp9y}
}