Binance Wallet upgrades Agentic Wallet security mechanism, r
On November 2, Binance Wallet announced that it had completed a new round of Agentic Wallet security upgrades, restricting users from logging in to high-risk third-party websites via QR codes in accordance with real-time risk control rules; sites that trigger the rules will be forcibly logged out, and the platform will also carry out regular security scans. Binance Wallet said that users have recently reported QR code login failures, and reminded users not to scan QR codes from non-official platforms.
Event Timeline
- [11-02 12:24] Binance Wallet upgrades Agentic Wallet security mechanism: restricts QR code login on high-risk websites (Odaily 星球日报)
- [11-02 12:31] Binance Wallet upgrades Agentic Wallet security mechanism, restricts scan-code login on high-risk third-party websites (PANews)
Background and Impact
On November 2, Binance Wallet announced that it had completed a new round of Agentic Wallet security upgrades. Odaily 星球日报 reported the news at 12:24 that day, and PANews published a largely identical report at 12:31; the two sources' descriptions of the direction of the upgrade, the trigger conditions and the user reminders are consistent, differing only in headline wording, using "QR code login" and "scan-code login" respectively. As of publication, neither item disclosed the specific list of restricted websites, the details of how the risk control rules are determined, or the scope of coverage of the mechanism.
According to both sources, the new mechanism operates on real-time risk control rules: the platform restricts users from logging in to high-risk third-party websites via QR codes; for specific websites that trigger the risk control rules, users will be forcibly logged out. In addition, the platform will carry out regular security scans. Binance Wallet also stated that users have recently reported QR code login failures. This phenomenon appears alongside the above restrictions in both items, but the items do not further explain the specific distribution of causes behind the login failures.
In the user reminder section, Binance Wallet stated that, to protect asset safety, users should not scan QR codes from non-official platforms to log in to Agentic Wallet, and should use only trusted Agents such as Binance AI Pro as well as Claude, Codex and Grok. In terms of mechanism design, the restriction falls at the login entry point, which amounts to moving risk control ahead of the authorization action; for users, the directly visible change is that the scan-code path for some third-party websites is no longer available, and websites that trigger the rules will be forcibly logged out.
Neither source mentioned whether this upgrade is related to asset loss incidents or specific attack cases, nor did they provide a timetable for subsequent rule adjustments. For wallet users accustomed to switching between multiple tools — whether in OKX community groups, Huobi player discussions, Huobi community groups, or Zhima Kaimen player discussions and Bitget player discussions — when encountering scan-code login anomalies, checking the source of the website first and returning to the official entry point to operate is more reliable than repeated retries.
FAQ
### Which operations does this upgrade affect?
According to both sources, the restriction targets the act of logging in to high-risk third-party websites via QR codes, and specific websites that trigger the risk control rules will have users forcibly logged out. Binance Wallet did not publish the list of restricted websites or the determination details in the items, nor did it state whether other login methods are involved.
### What should be done if scan-code login fails?
Binance Wallet stated that users have indeed recently reported QR code login failures, and reminded users not to scan QR codes from non-official platforms to log in to Agentic Wallet, and to use only trusted Agents such as Binance AI Pro as well as Claude, Codex and Grok. The items did not provide further troubleshooting instructions.
### What other points are worth watching going forward?
The items mention that the platform will carry out regular security scans, but did not publish the scan frequency, the update cadence of the restricted list, or a timetable for rule adjustments. How the scope of restricted websites changes and whether the risk control rules are made public are information points to watch going forward.