BTC $83,486.48 -0.99%
ETH $2,687.05 +0.18%
BNB $761.44 -1.93%
XRP $1.49 -1.27%
SOL $118.76 -2.59%
TRX $0.3357 +0.73%
DOGE $0.0936 -2.72%
ADA $0.2465 -2.90%
BCH $310.39 -6.46%
LINK $15.37 +9.88%
HYPE $87.44 -4.64%
AAVE $148.38 -3.88%
SUI $1.15 -7.63%
XLM $0.2277 +5.85%
ZEC $1,485.06 -6.63%
AAPL $338.79 -0.27%
AMZN $246.58 -0.97%
GOOGL $342.65 -0.20%
MSFT $509.87 -1.33%
META $718.66 -4.14%
NVDA $229.64 +2.36%
TSLA $358.62 -3.77%
SNDK $1,718.54 -3.05%
INTC $116.39 -5.57%
SPCX $146.27 -2.12%
MU $1,057.34 -3.00%
AMD $611.95 -2.95%
BTC $83,486.48 -0.99%
ETH $2,687.05 +0.18%
BNB $761.44 -1.93%
XRP $1.49 -1.27%
SOL $118.76 -2.59%
TRX $0.3357 +0.73%
DOGE $0.0936 -2.72%
ADA $0.2465 -2.90%
BCH $310.39 -6.46%
LINK $15.37 +9.88%
HYPE $87.44 -4.64%
AAVE $148.38 -3.88%
SUI $1.15 -7.63%
XLM $0.2277 +5.85%
ZEC $1,485.06 -6.63%
AAPL $338.79 -0.27%
AMZN $246.58 -0.97%
GOOGL $342.65 -0.20%
MSFT $509.87 -1.33%
META $718.66 -4.14%
NVDA $229.64 +2.36%
TSLA $358.62 -3.77%
SNDK $1,718.54 -3.05%
INTC $116.39 -5.57%
SPCX $146.27 -2.12%
MU $1,057.34 -3.00%
AMD $611.95 -2.95%

user

All
Article
Flash

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.

first_img MEXC user: API not revoked after account was hacked, approximately 340,000 USD was transferred away

A MEXC user posted on X that their account was compromised after someone reset the security items. MEXC has confirmed the account was hacked, frozen the account, and assisted in recovery, but did not revoke the API left by the attacker. From 04:12 to 04:25 on September 27, 2026 (Beijing time), the account transferred out 322,110 USDT and 9,133,999 ONE, totaling approximately $340,000, about 27 minutes after the 24-hour transfer limit was lifted.The user stated that at 03:10 on September 25, they received a reset security item email that was not submitted by them, and about 10 minutes later, the request was approved. Subsequently, the account was logged in from an IP in Jakarta, Indonesia, bound to Google verification, and at 05:05, an API was created, approximately 83 seconds after logging in. At 10:55 that day, MEXC froze the account after a risk review and reverted to the original email. Customer service responded in writing that the review materials met the requirements, so the binding change was approved, and after the risk review, the account was urgently frozen and reverted to the initial email. The user changed their password and Google verification on September 26 but stated that the API was not revoked, and there were no related records in the security operation history.The user also claimed that there were no new login records in the login history when the assets were transferred out. They have submitted a formal claim to MEXC and attempted to report to the police, with the ticket number M2026092712031, requesting the platform to preserve logs, provide a written explanation of the review and API situation, and return the aforementioned assets. MEXC customer service stated that it is currently unable to confirm whether these transfers were initiated via APP, WEB, or API, and the issue has been forwarded to the relevant department.

DyorSwap: The previously identified "GIWA Mainnet" is actually a fake chain built by scammers, and compensation for affected users will be provided through treasury funds

DyorSwap officially announced that the so-called "GIWA Mainnet" identified by the team earlier is actually a fake chain set up by scammers. This fake network used the correct GIWA chain ID (9134), making it appear legitimate during the initial verification phase. The team also identified several suspicious messages and individuals within the related community that may be connected to this incident. The announcement stated that significant losses have occurred due to this fraudulent cross-chain bridge.DyorSwap stated that it is taking three immediate actions: first, contacting a professional security team to conduct further on-chain tracking and investigate the involved addresses, transactions, and fund flows; second, preserving all relevant evidence, including chat records, RPC information, cross-chain bridge addresses, and on-chain transactions; third, preparing to use treasury funds to compensate affected users, with eligibility criteria, loss verification processes, compensation scope, and detailed plans to be announced after the investigation and verification processes are completed.DyorSwap emphasized that until further notice, users should not use any unofficial GIWA mainnet RPCs, cross-chain bridges, or contracts, and should not send funds to any related addresses. The official team deeply apologizes to every affected user in this incident and states that subsequent updates will be released as soon as possible.

DyorSwap: The previously identified "GIWA Mainnet" is actually a fake chain built by scammers, and compensation for affected users will be provided through national treasury funds

DyorSwap officially announced that the so-called "GIWA mainnet" previously identified by the team is actually a fake chain set up by scammers. This fake network used the correct GIWA chain ID (9134), making it appear legitimate during the initial verification phase. The team also identified several suspicious messages and individuals within the related community that may be connected to this incident. The announcement stated that significant losses have occurred due to this fraudulent cross-chain bridge.DyorSwap stated that it is taking three immediate actions: first, contacting a professional security team to conduct further on-chain tracking and investigate the involved addresses, transactions, and fund flows; second, preserving all relevant evidence, including chat records, RPC information, cross-chain bridge addresses, and on-chain transactions; third, preparing to use treasury funds to compensate affected users, with eligibility criteria, loss verification processes, compensation scope, and detailed plans to be announced after the investigation and verification processes are completed.DyorSwap emphasized that until further notice, users should not use any unofficial GIWA mainnet RPCs, cross-chain bridges, or contracts, and should not send funds to any related addresses. The official team deeply apologizes to every affected user in this incident and states that subsequent updates will be released as soon as possible.

Magic Eden: Current open orders are not affected by this vulnerability; users in the EVM market from February to October 2024 need to revoke related contract authorizations

Magic Eden announced that the vulnerability occurred in the NFT trading protocol Payment Processor V2 maintained by Limit Break. Magic Eden adopted this protocol for EVM network transaction settlements in 2024 but stopped using V2 in October 2024 and will completely shut down the EVM market in the first quarter of 2026. Therefore, NFTs currently listed on Magic Eden are not affected by this vulnerability.NFTs listed through its EVM market between February and October 2024 may be affected, while listings after October 2024 are generally not impacted. The platform is contacting the protocol owner and maintainer Limit Break to explore other risk mitigation measures, including pausing protocol transfers, and will continue to investigate the actual scope of the impact.Magic Eden reminds users who have listed or traded NFTs on its EVM market to revoke relevant contract authorizations on the Ethereum, Polygon, and Base networks. Users can filter the address through revoke.cash and revoke all authorizations marked as "approved for all" for NFTs. Magic Eden emphasizes that revoking authorization cannot recover assets that have already been transferred.Yuga Labs' Vice President of Blockchain Quit stated today that at 9 AM Eastern Time, attackers exploited the Payment Processor V2 vulnerability to steal a large number of NFTs. After contacting the LimitBreak team, the latter quickly paused the similarly affected Payment Processor V3. However, V2 could not be paused, and V3 on ApeChain is also temporarily unable to be paused. Therefore, the team implemented a white-hat operation, successfully transferring and protecting 23,155 NFTs valued at over 5.7 million dollars.

first_img Meta's Muse AI assistant reads users' private information and falsely reports the method of access

Meta's personal AI assistant Muse has been accused of reading users' private iMessages without permission and providing false explanations about how it accesses this information. Technology columnist Jason Aten installed the assistant on his iPhone and Mac when Muse launched on September 8 and explicitly refused to grant it access to personal data such as information and calendars.A few days later, Muse sent Aten a notification suggesting he write a column about the new iPhone that he had just discussed with his podcast partner, also mentioning a deadline reminder from the editor. Aten asked Muse how it knew this, and it replied that the Mac application only forwards notification previews and does not involve the content of messages. In reality, Muse had synchronized over 187,000 records from the local private information database on the Mac, an operation that requires full disk access permissions on macOS.David Singleton, head of Meta's superintelligent lab, responded on Threads that this feature requires users to actively choose to opt-in. Aten denied ever turning on that switch and stated that Meta had not answered related questions. Amazon has banned Muse from shopping on its site, stating that the assistant did not indicate its AI identity while browsing and seemed capable of capturing and storing user credentials. Since its launch, Muse has been downloaded over 2.5 million times, with its promotion emphasizing user control over access.
app_icon
ChainCatcher Building the Web3 world with innovations.