ImportantPANews
1inch has blocked Binance exploit-related addresses across all its products, stolen 1INCH cannot be frozen
1inch has implemented emergency risk control measures in response to the Binance exploit incident. <p>The 1inch risk management team, in collaboration with security organizations including ZeroShadow, SEAL 911, and TRM Labs, completed relevant remediation within one hour after the incident occurred, fully blocking all addresses associated with the exploit across the 1inch dApp, 1inch Wallet, and 1inch API. The team will continue to update newly identified high-risk addresses going forward, and share the list of risky addresses with its resolvers and all partner integrators.</p><p>Part of the stolen assets consist of 1INCH tokens. As 1INCH is a standard ERC-20 token that does not natively support freezing or blacklist control functionalities, no entity is able to execute freezing operations on the stolen 1INCH tokens.</p><p>1inch has proactively reached out to the Binance team to offer relevant technical support, and will fully cooperate with the Binance platform and relevant law enforcement agencies to conduct full-chain tracking of the stolen assets, and advance the recovery of stolen assets to the greatest possible extent.</p>
- #Hack
More flash news
View allBinance Discloses Details of Security Incident: Compromised Employee Computer Served as Attack Entry Point, User Funds Remain Secure
In response to the recent security incident, Binance has officially released relevant technical details and current handling progress. <p>The initial entry point of this attack was the compromise of an employee's computer. The attacker did not directly obtain engineer privileges to complete fund transfers. The attacker employed multi-stage complex infiltration tactics, and this security incident was not caused by the actions of a single individual. The ongoing investigation has not yet attributed responsibility for the incident to any internal personnel.</p><p>At this stage, the platform has found no evidence of wallet private key leaks, and all user funds remain in a secure state. All stolen losses arising from this incident will be fully covered by Binance's SAFU Fund and the company's own capital, and no losses will be borne by regular users.</p><p>Approximately $3 billion of affected related on-chain assets have been successfully frozen. The platform is concurrently cooperating with law enforcement agencies and blockchain intelligence organizations to conduct follow-up investigations into the attackers. Deposit services on the platform remain fully operational at present. Withdrawals have been temporarily suspended as a precautionary security measure, and are expected to resume within 48 hours.</p>
OneKey Founder: IBIT May Have Become a Potential Target of North Korean Hackers, Its Highly Centralized BTC Custody Risks Cannot Be Ignored
OneKey founder Yishi analyzed that he suspects IBIT is already on North Korea's list of potential targets. During the Bybit hacking incident in February 2025, attackers infiltrated the Safe{Wallet} developer's Mac computer through a malicious project disguised as a legitimate Docker tool, gaining 17 days of access — sufficient to manipulate the transaction interface used by signers, tricking them into authorizing the theft of $1.5 billion without their knowledge. Yishi noted that TRM Labs is highly confident that the Binance incident is linked to TraderTraitor, a group also associated with the Bybit and DMM Bitcoin heists; Binance stated there is no evidence of private key leaks, while TRM believes the attackers may have gained control of the signing infrastructure.
XRP Ledger Developers Propose Four Fixes to Tighten Restricted Token Holding Rules
XRP Ledger developers have put forward four fixes designed to close loopholes that allow restricted tokens to enter accounts without prior approval from the token issuer. These changes have been consolidated into the network upgrade fixCleanup3_5_0, which has not yet been activated on the mainnet. Some restricted tokens on the XRP Ledger require explicit approval from the issuer before an account is permitted to hold them, but developers have identified several methods that bypass this approval requirement. The fixes mandate that both tokens in an Automated Market Maker (AMM) pool must be approved before a user can purchase assets from the pool, and resolve the issue where approval checks were only triggered on zero-balance trust lines, allowing trust lines that already hold tokens to continue receiving additional tokens. The XRP Ledger Foundation stated that this is a routine protocol hardening measure, not a security incident, and no user impacts have been reported to date.
Strategy eyes more Bitcoin buys as Saylor touts $30B credit capacity
Michael Saylor says Strategy could create up to $30 billion in digital credit without new common-stock fundraising or further Bitcoin price gains, as the company plans more BTC purchases.
BreakingNorth Korea linked to $6.3B Binance hack by crypto investigators
TRM Labs says it has high confidence in the attribution, while ZachXBT identified stolen funds from the Binance and Bitget hacks converging at the same address.