Morning Edition · Friday, October 9, 2026Published at 1:49 AM EDT · New York
Investigators trace the Bitget theft to zero-day flaws in two third-party security appliances and to North Korea-linked actors, while NEAR Intents, Duelbits, Nostra and SingularityNET lost funds through custody integrations, private keys, oracles and cloud access.

Rekt News has published post-mortems on a cluster of recent incidents. In most of them the failure point was infrastructure around the contracts, not contract code. The largest is Bitget. The exchange disclosed on September 24 that attackers took $387.5 million from its hot and warm wallets across 11 chains, including Ethereum, Tron, the XRP Ledger and Zcash. Separate investigations by SlowMist and Mandiant, the cyber-defense arm of Google Cloud, found that the attackers compromised two third-party security appliances with zero-day exploits. They used that access to obtain high-level internal credentials and to issue withdrawal commands that bypassed Bitget's risk controls. SlowMist dated the earliest malicious activity to August 31, more than three weeks before the theft. Circle, Tether and NEAR Intents froze about $1.1 million. Chainalysis attributed the theft to actors tied to North Korea, and Bitget cites IP behavior and on-chain analysis that point the same way. Pyongyang does not comment on such attributions.
On October 1, NEAR Intents lost $3.8 million and restricted deposits and withdrawals on 11 networks. The root cause was a bug in the interaction between the NEAR Intents contract and the custody architecture of Omni, its bridge, which allowed unauthorized withdrawals of USDT from a hot wallet on BNB Chain. Alex Shevchenko, NEAR Intents' general manager, publicly named the attacker and set a 48-hour deadline. The full $3.865 million came back within 24 hours.
The crypto casino Duelbits lost about $7 million when an attacker moved funds from its hot wallets on five chains in a suspected private-key compromise. The casino has since resumed operations. Nostra, a lending protocol on Starknet, lost $3.5 million to an oracle exploit. At SingularityNET, an attacker reached the project's cloud infrastructure and used it to mint tokens on its bridge without authorization and drain funds. BeInCrypto counts a 462% month-on-month jump in hack losses in September, driven by Bitget.
Part of a tracked trend
Losses Move to Components That Worked as Designed
A growing share of DeFi losses will come not from buggy contract code but from components behaving exactly as specified — oracle forwarders, validator signature sets, governance votes and other trusted off-contract inputs — so audits and bug bounties scoped to on-chain code keep missing the failure surface, and protocols will be repeatedly forced to extend review, scope and monitoring to their privileged operational infrastructure.
Start a discussion in Townsquare.
More from this edition
If North Korea is responsible, Bitget can place blame on a state actor and an unnamed appliance vendor instead of its own controls. Analytics firms that trace and freeze stolen funds also gain support for wider monitoring mandates.
Bitget, Chainalysis and Elliptic made the North Korea attribution, based on laundering paths that overlap with earlier thefts such as Bybit (Chainalysis, Elliptic). The coverage reviewed cites no government attribution. Bitget first reported $351.6 million and later revised the figure to $387.5 million, and no one has named the vendor whose security appliances failed.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
Every incident here except Nostra's oracle failure came through operational infrastructure: appliances, cloud accounts, hot-wallet keys and custody integrations that no smart-contract audit covers. That puts centralized exchanges and any protocol that runs a hot wallet or a bridge relayer at risk, along with the insurers and market makers who price counterparty exposure to them. The Bybit theft of February 2025, also attributed to North Korea and also executed through infrastructure around the signing flow, was followed by industry-wide reviews of signing tooling and did not slow the attacks. The likelier outcome over the next few months is that exchanges move more balances into cold storage and tighten vendor access. Withdrawal times rise, and North Korea-linked groups shift to softer targets such as casinos, payment processors and bridges. A major theft traced to a flaw in audited contract code, not operational access, would undercut this read.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Rekt News (Bitget) · The Hacker News · CryptoTicker · CoinDesk · Crypto Briefing · ForkLog · BeInCrypto
Comments
0No comments yet.