b14g Pauses Contracts After 97 Million CORE Drained in Unauthorized Withdrawals

Published November 1, 2026, 01:50 AM PKT. Based on b14g's security announcement of October 31, 2026, as reported by EconoTimes and Dave Finances on October 31, 2026, and on a BBX news flash of October 31, 2026. The project has not published a technical cause, a dollar value for the loss, or a count of affected users, and a detailed post-mortem is still pending.

Bitcoin-yield platform b14g disclosed a security incident on October 31, 2026, in which approximately 97 million CORE tokens were taken from its protocol in unauthorized withdrawals. The project said the withdrawals occurred at 09:29 UTC, moving the tokens to attacker-controlled addresses, and that it paused the affected contracts in response. It is now coordinating with the Core blockchain team, exchanges, and security researchers to investigate and to try to recover the funds, according to the announcement as reported by EconoTimes and Dave Finances.

97 million CORE moved at 09:29 UTC

The single hard figure in the disclosure is the token count: about 97 million CORE, the native token of the Core blockchain, withdrawn without authorization from b14g's staking infrastructure. The project disclosed two addresses associated with the incident, including 0x27758c30f8e424fbd8ca605bf31e9496c26ce92c, according to Dave Finances. The announcement did not name a vulnerability, an attacker, or a method of entry, so how the withdrawals were authorized remains unexplained for now. Readers should also note what the figure is not: b14g has not converted the 97 million CORE into a dollar loss, and no verified valuation has been published, so any dollar figure circulating for this incident is an estimate by others, not the project's number.

68 million traced, 9 million frozen

Initial tracing gave two partial location figures. About 68 million CORE remained on the Core network in wallets linked to the incident, and exchange partners had frozen about 9 million CORE tied to the attacker, according to the project's announcement as reported by both EconoTimes and Dave Finances. The frozen 9 million CORE is roughly 9% of the reported drain. Neither figure should be read as recovered funds. A freeze stops movement, it does not return tokens to users, and the disclosures do not establish whether the traced and frozen balances overlap, how much can ultimately be returned, or which parties retain control over the assets. That distinction matters: the 68 million CORE still sitting on the Core network may remain inaccessible without further recovery measures, and the 9 million CORE at exchanges is restricted, not refunded.

Bitcoin staking untouched, CORE staking hit

The incident concerns CORE staking infrastructure, not b14g's Bitcoin deposits. Bitcoin staked through b14g remains time-locked on the Bitcoin network and was unaffected, the project said, a point both EconoTimes and Dave Finances report. That boundary is the most important reassurance in the disclosure so far: users who staked Bitcoin through the platform are not described as affected, while the loss sits in the CORE side of the protocol. It also frames what the post-mortem must explain, namely how CORE staked through b14g's contracts could be withdrawn without authorization while the Bitcoin leg stayed locked.

What b14g has not said yet

The gaps in the disclosure are as notable as the figures. There is no technical cause, no final loss figure, no number of affected customers, and no timetable for user instructions beyond the promised detailed post-mortem. The incident also lands in the same week as the far larger Binance security incident, in which about $6.3 billion was stolen on October 29, but no source has linked the two events, and they should not be treated as one story: different platforms, different assets, and different disclosed facts. For b14g users, the next substantive evidence will be the post-mortem, independently verifiable recovery figures, and instructions for affected stakers. Until then, the confirmed facts are the 97 million CORE drain at 09:29 UTC on October 31, the contract pause, the 68 million CORE traced on the Core network, the 9 million CORE frozen at exchanges, and the unaffected Bitcoin staking position.

This article is news reporting and is not investment advice.

Sources

• b14g security announcement, October 31, 2026 (primary source for the approximately 97 million CORE unauthorized withdrawal, the 09:29 UTC timing, the contract pause, the approximately 68 million CORE traced on the Core network, the approximately 9 million CORE frozen at exchanges, the unaffected Bitcoin staking position, and the pending post-mortem, as reported by EconoTimes and Dave Finances)
• EconoTimes, B14G Ties Protocol Contract Halt to 97 Million CORE Drain (published October 31, 2026, secondary source for the 97 million CORE figure, the contract halt, the 9 million CORE exchange freeze, and the unaffected Bitcoin staking position)
• Dave Finances, Crypto roundup: Binance hack, CORE theft and USDC crunch (published October 31, 2026, secondary source for the 09:29 UTC withdrawal time, the 68 million CORE traced on the Core network, the 9 million CORE exchange freeze, the disclosed attacker address, and the pending post-mortem)
• BBX, b14g protocol CORE unauthorized withdrawal news flash (October 31, 2026, secondary source confirming the approximately 97 million CORE figure, the contract suspension, the 68 million CORE on the Core chain, the 9 million CORE exchange freeze, and the unaffected staked Bitcoin)