BTC $63,987.66 -1.42%
ETH $1,798.62 -0.84%
BNB $589.22 -0.32%
XRP $0.9691 +1.60%
SOL $73.13 +2.66%
TRX $0.3074 +0.64%
DOGE $0.0594 +0.24%
ADA $0.1535 +0.22%
BCH $208.90 +0.63%
LINK $9.17 +0.62%
HYPE $68.27 +0.03%
AAVE $110.63 +3.16%
SUI $0.7247 +0.50%
XLM $0.1391 +1.41%
ZEC $926.80 +3.95%
AAPL $351.22 -0.20%
AMZN $258.08 +0.04%
GOOGL $280.33 -1.52%
MSFT $506.30 -2.36%
META $621.04 -0.87%
NVDA $153.99 -1.04%
TSLA $380.33 +0.77%
SNDK $798.52 -1.83%
INTC $54.37 -1.98%
SPCX $141.71 +1.42%
MU $703.53 -2.43%
AMD $492.76 -2.27%
BTC $63,987.66 -1.42%
ETH $1,798.62 -0.84%
BNB $589.22 -0.32%
XRP $0.9691 +1.60%
SOL $73.13 +2.66%
TRX $0.3074 +0.64%
DOGE $0.0594 +0.24%
ADA $0.1535 +0.22%
BCH $208.90 +0.63%
LINK $9.17 +0.62%
HYPE $68.27 +0.03%
AAVE $110.63 +3.16%
SUI $0.7247 +0.50%
XLM $0.1391 +1.41%
ZEC $926.80 +3.95%
AAPL $351.22 -0.20%
AMZN $258.08 +0.04%
GOOGL $280.33 -1.52%
MSFT $506.30 -2.36%
META $621.04 -0.87%
NVDA $153.99 -1.04%
TSLA $380.33 +0.77%
SNDK $798.52 -1.83%
INTC $54.37 -1.98%
SPCX $141.71 +1.42%
MU $703.53 -2.43%
AMD $492.76 -2.27%

sati

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.

first_img Knowledge base application Notion reports less than 1% workspace AI conversation leaks

The knowledge management application Notion has released an announcement acknowledging that some users' AI chat records have been leaked. The company stated that the affected workspaces account for less than 1% of all workspaces and is currently notifying the affected users. If users have provided their account, password, or credentials to the AI, Notion recommends treating them as compromised, immediately checking the login records of the relevant accounts, and changing passwords or credentials.The source of this incident is a hacker attack on the service provider Fireworks. Notion uses Fireworks AI to process data for a feature called Insights, which helps workspace administrators understand how team members are using AI. To generate this analytical data, Notion sends the saved AI conversation content to Fireworks for processing. Fireworks has also served as the inference service provider for some open-weight models in Notion's products.Notion stated that the potentially leaked data mainly consists of user chat records, including the chat content input by users and the replies given by the AI. The announcement explained that some users may have sent their account, password, or various credentials to the model while using AI. Notion advises the relevant users to immediately change these passwords or credentials and check for any unusual activity in their account login records.

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 Binance: The compensation ratio for stolen assets has increased to 90%, and withdrawals are still planned to resume on Sunday

Binance released a security incident update stating that the company had previously reserved over $6.34 billion of company funds to cover the stolen losses, with the coverage ratio at that time being approximately 80%, which has now increased to 90%. BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC have achieved 100% coverage, while the remaining related tokens will continue to be purchased through market and over-the-counter channels until the coverage ratio for all tokens reaches 100%. Binance stated that the financial impact of the stolen funds will be borne by the platform, not the users.The replenished funds come from a partial drawdown of the user security asset fund SAFU, a portion of the contract insurance fund, and Binance's company funds. The partial drawdown of SAFU is expected to occur within the next 24 hours. The remaining 10% consists of assets outside the aforementioned ten tokens with lower liquidity, and the time required for purchase may be longer.Binance completed a new reserve proof snapshot on October 31 at 00:00 (UTC) and updated it on the reserve proof page. The complete zero-knowledge proof is expected to take 40 to 50 hours to generate, approximately by November 3 (UTC). Withdrawal services will continue to progress according to the previous schedule, with plans to reopen on Sunday, November 1.Binance introduced that SAFU was established in July 2018 and is held and managed by Nest Clearing and Custody Limited, regulated by the Abu Dhabi Global Market Financial Services Regulatory Authority. The company commits to replenishing the scale of SAFU to approximately $1 billion and clarifies that the partial drawdown of SAFU is for purchasing the remaining 10% of assets. After withdrawing the balance exceeding the stipulated level, the contract insurance fund remains above the coverage level required by the existing risk management framework; if the balance falls below the requirement, Binance will make up the difference with company funds.
app_icon
ChainCatcher Building the Web3 world with innovations.