river.io/the dark factory
Order 0174 August 20266 minBriefing

The bug hunt becomes a factory

Microsoft shipped its first dedicated cybersecurity model. It drives a harness of more than 100 agents to 95.95% on CyberGym, at half the cost. The same machinery has already produced 16 real Windows CVEs. Autonomous vulnerability discovery is now a product.

In early August 2026, the most important development in autonomous software was not a code-writing agent. It was a code-breaking one. Microsoft announced MAI-Cyber-1-Flash on July 27 and 28. It is Microsoft's first dedicated cybersecurity model. Its delivery vehicle, Project Perception, entered public preview on August 3.

The numbers are the story. An autonomous bug-hunting system now finds vulnerabilities at operating-system-kernel depth. It works at scale, and at half its previous cost. The evaluator side of the automated software factory is industrializing.

What Microsoft shipped

MAI-Cyber-1-Flash is a cyber fine-tune of MAI-Code-1-Flash. It is a sparse mixture-of-experts model. A model of that kind activates only part of its parameters on each request. This one has 137 billion total parameters, 5 billion active, and a 256k context window. Microsoft designed it to find hard vulnerabilities in complex code.

The model slots into MDASH. MDASH is Microsoft's multi-agent vulnerability harness. It orchestrates more than 100 specialized agents across multiple models.

With the new model inside, the system scored 95.95% on CyberGym. CyberGym is a benchmark of 1,507 real-world vulnerability-reproduction tasks drawn from 188 OSS-Fuzz projects. The score was 88.45% in May. Microsoft says the result tops Google's Gemini 3.5 Flash Cyber, OpenAI's GPT-5.6 Sol, and Anthropic's Mythos 5. Microsoft also states that it trained the model for defensive tasks, that is patching, and not for offensive ones.

MDASH with MAI-Cyber-1-FlashFigure
CyberGym score (1,507 tasks, 188 OSS-Fuzz projects)95.95%
Previous best configuration (May 2026)88.45%
Specialized agents orchestrated100+
Tasks handled by the small model~90%
Cost saving versus previous configuration~50%
Windows CVEs produced by MDASH-assisted work (May)16
Of which critical remote code execution4

The economics are the architecture

The design decision worth studying is the routing. Microsoft tuned the small model to handle roughly 90% of tasks. The small model escalates the hardest 10% to GPT-5.4. That split gives a 50% cost saving against Microsoft's previous best MDASH configuration. Tiered model routing uses a cheap specialist for volume and a frontier model for exceptions. It is becoming the standard shape of production agent fleets.

Real-world output, not just benchmarks

MDASH-assisted work generated 16 CVEs in the Windows networking and authentication stack in May. Four of them were critical remote code execution flaws. The system also ran retrospectively against past cases. It recovered 96% of 28 MSRC cases in clfs.sys, and 100% of 7 in tcpip.sys, over a five-year window. Autonomous vulnerability discovery at OS-kernel depth is no longer speculative.

Multi-agent orchestration pays off in verification, not in generation.

A small tooling note with a large implication

GitHub released Copilot CLI v1.0.78 on August 3. It shows a live timing display for each tool call. That is a small but real observability win for agent loops. The release also enables automatic updates for first-party plugins by default, and that deserves a raised eyebrow. The recent AgentBaiting campaign put roughly 7,600 malicious repositories on GitHub. More than 800 of them posed as AI skills or MCP servers.

Against that backdrop, any auto-updating capability channel into an agent runtime is a supply-chain surface. It does not matter whether the channel is first-party.

SOURCING

The Copilot CLI release details come from a third-party changelog aggregator. Treat them as unofficial. Microsoft reported the CyberGym comparisons itself.

How we apply this at River.io

The adversarial reviewer is the next loop we build, and we build it on low-stakes repos first. MDASH shows that verification is where multi-agent orchestration earns its keep. A scaled-down version fits our factory today. We want an autonomous find-bugs loop that fuzzes, statically analyzes, and files GitHub issues with citations. We point it at sloth, MeowPassword, or weathergalactic. Sloth is doubly interesting because it is itself a static analyzer, so a loop that both runs it and stress-tests its detectors compounds.

Our regulated products stay human-gated: CareTime, TimeForCare, and MaterialsAndPractices. Reading an autonomous reviewer's findings is safe at any stakes level.

Tiered model routing is a cost discipline, not just a hyperscaler trick. Microsoft's 90/10 split maps directly onto a small shop. We use inexpensive, fast models for lint triage, test scaffolding, and issue grooming. We keep frontier models for synthesis and design. We route by task difficulty, not by habit.

Zero third-party dependencies is a defensive posture in the machine-speed patching era. Autonomous systems now find kernel-depth CVEs at scale. Attackers will run the same play against application stacks. The fattest target is dependency sprawl. Native, zero-dependency code does not eliminate bugs, but it shrinks the CVE surface you must race machines to patch. For our work as a Medicaid EVV vendor, auditors understand that argument immediately.

We turn auto-update off in agent tooling. Auto-updating plugins are convenient. They are also exactly the wrong default for a regulated pipeline. We pin agent-runtime and plugin versions like any other dependency. We upgrade deliberately, on our schedule, with a diff review.


Sources

Vendor and blog figures show direction, not audited benchmarks. Microsoft reported the CyberGym comparisons itself. The Copilot CLI release details come from a third-party aggregator.

← The Dark Factory Subscribe by RSS Reply by email