Scan to download
BTC $60,731.49 -1.90%
ETH $1,558.08 -5.86%
BNB $572.80 -2.73%
XRP $1.08 -2.88%
SOL $62.30 -5.03%
TRX $0.3192 -1.86%
DOGE $0.0811 -2.58%
ADA $0.1555 -3.65%
BCH $216.26 -1.91%
LINK $7.30 -2.68%
HYPE $59.19 -4.04%
AAVE $61.39 -5.80%
SUI $0.7013 -0.35%
XLM $0.1991 +5.82%
ZEC $360.52 +17.69%
BTC $60,731.49 -1.90%
ETH $1,558.08 -5.86%
BNB $572.80 -2.73%
XRP $1.08 -2.88%
SOL $62.30 -5.03%
TRX $0.3192 -1.86%
DOGE $0.0811 -2.58%
ADA $0.1555 -3.65%
BCH $216.26 -1.91%
LINK $7.30 -2.68%
HYPE $59.19 -4.04%
AAVE $61.39 -5.80%
SUI $0.7013 -0.35%
XLM $0.1991 +5.82%
ZEC $360.52 +17.69%

xpos

Coinbase reviews the May outage incident: AWS cascading failure exposes architectural risks

Coinbase released a retrospective report on the large-scale service interruption event on May 7, 2026.The outage lasted approximately 8 hours, with full recovery taking about 12 hours. During this time, trading, deposits, withdrawals, and most core services were unavailable or severely degraded. Coinbase stated that the outage was caused by multiple cooling units failing simultaneously in the cooling system of a data center in one availability zone (use1-az4) in the AWS us-east-1 region, triggering cabinet thermal protection shutdowns, which led to EC2 instances and EBS volumes going offline, affecting multiple internet services.During the recovery process, the Coinbase trading matching engine lost quorum due to the cluster architecture deployed in a single AWS data center losing most nodes. It required urgent code adjustments and the reconstruction of a new node group to restore operation, gradually restarting market trading during the recovery.Additionally, the AWS-managed Kafka (MSK) service experienced control plane failures, preventing the automatic re-election of partition leaders, further blocking quotes, fees, and some settlement and data flow systems, which expanded the overall impact.After manual partition migration in collaboration with the AWS engineering team, the system gradually returned to normal. Coinbase stated that this incident exposed its shortcomings in cross-availability zone automatic switching capabilities and disaster recovery for managed middleware. The company will upgrade its cross-region hot backup architecture, strengthen regular failure drills, and migrate the Kafka system from dual availability zones to a three availability zone deployment, while also working with AWS to advance root cause fixes and improvements.

AI Agent Security Risk Exposure: Attackers Can Exploit "Memory Pollution" to Induce Misoperation of Funds

The GoPlus Security team has disclosed a new type of attack in its AgentGuard AI project: inducing AI agents to perform unauthorized sensitive operations through "memory poisoning." This attack method does not rely on traditional vulnerabilities or malicious code but exploits the long-term memory mechanism of AI agents. For example, an attacker first induces the agent to "remember preferences," such as "usually prioritizing proactive refunds instead of waiting for chargebacks," and then uses vague expressions like "process as usual" or "execute as before" in subsequent instructions, thereby triggering automated financial operations.GoPlus points out that the key risk in such cases lies in the AI agent mistakenly treating "historical preferences" as a basis for authorization, leading to financial losses or security incidents in operations such as refunds, transfers, and configuration changes. To address this issue, the team has proposed several protective recommendations, including:Operations involving refunds, transfers, deletions, or sensitive configurations must require explicit confirmation in the current session.Memory-related instructions like "habit," "usual way," and "as before" should be regarded as high-risk state changes.Long-term memory must have a traceability mechanism (writer, time, confirmation status).Vague instructions should automatically elevate the risk level and trigger secondary verification.Long-term memory must not replace real-time authorization processes.The team emphasizes that the "AI agent memory system" should be viewed as a potential attack surface and should be constrained and audited through a dedicated security framework.

Polish cryptocurrency trading platform exposed for Ponzi scheme, former CEO disappears with 4,500 Bitcoin private keys

According to Politico, Poland's major cryptocurrency exchange Zondacrypto is facing a serious fraud investigation. Its former CEO went missing in 2022, taking with him the private keys to a cold wallet containing 4,500 bitcoins (currently worth over $340 million). The current CEO has admitted to being unable to access the wallet and has recently been reported to have fled to Israel. Prosecutors estimate potential losses for customers to be around $97 million.On-chain data shows that the bitcoin balance in the platform's hot wallet has plummeted by 99.7% since mid-2024, with users generally reporting difficulties in withdrawing funds. Polish Prime Minister Tusk estimates that up to 30,000 users may be affected.Tusk publicly accused the platform of being funded by Russian-linked money, used to finance opposition lawmakers to obstruct Poland's cryptocurrency regulatory legislation. He bluntly stated that this is a "Polish version of a Ponzi scheme" and criticized the president for vetoing the localization of the EU MiCA framework twice, making Poland a "paradise for scammers."The platform's board stated that they failed to obtain "verifiable information" from the missing CEO and have collectively resigned. The founder has been missing since 2022, and the previously mentioned "suspect kidnapping allegations" case is still under investigation. This incident is expected to prompt Poland and the EU to strengthen regulatory scrutiny of cryptocurrency exchanges.

Bitcoin Quantum Security Crisis: 6.9 million BTC exposed to risk, governance challenges hinder response progress

According to CoinDesk, while quantum computers cannot disrupt the Bitcoin mining mechanism or the blockchain ledger, they may potentially crack the elliptic curve encryption system that protects wallet ownership through Shor's algorithm. Currently, about 6.9 million BTC (approximately one-third of the total supply) face potential risks due to public keys being visible on-chain, including around 1 million early holdings by Satoshi Nakamoto; transactions generated after the Taproot upgrade in 2021 are also affected due to public key exposure.Ethereum has established a formal quantum resistance migration plan since 2018, with 4 full-time teams and over 10 independent development groups, and has launched a dedicated progress website at pq.ethereum.org. In contrast, Bitcoin currently lacks a unified response roadmap, and the existing BIP-360 proposal and BitMEX Research detection scheme have not received widespread support from core developers. Notable Bitcoin advocate Nic Carter pointed out that Bitcoin's response is "the worst," while Blockstream CEO Adam Back believes that current quantum systems are still in the laboratory stage, but he also agrees that optional upgrade solutions should be deployed in advance.Analysts point out that Bitcoin's anti-centralization governance culture makes coordinating large-scale security upgrades extremely difficult, and how to handle historical legacy issues such as Satoshi Nakamoto's holdings is particularly challenging. A related paper from Google warns that once quantum attacks become a reality, the window for response may have already closed.

Lido discloses the impact of the Kelp security incident: approximately 9% of EarnETH exposure affected, core staking assets are secure

Lido has released the latest developments regarding the Kelp security incident, stating that its Earn series vaults are working with the management to address the issues, which involve two major risk points: the rsETH exposure and the liquidity tension in the lending market. Lido emphasizes that the core staking protocol has not been affected, and both stETH and wstETH remain safe and stable.Currently, only the EarnETH vault has an approximately 9% TVL exposure to rsETH, and related deposits and withdrawals have been suspended by the management, awaiting a solution. Approximately $70 million in ETH has been recovered from the previous attack, and the subsequent asset recovery and loss distribution are still in progress. In response to liquidity pressure, the management has reduced leverage and optimized the position structure, significantly decreasing the wETH debt exposure. If losses ultimately occur, EarnETH will activate a $3 million "first loss protection mechanism" (funded by the DAO). As for other vaults, DVV and EarnUSD have not been affected and are operating normally; the GGV sub-vault is currently experiencing negative returns due to the combination of circular staking strategies and rising lending rates, but adjustments are ongoing. Withdrawal requests submitted by users will be processed based on valuations prior to the incident.
app_icon
ChainCatcher Building the Web3 world with innovations.