BTC $64,897.94 -0.17%
ETH $1,826.20 +0.01%
BNB $593.32 +0.33%
XRP $0.9643 +0.26%
SOL $72.83 +1.39%
TRX $0.3049 +0.34%
DOGE $0.0591 +0.22%
ADA $0.1540 -0.19%
BCH $208.94 +0.05%
LINK $9.18 -0.33%
HYPE $70.18 +5.76%
AAVE $112.08 +2.26%
SUI $0.7265 -0.18%
XLM $0.1392 -0.89%
ZEC $917.98 +2.64%
AAPL $353.19 -1.15%
AMZN $258.63 -2.51%
GOOGL $284.72 -3.47%
MSFT $517.84 -1.04%
META $625.16 -1.86%
NVDA $157.90 -3.06%
TSLA $380.10 -1.93%
SNDK $819.12 -4.29%
INTC $54.82 -5.79%
SPCX $138.10 -1.74%
MU $725.73 -4.25%
AMD $513.21 -1.75%
BTC $64,897.94 -0.17%
ETH $1,826.20 +0.01%
BNB $593.32 +0.33%
XRP $0.9643 +0.26%
SOL $72.83 +1.39%
TRX $0.3049 +0.34%
DOGE $0.0591 +0.22%
ADA $0.1540 -0.19%
BCH $208.94 +0.05%
LINK $9.18 -0.33%
HYPE $70.18 +5.76%
AAVE $112.08 +2.26%
SUI $0.7265 -0.18%
XLM $0.1392 -0.89%
ZEC $917.98 +2.64%
AAPL $353.19 -1.15%
AMZN $258.63 -2.51%
GOOGL $284.72 -3.47%
MSFT $517.84 -1.04%
META $625.16 -1.86%
NVDA $157.90 -3.06%
TSLA $380.10 -1.93%
SNDK $819.12 -4.29%
INTC $54.82 -5.79%
SPCX $138.10 -1.74%
MU $725.73 -4.25%
AMD $513.21 -1.75%

origin

All
Article
Flash

first_img Users claim that Aster misappropriated keys and transferred 4.56 million USD, demanding compensation for the original assets

User furongfei (@fuhuahuai) posted on November 16 that an abnormal transfer occurred in their account on the decentralized perpetual trading platform Aster in the early morning of November 13, 2026, Beijing time, resulting in a total loss of 4.56 million USD. According to the UTC times listed by the user, on November 12, 2026, at 16:22, someone registered a new account using their web proxy key, and from 16:24 to 17:08, the system executed 7 consecutive transfers to other users based on that key's signature, transferring 4,564,675.50 USDT to the new account. During the same period, 33 BTC in the account were transferred between contracts and spot 9 times, and from 16:49 to 16:59, they were split into 17 market sell orders.The user stated that the Aster signature records show that the signature address for the aforementioned 7 transfers was the proxy key 0x647E, and none of the transfers came from their main wallet. They cited the docking records stating that Aster's CEO's preliminary conclusion was that the proxy key was exposed, not the private key of the address itself; it was later confirmed in writing that this key was a temporary private key created locally in the browser after the user clicked to enable trading and completed wallet authorization, named aster-desktop, and was not the user's wallet private key. The user also mentioned that according to Aster's documentation, transferring to other users is classified as a withdrawal-level operation, and this key does not have withdrawal permissions, and the account had enabled a user privacy mode that prohibits internal transfers, yet the 7 transfers were still allowed by the system.The user claimed that the new account subsequently withdrew 4,564,674.38 USDT in 10 transactions. After the funds were cross-chain, 1,000 ETH entered Tornado Cash, and 768.1 ETH along with 993,999.67 USDT entered NEAR Intents confidential exchange. The user requested Aster to provide a written processing timeline, stating that they would not wait for recovery and would compensate according to the original assets, with the listed scope including 33 BTC, 2,200,134.21 USDT, and forced liquidation fees, and stated that any subsequently recovered funds would belong to the platform, while also requesting an explanation of the basis for the release and preservation of server logs. Reports indicate that Aster's relevant account responded under the post that an investigation team has been established.

SignalPlus: The network attack originated from a third-party Telegram account being hacked, resulting in a loss of less than $82,000, and full compensation will be provided

The cryptocurrency derivatives trading tool platform SignalPlus announced that it was attacked in the early hours of November 4, originating from a third-party Telegram account that was hacked, affecting a small number of accounts that had not enabled IP whitelisting.The team stated that they quickly identified and controlled the intrusion. As a precautionary measure, they have revoked all associated API keys with their centralized trading platform partners and temporarily suspended terminal services. The official statement indicated that the total loss was less than $82,000, and affected users will receive full compensation. They expect to fully restore services in the coming days, with subsequent updates and operational guidelines to be released through official channels.This evening, Binance also issued a statement indicating that it has taken precautionary measures regarding the potential security issues reported by the third-party platform SignalPlus, actively revoking all API keys associated with SignalPlus.Binance emphasized that its own system was not affected and that user funds are secure. Binance reminded SignalPlus users to log directly into their Binance accounts to check their positions and open orders, and not to rebind API keys until the issues with SignalPlus are completely resolved. They also advised to always enable IP whitelisting.

first_img NEAR Intents released a post-mortem report, revealing that the $3.8 million vulnerability originated from a deposit notification flaw

The cross-chain exchange protocol NEAR Intents released a post-mortem report attributing a $3.8 million vulnerability to a flaw in the deposit notification feature. The protocol deploys a public settlement contract on NEAR that maintains an internal ledger of deposited tokens, while withdrawals transfer tokens out via a cross-chain bridge. The report was published by NEAR Intents General Manager Alex Shevchenko on October 16, stating that the attacker withdrew $3.8 million before the protocol was shut down on October 1 and returned all funds within 36 hours of detection, with all affected users fully compensated.The report indicates that the feature notifies third-party contracts when tokens are deposited. The attacker created a contract that intentionally caused the notification to fail, allowing the token contract to refund the deposit while NEAR Intents retained the corresponding ledger credit. Through 23 failed deposit transactions, the attacker accumulated $3.8 million in unsupported balance, referred to in the report as ghost funds, and subsequently withdrew real tokens based on this and transferred them to other chains via the Omni infrastructure. Shevchenko stated that this was a vulnerability in the NEAR Intents contract, not in the Omni infrastructure.Withdrawals occurred between September 29 and October 1. The settlement contract was paused and reopened on October 1, with affected routes gradually restored, and contract-side deposits resumed on October 2. The report noted that the vulnerability went undetected because monitoring only compared the original chain assets with the total balance of NEAR side tokens, without comparing the total internal user balances with the actual tokens held by the contract; the team has since added this check and will automatically pause the contract when there is a balance inconsistency. The fix for the October vulnerability was deployed on October 2, but another serious vulnerability report regarding the same feature prompted its complete removal on October 7, with the relevant researcher receiving a $300,000 reward.

Bitget CEO live-streamed a response to the platform's first security incident in eight years: the attack originated from a vulnerability in a third-party security product, and the losses will be covered by the user protection fund

In today's community live broadcast, Bitget CEO Gracy responded to recent security incidents and the platform's financial status. She candidly stated that this is the first security incident encountered since Bitget was established 8 years ago. After a complete trace, it was found that hackers exploited vulnerabilities in third-party security products to steal internal network access credentials, forged withdrawal commands to the wallet system, and deceived the wallet into executing abnormal transfers that bypassed risk checks. Gracy emphasized that no private keys were leaked, and cold wallets were unaffected; specific technical details will be disclosed in the formally released security report.Gracy pointed out that the verified losses from this incident are within the coverage of the protection fund, and user funds are not affected. The platform's own funds exceed $1.4 billion, which includes approximately $464 million in the user protection fund. The platform will continue to uphold the security commitments made when the protection fund was established in 2022, planning to replenish the fund to the baseline of $300 million within a week."The protection fund is not just a slogan, but an important mechanism that provides tangible security for users in the event of extreme security incidents," Gracy stated. In the face of sudden security challenges, the platform's comprehensive strength and its ability to take responsibility are important criteria for measuring its risk response capability and long-term credibility. Bitget will continue to uphold its long-term commitment to prioritize user interests.
app_icon
ChainCatcher Building the Web3 world with innovations.