BTC $64,629.98 -0.00%
ETH $1,830.16 +0.88%
BNB $593.08 +0.11%
XRP $0.9610 +0.47%
SOL $72.84 +2.25%
TRX $0.3062 +1.24%
DOGE $0.0590 +0.18%
ADA $0.1535 +0.66%
BCH $208.77 +0.25%
LINK $9.18 +0.35%
HYPE $69.78 +5.06%
AAVE $112.83 +2.65%
SUI $0.7242 +0.33%
XLM $0.1378 -0.68%
ZEC $922.25 +3.79%
AAPL $352.90 -1.22%
AMZN $257.64 -2.23%
GOOGL $283.98 -3.14%
MSFT $517.58 -1.02%
META $622.99 -1.72%
NVDA $157.68 -2.27%
TSLA $379.02 -1.61%
SNDK $814.69 -3.24%
INTC $54.66 -4.77%
SPCX $137.93 -1.73%
MU $723.80 -3.25%
AMD $510.64 -1.02%
BTC $64,629.98 -0.00%
ETH $1,830.16 +0.88%
BNB $593.08 +0.11%
XRP $0.9610 +0.47%
SOL $72.84 +2.25%
TRX $0.3062 +1.24%
DOGE $0.0590 +0.18%
ADA $0.1535 +0.66%
BCH $208.77 +0.25%
LINK $9.18 +0.35%
HYPE $69.78 +5.06%
AAVE $112.83 +2.65%
SUI $0.7242 +0.33%
XLM $0.1378 -0.68%
ZEC $922.25 +3.79%
AAPL $352.90 -1.22%
AMZN $257.64 -2.23%
GOOGL $283.98 -3.14%
MSFT $517.58 -1.02%
META $622.99 -1.72%
NVDA $157.68 -2.27%
TSLA $379.02 -1.61%
SNDK $814.69 -3.24%
INTC $54.66 -4.77%
SPCX $137.93 -1.73%
MU $723.80 -3.25%
AMD $510.64 -1.02%

dent

All
Article
Flash

first_img Cursor reviews the malicious expansion incident, approximately 5,000 people downloaded

AI programming tool Cursor released a report on the malicious Claude Code extension incident on October 29. The extension was listed in the extension market with the author as Anthropic, leading some developers to mistakenly believe that the Anthropic developer account had been compromised. However, the malicious version was actually published to the extension market cache by attackers impersonating Cursor. Cursor's investigation revealed that the malicious extension was available for 11 hours, during which approximately 5,000 developers downloaded this version.Cursor stated that the attackers first obtained an access key sent by the company to Fireworks AI and used it to copy data from a shared read-only bucket. The bucket contained a small amount of historical coding agent records from Cursor, mostly from 2025, with privacy mode off and allowed for model training sessions. These sessions contained unsanitized data, including sensitive credentials that Cursor directly sent to the model during regular use of the AI IDE. The internal key itself was not used for the extension market; the attackers used it to access Cursor's internal systems and obtain more credentials, including keys that could control the extension market system, and subsequently published the tampered Claude Code to the extension market cache.The tampered Claude Code extension would collect device and user information and attempt to write an SSH public key controlled by the attackers, enable SSH services, establish reverse tunnels, and maintain persistence through startup items. Due to issues in the code written by the attackers, most affected devices failed to complete SSH remote access, but the malicious extension could still leave behind public keys, persistence files, and send device information. Cursor recommends that affected developers reinstall their systems and rotate all credentials, as simply uninstalling the malicious extension will not remove independently running persistence scripts.

Web3Auth disclosed the progress of the security incident: affected wallets have restored access, and the asset return process will be announced soon

Web3Auth has released the latest developments on the security incident, which previously affected some embedded wallets created through Google or Apple login due to security vulnerabilities in the infrastructure, leading to unauthorized access to some accounts. Affected services include Torus Wallet and some embedded wallets used by third-party applications like Keplr.Currently, the affected funds are securely held by the project team, which is coordinating the subsequent return process. Specific procedures are expected to be announced in the coming days, and asset rescue operations are still ongoing. In terms of services, existing users can log in and access wallets through Web3Auth Plug & Play and Single Factor Auth (SFA) SDK, but some restrictions still exist. Web3Auth SDK v9 and earlier versions have been deprecated, and developers need to upgrade to v10 or v11. Existing SFA users can log in normally, but new user registration is temporarily restricted. Developers on the Sapphire network can open new user registration by migrating to the latest SDK, while the Legacy network plans to restore this feature by November 23, 2026.Web3Auth reminds users to be vigilant against scams impersonating official asset recovery services, and not to disclose their mnemonic phrases, private keys, or login credentials to anyone, nor to trust private messages that actively offer asset recovery services.
app_icon
ChainCatcher Building the Web3 world with innovations.