Field noteOct 24, 20261 min read1 source

Moonshot says Kimi K3.1 Pro was trained with cyber-related data removed to cap offensive capability before open-weight release

In one minute

Moonshot AI introduced Kimi K3.1 Pro, the first model in its K3.1 series, and Kimi K3.1 Pro Highspeed.

What changed: The launch post adds that Kimi K3.1 Pro was trained with cyber-related data removed to limit offensive capability before its open-weight release.

The company describes Pro as a 3T-class open-weight model with a one-million-token context window; Highspeed is claimed to deliver two to three times the speed. Both are available now through Kimi.com, Kimi Work, Kimi Code, and the Kimi API. Moonshot says full model weights will be released by November 4.

The accompanying technical post also describes cyber-risk controls for the planned open-weight release. Moonshot says it found cyber-related content in its mid-training corpus and cyber-related tasks in its reinforcement-learning environment mix as vulnerability-research performance increased. It says it removed that material from both stages while retaining general-purpose coding tasks.

Moonshot states that it does not intend to release open weights that extend the absolute frontier of cyber capability, and that K3.1 Pro's offensive cyber capability is deliberately below what its training pipeline could otherwise produce. The post does not provide an independent assessment of the filtering, a reproducible measurement of the resulting capability limit, or evidence that the controls prevent misuse after weights are released.

Evidence / sources

  1. 1kimi.com/blog/kimi-k3-1-pro
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicModelsExplore the models topic hub.
  2. 02topicOpen ModelsExplore the open-models topic hub.
  3. 03topicAi SecurityExplore the ai-security topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract