Bitget Wallet announced Nov. 11 that it is expanding AI-assisted threat detection after Bitget Wallet phishing alerts averaged about 37,000 signing requests a week in Q3 2026 — 7.4 times the 5,000 weekly average in Q2. The company was upfront that better detection, not just greater threat activity, drove part of that jump: the figures count flagged signing interactions, not unique attacks or confirmed financial losses.
- đź“ŽBitget Wallet Phishing Alerts and What Drives the Jump
- đź‘ĄHow GetShield Checks Sites and Permissions Before Users Sign
- ⚠️AI Flags 90% of Newly Blocked Risky Domains
- ⚠️Why Signing Permissions Are the Core Risk
- âť“FAQ
Bitget Wallet Phishing Alerts and What Drives the Jump
Chief operating officer Alvin Kan shared the numbers with Cointelegraph, saying the surge likely reflects both a more active threat environment and sharper monitoring. The wallet rolled out AI-assisted risk detection in Q2, so the expansion announced this month builds on a system that has been live for less than two full quarters.
Phishing-related signing requests led all categories at 57% of Q3 detections. Malicious addresses came in at 17%, risky contracts at 14%, and malicious approvals at 12%.
How GetShield Checks Sites and Permissions Before Users Sign
The Nov. 11 announcement details expanded checks built into GetShield, Bitget Wallet’s security engine. It scans website code for fraud or impersonation, then checks domain registration records and connections to known malicious domains.
On the transaction side, GetShield simulates outcomes before a user signs anything — hunting for hidden permissions or gaps between what the screen shows and what the signature would actually authorize. That matters because a crafted approval can hand an attacker access to funds without ever touching the private key. The engine layers its own screening over external threat intelligence and handles token approval management across websites, decentralized applications, and smart contracts, including unexpected last-second changes to signing requests.
AI Flags 90% of Newly Blocked Risky Domains
In October, AI identified 90% of newly blocked risky domains, up from 36% in Q2. Nearly 70% of those flagged domains had no matching alerts in any external threat feed the wallet checked. That blind spot — not theoretical risk, but real gaps in existing lists — is the core reason Bitget Wallet is pushing beyond third-party databases.
Kan framed the broader goal as catching risks earlier and limiting damage while keeping users in full control, as self-custodial wallets push deeper into payments and day-to-day finance.
Why Signing Permissions Are the Core Risk
The stakes are concrete. In July, a trader lost nearly $1 million after signing a malicious Ethereum token approval — a clean example of how a single signature, not a compromised seed phrase, can drain a wallet.
In comments published Oct. 6 and reported by crypto.news, Kan argued that wallets need to make plain whether an approval covers one payment or grants an app the ability to move funds indefinitely — and that revoking existing permissions should be straightforward. The next step Bitget Wallet has outlined is wider AI-driven threat detection paired with AI-assisted incident response, with humans staying in the loop.
FAQ
When did Bitget Wallet introduce AI-assisted risk detection?
The initial introduction came in Q2 2026, according to chief operating officer Alvin Kan. The Nov. 11 announcement expands that work across website, domain and transaction analysis.
What share of Q3 detections involved phishing-related signing requests?
These requests made up 57% of the wallet’s detections across four monitored categories. The remaining categories were malicious addresses, risky contracts and malicious approvals.
How does GetShield check what a transaction would authorize?
GetShield simulates transaction outcomes before approval. It looks for concealed permissions and discrepancies between the displayed signing request and the actions it would permit.
How can malicious signing permissions expose funds without revealing a private key?
A signature can authorize an application to spend tokens, giving an attacker a route to funds without obtaining the key. In his Oct. 6 comments, Kan emphasized the distinction between approving a single payment and granting ongoing spending permission.
What further security work does Bitget Wallet plan?
The company plans to explore AI-assisted incident response alongside further expansion of threat detection. It says that response work would aim to identify emerging risks and accelerate action under human oversight.
This article is for information only and is not financial advice.
Related Articles
Crypto Hosting Vercel Confirms Breach as Hackers Seek $2M for Stolen Data
Crypto hosting firm Vercel said a limited subset of users was affected as hackers claimed to be...
MetaMask Security Incident Triggers Ethereum Validator Exits as Lido Sets Oct. 7 Deadline
MetaMask has begun removing Ethereum validators from its noncustodial staking service following a...
Bitcoin Core Fast-Tracks Fixes and Disclosure for Easily Found Bugs
The Bitcoin Core security policy fast-tracks patches and advisories for easily rediscovered bugs,...
Whale vs. Coinbase: Anonymous Plaintiff Sues Exchange for Refusing to Return $55M
The investor lost funds in a phishing attack back in 2024. Coinbase froze part of the stolen assets...
Ethereum Foundation and Vitalik Buterin Sued by Former Employee Over Firing
Ethereum Foundation Vitalik Buterin lawsuit alleges former employee Kayleen Fulton was fired after...
New York Seeks $1.4B From NovaTech Founders After Default Judgment
New York seeks $1.4 billion from NovaTech founders in the NovaTech lawsuit after a default...
