The Curious Case of the “极” Token Bug in DeepSeek V3.1

In recent weeks, several developers and AI enthusiasts have reported a peculiar bug in DeepSeek V3.1: the model occasionally inserts the Chinese character “极” (both in simplified and traditional forms) into its output without any clear reason. While this may sound minor, it has significant implications when working with structured data, code, or academic writing.

How the Bug Was Discovered

The issue first surfaced on third-party API platforms such as Volcengine and Chutes, where developers noticed random “极” characters appearing in generated outputs. These unexpected insertions caused downstream problems:

• Code generation: inserting a stray character broke compilation.
• Data tasks: malformed JSON due to the extra token.
• Technical writing: reduced readability and professionalism.

Initially, many assumed the problem was related to deployment differences — such as quantization, serving configuration, or hardware inconsistencies — introduced by third-party providers. However, further community testing showed that the same bug could be reproduced on DeepSeek’s official Playground, though at a lower frequency.

Possible Root Causes

Discussions within the community, including detailed threads on Reddit, Zhihu, Github, have highlighted some plausible explanations:

Token Adjacency Issue

• The token ID for “…” (ellipsis) is 2576, while the token ID for “极” is 2577.
• The closeness in the vocabulary table suggests the model may sometimes mispredict and output the adjacent token.
• Several Reddit users independently reproduced this behavior and noted its persistence across sessions, refer to Reddit discussion above.

Data Contamination

• During training or data cleaning, corrupted or low-quality samples containing “极” may not have been fully removed.
• Reddit contributors speculated that certain noisy text sources may have introduced the anomaly.

Model Shortcut Behavior

• Some speculate the model “learned a shortcut” that leads it to occasionally substitute “极” in contexts where it should produce an ellipsis or other tokens.
• A few community members observed that once the bug appears, it becomes more frequent in subsequent outputs — a kind of self-reinforcing loop.

What’s particularly concerning is that once triggered, the bug appears to persist across subsequent generations, leading to higher frequency of “极” insertions — as if the model becomes “stuck” in this erroneous behavior.

Impact on Developers

The severity of this bug depends on the application domain:

• Code Generation → Compilation errors due to stray characters.
• API Responses → JSON or XML parsing failures.
  

  JSON (invalid because of an injected character):
  {"id": 1, "name": "Alice", "scores": [10, 9, 8] 极}
  
  Python (syntax error due to stray character):
  result = compute(x, y) 极  # SyntaxError

• Academic and Technical Writing → Reduced clarity and trustworthiness.

For tasks requiring high precision and structured output, this is a blocking issue.

Final Thoughts

While the exact root cause has yet to be confirmed, the evidence — including independent verifications from the Reddit discussion — suggests that the “极” bug originates from the model itself rather than third-party deployment environments. This underscores the importance of rigorous dataset cleaning and vocabulary alignment during training.

For developers, the best workaround for now is to add post-processing validation steps to detect and filter out anomalous characters in critical workflows. However, a permanent fix will need to come from DeepSeek’s team in the form of retraining or patching the model.

The community has already raised awareness, and many hope DeepSeek will issue an official response and release a corrective update soon.