BTC $63,802.64 +0.12%
ETH $1,811.73 +2.11%
BNB $591.70 +0.76%
XRP $0.9908 +0.74%
SOL $75.23 +1.82%
TRX $0.3106 +0.25%
DOGE $0.0595 +0.77%
ADA $0.1550 +1.76%
BCH $208.21 +0.35%
LINK $9.21 +1.39%
HYPE $69.25 +3.45%
AAVE $108.36 -0.74%
SUI $0.7274 +0.95%
XLM $0.1372 -1.91%
ZEC $942.00 +1.24%
AAPL $350.07 -1.36%
AMZN $271.49 +2.86%
GOOGL $293.23 +3.30%
MSFT $523.74 +3.24%
META $626.19 +1.14%
NVDA $156.04 +0.65%
TSLA $387.05 +1.01%
SNDK $831.28 +7.01%
INTC $59.24 +8.08%
SPCX $143.91 +0.31%
MU $760.28 +7.41%
AMD $543.60 +5.77%
BTC $63,802.64 +0.12%
ETH $1,811.73 +2.11%
BNB $591.70 +0.76%
XRP $0.9908 +0.74%
SOL $75.23 +1.82%
TRX $0.3106 +0.25%
DOGE $0.0595 +0.77%
ADA $0.1550 +1.76%
BCH $208.21 +0.35%
LINK $9.21 +1.39%
HYPE $69.25 +3.45%
AAVE $108.36 -0.74%
SUI $0.7274 +0.95%
XLM $0.1372 -1.91%
ZEC $942.00 +1.24%
AAPL $350.07 -1.36%
AMZN $271.49 +2.86%
GOOGL $293.23 +3.30%
MSFT $523.74 +3.24%
META $626.19 +1.14%
NVDA $156.04 +0.65%
TSLA $387.05 +1.01%
SNDK $831.28 +7.01%
INTC $59.24 +8.08%
SPCX $143.91 +0.31%
MU $760.28 +7.41%
AMD $543.60 +5.77%

vulnerability

All
Article
Flash

first_img LUKSO email recovery system vulnerability led to approximately 300 accounts being hacked, resulting in 1.4 million LYX stolen

LUKSO stated that from the night of November 17 to 18, attackers exploited a security vulnerability in its email recovery system backend, gaining control of approximately 300 Universal Profile accounts and stealing around 1.4 million LYX. The attackers then transferred all LYX to the Ethereum network via a cross-chain bridge and exchanged it for about 50 ETH on decentralized exchanges like Uniswap, valued at approximately $95,000.LUKSO mentioned that the vulnerability allowed attackers to control the "recovery" Universal Profile of the recovery service itself, enabling them to add their own control keys to about 300 user accounts and subsequently transfer assets. LUKSO emphasized that its blockchain and the Universal Profile smart contracts themselves were not affected, and that private keys and mnemonic phrases were not leaked. Accounts that did not use email recovery were unaffected. The email recovery system has now been shut down and deactivated, while backups based on files and device keychains remain secure.LUKSO reminded affected users that simply revoking permissions is not enough; they must sequentially remove the attackers' control keys and the malicious "recovery-UP" controller. Once completed, users can retain their accounts, names, histories, and remaining assets. LUKSO stated that it is developing a compensation plan for affected users and will announce details in the coming weeks.

Coinkite CEO: About 0.17% of Coldcard users are affected by the firmware vulnerability

Coinkite CEO Rodolfo Novak stated that approximately 0.17% of Coldcard users were affected by the firmware vulnerability, but did not specify the number of users corresponding to that percentage. Coinkite has not released sales data and has not confirmed the number of affected users; the company previously stated that privacy design prevents it from verifying external loss estimates.Galaxy Research Director Alex Thorn mentioned that about 9,200 addresses were collectively robbed of 1,830 bitcoins, valued at approximately $116 million at the time. He also stated that among the 256 Coldcard victims who sought help from Galaxy, 245 had a total of 895 bitcoins across 2,585 addresses. Recently, Novak announced that he would step back from his role in the industry but did not specify whether he would resign as Coinkite CEO. His related comments sparked criticism from users, with some questioning his responsibility for the loss incident; Novak referred to some critics as "bots of competitors."The first report of theft incidents involving Coldcard was on July 30, and Coinkite is still preparing a technical review. A proposed class action lawsuit filed in September in Ontario names Coinkite, Novak, and co-founder Peter Gray as defendants, with the lawsuit application representing users who directly purchased specified models of Coldcard from Coinkite for personal use.

first_img Apache has a serious vulnerability, and the HTTP/2 service may be subject to remote code execution

A serious security vulnerability has been found in the open-source server software Apache HTTP Server. Attackers can exploit this vulnerability to corrupt server memory by crafting requests when they have access to the affected service, allowing them to execute code with the privileges of the web service process. The vulnerability is located in the HTTP/2 module, and attackers can trigger a concurrent synchronization flaw without authentication, leading to heap memory corruption. If successfully exploited, it allows code execution with the privileges of the Apache worker process and access to data that the process can read.The affected range includes Apache HTTP Server versions 2.4.55 to 2.4.70, as well as mod_h2 versions 2.0.8 to 2.0.42 used separately from GitHub. Red Hat stated that the risk involves servers that enable HTTP/2 through the Protocols directive, including H2 for encrypted connections and H2C for plaintext connections. Administrators need to check both global configurations and individual virtual host configurations; if a CDN or reverse proxy is deployed on the website frontend, it is also necessary to check whether the Apache origin server can be accessed directly via HTTP/2.Apache released HTTP Server 2.4.71 on November 11, 2026, and it is recommended that websites using Apache upgrade immediately. If an upgrade cannot be performed temporarily, HTTP/2 can be disabled as a temporary measure. The issue lies in the assign_headers() function of mod_http2. HTTP/2 allows multiple requests to be processed concurrently over the same connection, and the affected code has a synchronization flaw when handling shared resources, which may lead to heap memory corruption. This vulnerability was discovered by the Anthropic OSS Scanner open-source project and the Google Cloud vulnerability research team. Anthropic reported it to the Apache Foundation on October 26, and the Google Cloud team reported the same vulnerability on November 3.
app_icon
ChainCatcher Building the Web3 world with innovations.