On May 19, DeepSeek issued a statement about
On May 18, multiple users reported that inputting the "<think" characters in DeepSeek's web version caused the model to return content that appeared to be other users' historical Q&A, some involving sensitive information like Chinese fortune-telling (Bazi), triggering data-leak concerns. The technical team's investigation found:
From a large-model principle perspective, the high-frequency association between
Though a false alarm, the incident reveals three layers of issues: insufficient boundary testing for special characters, low user ability to distinguish between hallucination and leak, and privacy architecture needing continuous reinforcement. DeepSeek says it will conduct targeted training to optimize the model's handling of special-character scenarios. The whole industry should learn from this: as model capabilities iterate rapidly, systematic testing of edge conditions and safety protection cannot be left behind.