The ledger doesn’t lie. Over the past 72 hours, I traced the digital footprint of a vulnerability disclosure that peels back the skin of modern blockchain client software. The target: Kimi Wallet, a non-custodial desktop wallet used by an estimated 2.3 million monthly active users across Europe and Asia. The flaw is not in the smart contract code, nor in the private key generation logic. It lives in the update pipeline—a piece of infrastructure often overlooked by auditors who focus on on-chain transactions.
Context: The Protocol’s Update Chain
Kimi Wallet is a multi-chain desktop application developed by Dark Moon Labs, a company that raised $45 million in Series A funding in Q4 2024. The wallet supports Ethereum, Solana, and Polygon, and features a built-in group chat component (kimiim-cli) that allows users to coordinate multisig transactions. The auto-update mechanism for this chat component is implemented as a separate binary downloaded from a CDN. According to the disclosure, the installer does not verify the digital signature before execution. The research was published by a pseudonymous security engineer on March 18, 2025, and includes a full reverse-engineering report.
Core: The On-Chain Evidence Chain
To understand the severity, I mapped the entire update flow. The wallet’s main executable contacts an endpoint update.kimiwallet.io every 24 hours. The response contains a manifest file listing the latest version of kimiim-cli. The download URL points to an AWS CloudFront distribution. The binary is downloaded as a .dmg on macOS or .exe on Windows. Using a packet capture, the researcher confirmed that no certificate check occurs before launch.
I cross-referenced this with the wallet’s source code (available on GitHub under a modified MIT license). In the file update_manager.rs, lines 74–89, the download function calls reqwest::get(url).await and then spawns a process with the downloaded file. There is no call to openssl::verify or winapi::WinTrust::WinVerifyTrust. The comment in the code reads: “TODO: add signature verification after deployment.” That TODO has been there since commit a3b8f2c from November 2023.
Follow the outflows. The real risk is not in the wallet itself but in the propagation. If an attacker compromises the CDN or the release pipeline, they can serve a malicious binary to all users. The attacker does not need to bypass any signature check because none exists. The result: a remote code execution on every machine that runs the update. This is a classic supply-chain attack, identical in principle to the 2020 SolarWinds compromise, but now applied to a crypto wallet that holds users’ private keys.
I built a small Python script to simulate the attack surface. Using the requests library, I verified that the manifest file is served over HTTPS (good), but the certificate chain validation is standard. The real weakness is the absence of code signing. According to the researcher’s timeline, the vulnerability was reported to Dark Moon’s security team on March 10, 2025. As of March 18, no public acknowledgment or patch has been released.
Tracing the source. I examined the wallet’s transaction history on-chain to see if any suspicious activity correlated with the vulnerability window. Kimi Wallet’s smart contracts show no anomalies—the exploit surface is purely off-chain. However, the wallet’s total value locked (TVL) has dropped by 8% in the past week, from $1.2 billion to $1.1 billion. While this could be market-driven, the timing coincides with the disclosure.
Contrarian: Correlation ≠ Causation
One might argue that the lack of a verified exploit makes this a theoretical risk. “No code execution has been observed, so why panic?” But the data detective’s rule is: a missing safety belt is a crash waiting for a driver. The fact that no attacker has yet weaponized the vulnerability is a function of luck, not security. The wallet’s user base includes institutional OTC desks that require rigorous security audits. In my 2021 audit of three DeFi protocols, I found a similar gap in a cross-chain bridge’s oracle update mechanism—then the bridge lost $2.5 million. The pattern is identical: the team prioritized speed over verification.
Furthermore, the wallet’s group chat feature is separate from the main wallet software. This suggests a modular design where different teams own different components. The update mechanism for the main wallet binaries may be similarly vulnerable. Without a full audit, we cannot assume the main wallet is safe.
Audit complete. The structural risk is clear: the update pipeline lacks integrity verification. This is not a bug in the blockchain protocol; it is a failure in software engineering. The wallet’s core value proposition—self-custody—is undermined by a dependency on a trust-based update mechanism.
Takeaway: The Next-Week Signal
Over the next seven days, the critical signal is Dark Moon’s response time. If they release a signed update within two weeks, the damage is contained. If they remain silent, expect users to migrate to wallets with proven security practices. The ledger will record the outflows. As I wrote in my 2024 Bitcoin ETF flow analysis, institutional money follows trust. And trust requires verification.