At 09:29 UTC on 31 October 2026, about 97 million CORE staked through b14g was withdrawn without authorisation and sent to addresses the project called attacker-controlled. b14g said so in a security update on X at 16:38 UTC the same day. It had paused the affected contracts. It said it was working with the Core team, security partners, and exchanges to trace the funds and to freeze what could be frozen. It has not said how the withdrawals were made. This page will not say it either.
b14g is a staking application on the Core blockchain, which is a different ledger from Bitcoin. The product it describes is dual staking. A bitcoin holder locks bitcoin on the Bitcoin network, on a timer, and does not send those coins to b14g. A CORE holder stakes CORE through b14g’s contracts on Core. The two sides are paired so they can share rewards. The bitcoin and the CORE are not the same asset, they do not sit in the same place, and a balance of one is not a balance of the other. See What is Bitcoin?. See What is crypto staking?. A reward line in an application is not a savings rate, and the application is still someone else’s software around the lock.
What happened
b14g’s scope sentence is the one that decides who was hit. Only CORE staked through b14g. Bitcoin that users had staked through the same product “remains time-locked on Bitcoin and was not affected”. A time lock means those bitcoin cannot be spent until the lock expires, and they stay on Bitcoin while they wait. The project’s claim is that the lock held. CORE on Core is a separate coin. What if you send crypto on the wrong network?.
The tracing in that same post put about 68 million CORE still on the Core chain, and about 9 million CORE frozen by exchange partners. Those two figures do not add up to 97 million. b14g did not say where the remainder sat. A freeze is a token stuck at an exchange. It is not a return to the staking contract, and it is not a payment to the person who staked. The 68 million still on the chain is a location. It is not a refund.
Updated on 5 November, from b14g’s recovery update posted on 2 November. The project said a hard fork of Core that day moved 68,146,177.22 CORE off three attacker-controlled addresses, about 70 percent of the 97,045,563 CORE it counted as affected. It called the move a one-time state adjustment. It said the adjustment did not reverse transactions, did not mint CORE, and did not change the total supply. The tokens have not been distributed to the people who staked. There is no claims process. About 9 million CORE that the earlier note said exchanges had frozen has not been returned. The 68 million that the 31 October note had described as still on the chain is the pile this adjustment moved. A location on 31 October and a recovery address on 2 November are not a payment to a user. This page will not publish the addresses, and it will not describe the withdrawal.
Later the same day a message signed as the b14g team offered 10 percent of any further amount returned voluntarily, with the rest directed to a recovery address, and a deadline of 23:59 UTC on 6 November. Reports of that message say it also accepts ether or tether if the CORE was already sold. The offer is not a distribution plan. A message that asks for a recovery phrase is not the offer.
Updated on 7 November, from a post b14g made on 5 November, as quoted by Crypto Times. This page did not open that post. The project said it had checked the balances on the affected staking orders and would repay in two parts. The recovered 68.15 million CORE would go back onto those orders within five to seven days. Each person would receive about 70.2 percent of the balance that was taken. On that ratio, someone who had staked 1,000 CORE would receive about 702 CORE. The remainder would be paid from half of b14g’s future revenue on Core staking, claimable each week, and any further CORE later recovered from exchanges would be added to that. A plan to pay is not a payment that has landed. The voluntary-return deadline of 23:59 UTC on 6 November has passed. This page has not found a company total for anything returned under that offer. The earlier note’s about 9 million CORE frozen by exchanges stays that note’s figure. Later write-ups split the tracing across named venues, including a freeze one venue has not confirmed to b14g. Those splits do not replace the 9 million. The 5 November post is also an account of the cause. This page will not describe it.
Updated on 13 November. TokenPost, and Gate citing Foresight News, say b14g announced that day that the contracts are running again. Deposits, withdrawals, staking, and reward claims are open on the site. This page did not open that announcement. An application that accepts a new deposit is not the 68.15 million CORE sitting on the orders of the people who lost it. The weekly claims, and the promise to pay the rest from future staking revenue, are still that plan. They are not a receipt. The about 9 million CORE the earlier note said exchanges had frozen stays that note’s figure.
At 17:24 UTC the same day, Core DAO posted that “the Core network is secure”. Its account was that consensus, validators, and staking contracts operated normally, and that CORE staked directly with validators, or through protocols other than this one, was not affected. Core said it was helping b14g and the exchanges trace and freeze the funds, and that most of the stolen CORE remained on Core. The chain’s statement and the application’s statement are different layers. Core saying the network is intact does not put the 97 million back into b14g’s contracts. b14g saying the contracts are paused does not mean Core stopped producing blocks.
Dollar headlines are an evening multiplication, not the company’s sentence. A market print around 20:48 UTC put CORE near $0.0138, and one outlet’s arithmetic at that price put 97 million CORE near $1.34 million. Other writeups the same weekend used about $1.47 million. The price had also moved down on the day. Use the token count. The dollar figure depends on the hour, and b14g did not publish one.
b14g said it will publish a post-mortem covering the cause, the impact, and the next steps for affected users. As of the morning of 1 November, that post-mortem was not out. We will not fill the gap with a description of the withdrawal, and we will not publish the addresses the project named. Phishing will publish a lookalike.
Why it matters
If you staked CORE through b14g, that is the pile that moved. On 13 November the project said those contracts are taking deposits and withdrawals again. An open door is not the missing CORE put back. If you locked bitcoin through b14g, the project says those coins stayed on Bitcoin under the time lock. Check that on Bitcoin, in a wallet that can show the lock, and not on a webpage that arrived on 31 October. If you staked CORE directly with a Core validator, or through a different application, Core DAO says this incident was not that stake.
The failure mode to keep distinct is the one where the bitcoin claim was the thing that broke. Liquid printed unbacked L-BTC. Nomic’s nBTC broke, and Osmosis froze allBTC. Those were vouchers that were supposed to be bitcoin and were not fully backed. b14g’s account this week is the other way around: the application’s CORE moved, and the bitcoin lock was the piece that did not. A voucher story and a token-on-another-chain story are both “not your bitcoin”. They are not the same loss.
Nobody who can restore a CORE stake needs a recovery phrase, a fresh approval, or a deposit to a new address “so the freeze can be reversed”. See How do you keep crypto safe? and How crypto wallets actually work. The same week’s other losses were a trading bot on Solana, a rollup bridge, and an EVM-side token on Humanode. Bloom’s 9,408 SOL, zkLink’s halt, and Humanode’s eHMND are those pages. None of them spent bitcoin that was time-locked on Bitcoin.
What happens next
Whether anyone can actually claim their share of the 68.15 million CORE, which the 5 November post promised and which a reopened website does not prove. The weekly claims against future staking revenue, which are a promise and not a balance. Whatever the exchanges do with the frozen slice, still the earlier note’s about 9 million until the company replaces that figure. Watch b14g’s own account and Core’s. We will not treat an open deposit button as “b14g users were made whole”, and we will not treat a time lock as a reason to send more bitcoin to a message.
Not a recommendation to stake, unstake, buy, or sell CORE or bitcoin. Not a finding that every bitcoin-staking application was hit. Not a description of the withdrawal. A contract that is running again is not a receipt.





