On 14 November 2026 Proxima, a Solana trading app, said an attacker took 5,324.2 SOL from 870 wallets belonging to 181 users. The post-mortem, timestamped 22:16 UTC and quoted by several outlets, puts the drains between 03:22 and 05:42 UTC. Proxima says that is about 0.1 percent of the wallets on the platform, that only SOL was taken, and that every confirmed loss has been covered from its own treasury. This page did not open the post. It will not describe how a log line was switched on, and it will not describe the monitoring flaw.
A trading app that can create a wallet, and that can send from it, is holding the keys. What is Solana (SOL)?. A debug log is a record the software writes so someone can see what it did. A key in that record is a key that has left the wallet. How crypto wallets actually work. The same shape, on a different day, is Bloom’s trading bot. Software that can spend is a hot wallet, whether or not the marketing calls it a log.
What happened
The morning post, at 06:48 UTC, put the affected funds at about $200,000 to $250,000 and said users would be reimbursed. The post-mortem is the SOL count. That count replaces the morning range. It is not added to it. Proxima did not, in the quoted post-mortem, publish a dollar figure. An outlet’s multiplication of 5,324.2 SOL by a price is that outlet’s arithmetic.
The company’s account of the cause, at the level of the outcome, is that private-key material was written into diagnostic logs, and that those logs sat in a monitoring system an attacker could reach. Proxima says the keys were logged from 3 November until 13:20 UTC on 10 November, when that logging was switched off. Wallets created after that minute were not part of this exposure, it says. Wallet age alone does not decide it: a key is exposed if it was written down, including an older wallet whose key was used in that window. Proxima says its primary databases were not directly breached. It says it replaced exposed wallets, moved remaining balances to the new ones, and credited each affected account with the SOL that was taken. An auditor, Pashov Audit Group, says it checked that the refunds were paid on-chain. That is the auditor’s sentence. A treasury payment is the company paying. It is not the stolen SOL coming back.
Why it matters
If the app created your wallet, or you imported a key into it, during that window, Proxima’s own account is that the key was in a log. A key that has been in a log is a key to stop using, including anywhere else the same key can spend. If the wallet was created after 13:20 UTC on 10 November, and its key was never used in the logged window, Proxima says this exposure is not that wallet. If your SOL sits in a wallet this app cannot sign for, this page did not spend it. See How do you keep crypto safe?. A message that offers to “migrate” a wallet, and asks you to paste a recovery phrase, is not the post-mortem.
Proxima says the app was taken offline, secured, and brought back the same evening with the refunds credited. Automated trading sessions were paused and have to be started again on the new wallets. A screen that is back is not a statement that a logged key is safe to keep using.
What happens next
Whether every one of the 181 has the SOL the company says it credited, which the company and the auditor both say they have checked and which this page has not. The wallets Proxima said it would handle one by one because the positions were unusually large. Anyone who used an exposed key outside the app. Watch Proxima’s own account. We will not treat a treasury payment as the stolen coins returned, and we will not describe the log.
Not a recommendation to use, reinstall, or abandon Proxima. Not a finding that every Solana app was hit. Not a description of the monitoring system. The post-mortem’s own account is a SOL count, a log that held keys, and a claim that the loss has been covered.






