Kimi Work adjunta secretamente registros sin procesar de cinco sesiones recientes de agentes a los informes de retroalimentación

Finding

Submitting feedback in Kimi Work automatically triggers uploads of a diagnostic archive and bounded raw-record archives from the five most recently updated agent sessions, while the form does not list those attachments or let users choose which sessions are included.

How we verified

Methods: reverse engineering, testing.

RuntimeWire reverse-engineered Kimi Desktop 3.1.5 and its bundled Daimon 0.5.49 service. Static tracing established that the renderer invokes diagnostic-log and raw-record uploads before submitting feedback; the main process sorts all Work conversations by updatedAt, selects five, requests an archive for each and sends the ZIPs to /file/upload_simple. In a Windows Firewall-blocked test launched from Plugins feedback, Kimi selected five distinct conversation IDs, each reached the HTTP upload stage and failed with ERR_NETWORK_ACCESS_DENIED. Kimi's log concluded: "ok: 0/5 archives uploaded in 166ms." Official documentation describes wire.jsonl as the agent's complete communication record and says it includes request parameters, tool schemas and MCP tool listings.

RuntimeWire extracted the production ASAR and Windows Daimon bundle without modifying them, hashed the relevant files and traced the feedback flow from the renderer through preload IPC, the desktop main process, Daimon's archive generator and the two Kimi HTTP endpoints. We decoded the archive limits and sanitization logic, checked Kimi's public help, session-export documentation and privacy policy, and searched for prior reporting. For runtime validation, we blocked outbound traffic from the signed Kimi.exe, started the application, submitted harmless feedback from the Plugins page and reviewed the resulting main-process logs. The firewall denied every external request. We did not inspect or transmit conversation-record contents.

Tested versions:

• Kimi Desktop 3.1.5
• release 3.1.5+c88420152; Daimon 0.5.49; Windows x64; Electron 41.7.2

Reproduction

RuntimeWire independently reproduced the core finding.

Install Kimi Desktop 3.1.5 on Windows and ensure the Work interface has at least five recent conversations. Fully exit Kimi. Create a temporary outbound Windows Firewall block for Kimi.exe. Start Kimi and open Work > Plugins. Click the feedback icon, enter harmless test text and press Submit. Open %APPDATA%\kimi-desktop\logs\main.log. Search for FeedbackRawRecords. Confirm five distinct conversation entries fail with ERR_NETWORK_ACCESS_DENIED, followed by "ok: 0/5 archives uploaded." Remove the temporary firewall rule.

File hashes

• 4ecfdc4ff9ad57707f050888056babeac79eb85b61c3e0a369b612d809f80122 app.asar
• f92a5544c72a51e742060866a9cdb7c8129b553b36739a8d45a96e5aa9884e23 daimon-bundle.tar.gz
• bc7a22afe8c91b8196550e6401797d55ff7565f80da5dd6109bcff38ee5eb079 out/main/index.js
• aa4193cf1ac834842219823adaeb65d91c30d6b4739a95aad36c1a63e69dc508 preload-kimi-agent.mjs
• 57e81f63c0d21f38a2c74f0ea55edb63e4a07f8e9e64dda20a3e2cabf64028ea common-DPn1pjsS.js
• 794019269179bd285a5c16cdb7abe2f7d8f82737e1a3e1d1e90efd6422faca5d c-TFPRZLAB.js
• 799d67dc410e99553e68c9bc151cf95c559f2cedcc3936ab8f8800e8fc97cb28 c-ECRC3J6R.js

Company response

RuntimeWire requested comment; the company had not responded by publication time.