b14g

b14g took a hit too

October 31, 09:29 UTC
About 97 million $CORE staked through b14g
were withdrawn without authorization and transferred to an attacker’s address
The project then paused the affected contracts

Tracking update
About 68 million remain on the Core chain
Exchange partners have frozen about 9 million related tokens
BTC staked through b14g
was still subject to Bitcoin network timelocks,
so it wasn’t swept up in this incident

The on-chain postmortem is even more troubling
The attacker submitted withdrawal requests for 91 staking positions
with the requested amount set to 0
The underlying staking logic interpreted 0 as “all”
emptying the positions in a single transaction
Worth about $1.47 million
The contract was paused about 66 minutes too late

The cause is clear
It wasn’t the entire Core consensus that failed
The staking coordination layer let an invalid parameter through
The project says positions staked directly on Core were not affected

What to do
For dual-staking and restaking products,
check emergency pause permissions and parameter validation first
Don’t look only at APR
After an incident, follow the official postmortem and freeze updates

$CORE $BTC

#B14g约9700万枚CORE遭未授权转移 #b14g #StakingSecurity

CORE: About 97 million CORE were stolen from b14g—not $97 million. So why are the BTC staked through it safe?

Another one. The official b14g X account, a BTC staking protocol, posted a security update last night. Here’s the original, broken down into a few points:

1. Timing: At 09:29 UTC on October 31 (17:29 Beijing time), about 97 million CORE staked through b14g were withdrawn without authorization and transferred to addresses controlled by the attacker.
2. Response: After discovering the incident, the team paused the affected contracts. It is working with the Core team, security partners, and exchanges to track the funds and coordinate efforts to freeze and recover them.
3. Where the funds went: According to current tracking, about 68 million CORE remain on the Core chain. Exchange partners have frozen about 9 million CORE linked to the attacker.
4. BTC: BTC staked through b14g remains time-locked on the Bitcoin network. The official statement says it was not affected.

A few facts worth clarifying:
· 97 million is the number of tokens. Quite a few reports have described it as “$97 million,” which is a huge difference. The official statement gave no dollar amount for the losses, and I won’t estimate one for them.
· “Still on the Core chain” does not mean “recovered,” and “9 million frozen” does not mean compensation. The announcement did not say whether these two figures can be added together.
· The BTC is safe because it is locked on the Bitcoin network itself and was not handed over to a contract. The incident affected another layer: the CORE staked in the contract. One product, two assets, two kinds of risk.
· The technical cause has not been announced yet. The official team says it will publish a detailed postmortem. Until then, any “vulnerability analysis” is just speculation.

When you use BTCFi products, can you tell which of your assets are locked on-chain and which are held in a contract?

#BTCFi #安全事件 #b14g

#b14greportsunauthorizedtransferofabout97mcore
🚨 B14G SECURITY ALERT: 97 MILLION CORE STOLEN!
CRYPTO SECURITY INCIDENT
Crypto Post 📰
Bitcoin dual-staking protocol b14g has reported an unauthorized withdrawal of approximately 97 million CORE tokens from its staking contracts on October 31, 2026.
🔴 Around 68 million CORE reportedly remain on the Core network.
🔒 Exchange partners have frozen approximately 9 million CORE.
⚠️ b14g has paused the affected contracts and is working with Core DAO and security partners to investigate and recover the funds.
✅ BTC staked through b14g reportedly remains unaffected.
The technical cause and full impact are still under investigation.
What does this mean for CORE's security and investor confidence?
#CORE #B14G #CryptoSecurity #CryptoHack
$BTC $BNB