News linked to this event type.
Odaily reports: BlockSec has posted that its system detected an attack on the TENDRIL/USDT liquidity pool on BNB Chain several hours ago, causing losses of approximately $556,000. The root cause of the attack lies in a security flaw in the token's sell tax logic: after the attacker used flash loan funds to buy TENDRIL, by triggering the 30% sell tax and the tax-processing contract (_poolControl), the tax tokens were sold, and the contract further called controlburn() and sync(), causing the TENDRIL reserve recorded by the liquidity pool to drop to nearly zero, while the seller's remaining tokens only entered the pool afterward, allowing the attacker to extract nearly all remaining USDT in the pool through subsequent swaps.Specifically, the attacker used approximately 30.64 million USDT in flash loan funds to manipulate the pool's price and reserves, ultimately extracting approximately 4.42 million USDT from the liquidity pool, repaying the flash loan within the same transaction, and transferring approximately $308,960 in profit.
Loopscale reported that it has been continuously targeted by sophisticated attackers over the past week, with the protocol API receiving over 30,000 malicious requests daily. After the security systems detected a significant escalation in attack activity, the team suspended the protocol to contain the impact. The attacks primarily targeted the SOL and USDC Genesis Vaults, and all affected vaults have been fully replenished. No user deposits were compromised.
According to Reuters, the U.S. Federal Reserve (Fed) and the Office of the Comptroller of the Currency (OCC) have begun contacting banks to inquire whether unusual activity or service disruptions have occurred, investigating potential system security risks exposed following Binance's recent $6.3 billion hacking attack. Sources say multiple U.S. banks are reviewing their cybersecurity systems, and one large bank has already begun drafting an internal report to assess whether upgrades to its security defenses are necessary.
GoPlus Security has issued an alert stating that Android has released a critical security bulletin regarding severe vulnerabilities affecting versions including Android 14, 15, 16, 16 QPR2, and 17. Users should check the security patch level on the system version page in their device settings and install system updates provided by their manufacturer. The bulletin notes that the November 1, 2026 patch only resolves CVE-2026-58868; upgrading to November 5, 2026, or a newer version is required to address all vulnerabilities listed in this month's advisory.
According to Moneycontrol, Ethereum co-founder Vitalik Buterin stated in an exclusive interview that survival will be the top priority for cryptocurrency exchanges over the next two years, rather than competing for market advantage. With frequent hacking incidents across the industry, if security issues persist, regulators may intervene, requiring companies to adopt more prudent operational measures and assume stricter security responsibilities. Buterin also acknowledged the continued growth of India's developer ecosystem.
According to CertiK's analysis, the TENDRIL sell hook causes the trading pair reserves to be reset before the remaining sold tokens are settled, resulting in approximately $555,000 in net losses from the attack.
TenArmor Alert detected a suspicious attack involving the TENDRIL/USDT pool on BSC, with estimated losses of approximately $309,000.
Binance and Polymarket have proposed implementing a hard fork on the Polygon network to recover approximately 70.49 million stolen POL tokens, valued at about $6.8 million. Of these, Polymarket-related addresses account for 23.86 million tokens, while Binance-related addresses account for 46.63 million tokens. The tokens are planned to be transferred from 5 attacker-controlled addresses to verified recovery wallets designated by the two platforms, without changing the total POL supply.Polygon block producers have already blocked transactions from the affected addresses, but this restriction is only a temporary measure and cannot return the funds to their owners. The plan requires governance approval and must first be tested on the Polygon Amoy testnet, with discussion expected on November 5. The mainnet hard fork date has not yet been determined. (Cointelegraph)
Changpeng Zhao(CZ)表示,AI 正推动网络攻击提速,快于金融机构强化防御的速度。他称,过去加密行业每周或每月发生重大攻击,如今一天内可能出现多起,攻击者利用 AI 自动化侦察、钓鱼和漏洞发现。CZ 在 10 月 29 日币安遭遇 63 亿美元攻击后首次公开发声,称此类攻击的影响已超出数字资产领域,并涉及全球金融与国家安全。美国联邦调查局将此次攻击归因于朝鲜黑客;CZ 表示,行业欢迎美国和中国提供支持。CZ 支持建立加密行业安全联盟,以共享审计发现、交流攻击经验并协调冻结资产。他称,币安及整个行业对安全投入不足,并表示币安承担全部损失、及时确认用户资金安全,有助于遏制更广泛的市场冲击。(Bitcoin.com News)
According to Binance's official announcement, Binance released Security Incident Recovery Update #8 on November 5, gradually resuming withdrawals for a batch of assets starting from 2026-11-05 04:00 (UTC), while deposit services remain open. The update affects networks such as ETH, BSC, BASE, TRX, MATIC, and SUI, and covers assets including UNI, AAVE, PAXG, VIRTUAL, WLFI, ASTER, AERO, SUN, and SUI. Binance stated that priority will be assigned based on user demand over the past week, with phased reopening scheduled after completing security and readiness checks. Users may encounter processing delays during the rollout.
Odaily reports: Binance has released Security Incident Recovery Progress Update #8, announcing that it will begin opening withdrawals for some assets in batches starting at 12:00 Beijing time on November 5, 2026. The assets involved include UNI, AAVE, PAXG, VIRTUAL, MORPHO and others on the ETH network; ASTER, PROM, UNI, 1MBABYDOGE, FIL and others on the BSC network; AERO, VIRTUAL, MORPHO, and AVNT on the BASE network; JST, SUN, and BTTC on the TRX network; GNS on the MATIC network; and MMT on the SUI network. The relevant withdrawal services will be gradually restored in batches after security checks are completed, while deposit services will remain normal.
The Polkadot incident review shows that the October XCM exploit caused a treasury loss of approximately $1.381 million. The related fix was completed in June but was not deployed to the affected production version.
Indian CERT-In stated that the CRAFTY FALCON threat campaign is escalating, with attackers stealing cryptocurrency wallet keys and draining funds.
Odaily report: India's Computer Emergency Response Team (CERT-In) on Wednesday designated AI-assisted attackers targeting financial institutions as "CRAFTY FALCON," updating a warning it first issued last October. The latest advisory explicitly lists cryptocurrency exchanges as affected targets, stating that the attack campaign continues to escalate.CERT-In said attackers exploited vulnerable applications and exposed testing environments, using shared credentials and access tokens to gain entry into production systems and deploy malicious files against cloud infrastructure. AI tools were used to rapidly generate and refine attack scripts, with some attacks scheduled on weekends and holidays to delay detection.The agency said attackers had verified unauthorized transfers through small test transactions and stole cryptocurrency wallet keys and moved wallet funds. CERT-In did not disclose the names of affected exchanges or the amount of losses, and recommended that relevant enterprises strengthen security monitoring around the clock, increase staffing on weekends and holidays, and lower alert thresholds. (Cointelegraph)
According to Cointelegraph, BitMart cryptocurrency exchange founder Sheldon Xia said on Wednesday that the company's security team is currently severely understaffed following the confirmation of a new cyberattack. Xia posted on X that threats against current employees and alleged retaliatory actions by former staff have made it more difficult to retain technical personnel. He described the amount involved in Monday's attack as relatively minor but declined to disclose specific figures.
According to Decrypt, Bitcoin developer Matt Corallo stated on the MARA Foundation TV show that he estimates an 80% probability that the next soft fork on the Bitcoin network will be the "mass consensus cleanup" (BIP-54). Proposed in 2019, this proposal aims to fix four long-standing vulnerabilities in Bitcoin's consensus rules, including flaws in the difficulty adjustment mechanism and denial-of-service attack vectors among miners.
The bank stated that the attackers did not gain access through Fortuneo, confirmed only the magnitude of the reported stolen funds, and noted that final losses are still under assessment.
Sekoia discovered an attack campaign targeting iOS and Android devices, with attackers leveraging compromised websites and analytics scripts to deploy exploit chains.
Privacy Cash posted on X platform stating that in light of the recent hack on Binance, it has decided to temporarily suspend deposit services. During the suspension period, the team will continue to strengthen its wallet screening system.Additionally, during the suspension period, withdrawal services will remain open, and the specific resumption time will be announced separately.
Open-source Bitcoin payment processing tool BTCPay Server received multiple reports on November 1 alleging unauthorized theft of funds from Bitcoin and Litecoin hot wallets on its platform. On November 2, the project team released an investigation update confirming that the attack targeted servers running BTCPay Server version 2.4.1 or earlier. Attackers exploited a vulnerability that had been fixed in version 2.4.2 on August 7, using various methods to gain server administrator privileges and drain hot wallet funds. BTCPay Server founder Nicolas Dorier confirmed that only servers running versions prior to 2.4.2, particularly version 2.4.1, were affected; no credible loss reports have emerged from users running the latest version 2.4.7. Some affected service providers, including LunaNode, have automatically shut down vulnerable legacy instances. The official recommendation is for users still on 2.4.1 or earlier to immediately transfer any remaining funds from old hot wallets to new wallets created with a fresh mnemonic phrase, take the old servers offline and preserve relevant logs, then install the latest version on a brand-new virtual machine and connect the new wallet. Under no circumstances should the old server be restored in its entirety to a new machine. Updating the software version alone is insufficient to eliminate the risk, as attackers may have already established persistent access on the old servers. Funds stored outside the server, such as those in hardware wallets, were not affected by this incident. The vulnerability is related to one fixed in August of this year, when attackers manipulated nodes by obtaining LND administrative credentials. As of now, the vulnerability has not been assigned a CVE number and is not listed in CISA's Known Exploited Vulnerabilities catalog.