Published: October 28, 2026, 10:43 Beijing Time.

According to an October 28 report by BlockBeats, the growing use of AI tools for code audits, vulnerability discovery, and automated attack-script generation is lowering the barrier to attacks in the crypto sector.

The window between a vulnerability being discovered and exploited is shrinking, while weaknesses in supply chains, third-party components, and personnel are being exposed more efficiently. Several security incidents occurred in quick succession this week, with third-party dependencies and operational permissions standing out in particular.

Here are a few specific cases.

Solana transaction automation platform Bloom confirmed a security incident on October 26. Attackers exploited a complex remote code execution vulnerability in a third-party module to steal approximately 9,408 SOL (about $947,000) from 49 wallet addresses belonging to nine users.

The team said users’ private keys were neither accessed nor exposed, other wallets were safe, and all affected users had been fully reimbursed.

MYRIAD, a prediction market on BNB Chain, also suffered an exploit involving an internal operations wallet on October 26. Attackers used a private key leaked weeks earlier due to a vulnerability in a third-party library to manipulate the settlement outcomes of 10 markets.

After the team promptly revoked access, the attackers failed to withdraw any funds. The affected markets were voided and refunds were processed.

Around October 25, approximately 8.5 BTC was stolen from DotSwap V1 through a vulnerability in an outdated server-side signing flow.

Hardware wallet manufacturer NGRAVE had previously suffered a hijacking of the third-party push notification service used by its companion app. Fake alerts tricked users into entering their recovery phrases, resulting in losses of more than approximately $2.56 million. The company stressed that the hardware wallets themselves had not been compromised.

Keystone confirmed that its website had been breached, exposing customer records and device verification keys. It plans to destroy nearly 19,000 devices in inventory.

Risks related to personnel and operations should not be overlooked either. The impact of an internal data breach previously disclosed by Coinbase continues to this day. Attackers bribed overseas outsourced customer service agents to obtain sensitive data belonging to approximately 69,000 users, then demanded a $20 million ransom, which was refused.

The company stated that user passwords, private keys, and funds were not directly stolen. However, the leaked data was used in subsequent phishing and social engineering attacks, and the company estimates its overall response costs to be in the hundreds of millions of dollars.

Indian exchange CoinDCX confirmed a loss of approximately $15.99 million. The funds came from an old wallet that had reportedly been retired following an earlier hacking incident. A malfunction in the automated sweeping service caused deposits to accumulate, leaving them vulnerable to theft. The company absorbed the loss itself.

Taken together, these incidents share a clear pattern: the failures often involved not core private keys or underlying cryptography, but “peripheral components” such as third-party modules, outdated signing flows, permissions granted to outsourced staff, and sweeping services for retired wallets.

AI is helping attackers find and exploit these gaps more quickly. Projects may need to broaden their defensive focus from “protecting private keys” to covering the entire dependency chain and operational processes.

As for market prices, public spot market data showed that at around 03:49 UTC on November 20, 2026, BTC was trading at 62,250 USDT, down 1.463% over 24 hours; SOL was at 73.01 USDT, down 1.591%; and BNB was at 575.6 USDT, down 1.308%.

These prices are from Binance spot market snapshots and reflect rolling 24-hour data. Note that this market data is timestamped later than the news, so the two should not be directly compared. The ongoing impact of the security incidents on the relevant assets will need to be assessed in light of further disclosures.

For ordinary users, the takeaway from these cases is straightforward: be wary of any “security alert” asking for your recovery phrase, and watch out for phishing links. For platforms, auditing third-party dependencies and staff permissions may be just as important as auditing code.