Is GMGN Safe? Custody, Private Keys, and What You Actually Control

What is the one fact that decides everything else?

You cannot export a private key from a GMGN wallet on any chain it supports, including a wallet you imported yourself. GMGN's own wallet documentation is unambiguous about it:

For the safety of user wallet funds, GMGN all chains ( SOL chain / EVM chain / Tron chain ) are prohibited from exporting private keys; Wallets imported from outside also can't export private keys.

That is verbatim from GMGN's TG wallet documentation, and the same sentence appears in bold on the wallet connection page.

Read the second clause again. Wallets you generated yourself, elsewhere, and imported into GMGN also cannot be exported. Import is a one-way door.

Export was disabled around 19 March 2025. Co-founder Haze gave the rationale at the time: to eliminate security risks and protect asset safety, the wallet generated by GMGN does not support exporting private keys, a change prompted by thefts that happened after users exported their keys (Gate News). That rationale is real. Clipboard-stealing malware harvesting a plaintext key out of a Telegram chat was a live problem, and removing the key from the client removes that attack surface.

It also removes every user's exit path. Both things are true at once.

Four places GMGN's own material says it holds the key

The export ban on its own could be read as a UI restriction rather than a custody statement. It is not the only signal.

The Agent API language comes from GMGN's Agent API page. The Phantom quote is from the multi-wallet documentation, which also notes that connecting Phantom generates fresh addresses on each chain rather than trading from your Phantom address. The bounty tier is from the GMGN Vulnerability Bounty Program, which pays up to 1,000,000 USDT in its "Extreme" band for vulnerabilities "potentially leading to major business disruptions or unauthorized access to GMGN wallets, funds, or private keys." That is GMGN's own description of the scope it will pay to have tested.

No GMGN document we read on 6 August 2026 describes MPC, threshold signing, secure enclaves or any other architecture that would let GMGN sign a transaction without a key sitting on its side. We could not confirm the architecture either way, because GMGN does not publish it. What is on the record is the list above.

The contradiction, quoted from both sides

Now put the documentation next to the contract. GMGN's Terms of Service, at gmgn.ai/static/tos.html, section 3.3, says this:

...while maintaining control over your private keys. The TG Bot functions as an interface that allows you to interact with your own wallet created by GMGN. When you transfer funds to this wallet, you retain control over your private keys and assets.

Set that against the documentation sentence at the top of this page. One document says users retain control over their private keys. The other says users are prohibited from exporting them on every chain supported. Both were live when we read them on 6 August 2026. Both are published by GMGN. Which one governs is a question for a lawyer reading the whole agreement, not for a guide, so we are not answering it here.

The Terms go further with a disclaimer written in capitals, and it carries a qualifier worth reading slowly:

GMGN CANNOT INITIATE A TRANSFER OF ANY OF YOUR CRYPTOCURRENCY OR DIGITAL ASSETS OR OTHERWISE ACCESS YOUR DIGITAL ASSETS IN YOUR OWN WEB3 WALLETS

Note the closing words, "in your own web3 wallets." The sentence does not say "in your GMGN wallet," and we are flagging the wording rather than telling you what it means. GMGN's safety documentation states the point more broadly in plain text, saying GMGN "does not perform any operations on the user's wallet, and we do not have the ability to transfer any user's wallet balance." Nothing in this research contradicts that statement. Read the clause and the documentation side by side, and take advice if the difference matters to your situation.

What does "cannot exit" cost you in practice?

Three consequences follow, and they are the ones that actually cost people money.

Your Telegram account is your wallet. GMGN's wallets are generated and bound at first login through Telegram, and there is no exportable key or seed phrase behind them. GMGN's documentation describes no key-based recovery path if that Telegram account is lost, banned or taken over. GMGN devotes a section of its safety tips to hardening Telegram itself, including two-step verification and blocking group invites. On this setup, the Telegram account is the weakest link in the chain, and that section is the closest thing GMGN publishes to an acknowledgment of it.

Importing to an EVM bot deletes your old address. This one is stated with an exclamation mark in the docs and is still routinely missed:

When you import a new wallet address to EVM chain bots, the old wallet address will be automatically deleted. There is no way to help you recover your assets!

The ETH, Base and BSC bots share one address, so importing a key into any of them changes all three at once (wallet docs). Anything sitting on the replaced address across those three networks is gone from your reach, and because export is banned you cannot recover it with the old key either. Solana behaves differently: importing there opens the multi-wallet manager and keeps the previous wallet.

The path that keeps your keys costs you the product. You can use GMGN with a browser extension wallet through "Trade with Wallet", which leaves your keys where they already were. Doing so forfeits Anti-MEV routing and the automation suite, and creates a separate account whose data is not shared with a Telegram-wallet account (multi-wallet docs). That is the real trade: hold your own keys, or get the features people come to GMGN for. Pick knowingly. Our how to trade on GMGN walkthrough covers both paths, and connecting Telegram and funding the wallet covers the setup if you take the bot route.

What withdrawal holds does GMGN's documentation publish?

Before concluding that GMGN has frozen your funds, check this list, because each of these rules is published and each of them looks like a freeze from the inside. Withdrawal was moved off the Telegram bot entirely and rebuilt on the website in March 2025, with 2FA, whitelisting and time locks added at the same time (Odaily, 25 March 2025).

Every row comes from GMGN's own withdrawal documentation. Each control raises the cost of an attack on your session, and each one also slows you down when you want to move quickly. That trade-off is the practical thing to plan around. If your withdrawal is not blocked by one of the rows above, our transaction failure guide covers the error codes that explain the rest.

Does GMGN front-run its own users?

The most repeated claim about GMGN is that it front-runs or sandwiches its own users. The on-chain record points firmly the other way, and this is worth getting right because it is the one place where the crowd consensus is simply wrong.

GMGN's users were the victims. In an April 2025 analysis of Solana sandwich activity, GMGN was reported as the single most sandwich-victimized app on Solana, accounting for roughly 30.8% of sandwich attack profits relative to its own activity, inside a 30-day window covering more than 260,000 attacks and about 23,600 SOL extracted across Solana trading apps (Ainvest). That report does not name the underlying dashboard, so treat the exact percentage as a reported figure rather than one we independently reproduced. The direction of the finding is what matters: GMGN's order flow was being harvested, not doing the harvesting.

GMGN's behavior fits that reading:

• In March 2025, co-founder Haze publicly pressed Solana over validators leaking transaction data to sandwich bots (AiCoin).
• In July 2025, GMGN shipped hardened MEV protection with a compensation process attached. Haze's words: "If it has been verified that MEV was enabled and you were sandwiched, we will compensate you", while conceding the protection "is not perfect" (crypto.news).
• GMGN's fee documentation ships a plain-English explanation of sandwiching and a three-tier Anti-MEV RPC selector, with the trade-off between speed and protection spelled out (fee settings docs). We break the settings down in the GMGN fees guide.

In late October 2025 GMGN was hit by a phishing wave in which a forged third-party token website drove unauthorized transactions, affecting roughly 107 users. Haze committed to 100% compensation and the funds were credited directly to affected GMGN accounts, with no claim process for users to navigate (Lookonchain, Phemex News, 28 October 2025). GMGN separately published a statement rejecting the broader "GMGN was hacked" rumors after an audit (@gmgnai).

Set against that public record, the front-running story has nothing behind it that we could find. No specific, credible allegation naming GMGN as the front-runner surfaced in this research as of 6 August 2026. Treat the claim as unsupported until someone produces transactions.

Where the money that actually disappears goes

GMGN's own support pages are the best evidence for what causes user losses, because they are essentially a catalog of what support gets asked about. From the Q&A and safety tips, the recurring causes are: device malware from clicking unknown links, Telegram installed from unofficial sources, third-party Telegram translator plugins, authorizing a fake bot, and signing a malicious approval from an airdropped NFT. GMGN's blunt summary is that these are "GMGN official can not control", and on the causes listed above that description matches what the incidents involved.

None of those causes are things the terminal screens for, which is worth separating from the checks it does run. GMGN puts a contract security panel on every token page, and its fields are about the token rather than about your device or your Telegram account: what the contract security panel screens for defines mint authority, blacklist, LP burned and honeypot from GMGN's own wording, one field at a time. A clean panel says nothing about the five causes above.

Two patterns are worth naming precisely.

Fake bot handles. Scammers register lookalike Telegram handles using a capital "I" in place of a lowercase "l", which is visually identical in most fonts (sniper bot docs). GMGN also warns never to click the ads that Telegram displays above the bot, and states that official admins never DM first and never ask for a private key.

Fake domains. A live phishing clone at app-gmgn-ai.com has its own removal guides from security vendors (PCrisk), and Bing surfaces typosquats like gmgn-tracker and gmgn-app.at in its index. On RDAP and DNS checks run 6 August 2026, the obvious TLD variants did not resolve to a GMGN site: gmgn.com was registered in 2004, before gmgn.ai existed, gmgn.org was parked for sale on Afternic, gmgn.net returned a server error and gmgn.app was an empty deploy. Verify the address bar rather than assuming a variant belongs to GMGN. The same problem exists on the app stores, where a search is not a verification step; is there a GMGN mobile app records the two listings gmgn.ai/app itself links to and the developer and seller names on each.

Treat anything outside that list as unofficial until you can verify it, including the gmgn.io, gmgn.com, gmgn.net, gmgn.org and gmgn.app variants, none of which served a live GMGN site when we checked them on 6 August 2026. On the Telegram side, GMGN's alert channel documentation states the reason for its own setup in one line: "To avoid scam ads shown in public channels, the GMGN Team has switched official channels to private channels."

The legal picture is thinner than you would expect

The Terms of Service and Privacy Policy are not at /terms or /privacy, both of which return 404. They live at gmgn.ai/static/tos.html (last updated 6 December 2024) and gmgn.ai/static/privacy-policy.html (last updated 1 January 2025). Below is what those two documents said when we read them on 6 August 2026. This is a description of their contents, not an interpretation of them, and none of it is legal, regulatory or tax advice.

• Section 16.1 names the laws of the British Virgin Islands, and section 16.2 sends disputes to arbitration at the BVI International Arbitration Centre under BVI IAC rules, before a tribunal of three.
• No company is named in the document. The counterparty appears as "GMGN.AI", without a company number, registered address or list of officers, and section 19.5 directs questions, complaints and claims to a Telegram group and an X account.
• Neither document describes an identity-verification step. Reading the Terms, the privacy policy and the 68 documentation pages on 6 August 2026, we found no passage describing KYC and no passage in which a license or registration is claimed. What that absence means for GMGN, or for you as a user, is a question for a qualified lawyer in your own jurisdiction rather than one this page can answer.
• Section 5.2 asks you to represent that you are not in, under the control of, or a national or resident of Afghanistan, Cuba, Iran, North Korea or Syria, and not a person on UN, US OFAC or EU sanctions lists. The United States does not appear among the named countries. The clause is written as something you state about yourself, and we found no published description of how, or whether, GMGN verifies it. Whether you personally may use a service like this is governed by the law where you live, so ask a professional if the answer matters to you.
• Section 4.1 says you authorize GMGN to deduct fees directly from your wallet for each transaction, and reserves the right to change the fee schedule at any time, effective on posting.
• Section 8.14 lists front-running, wash trading and ramping among the things users agree not to do. We did not find an equivalent undertaking running in the other direction.

Then there is the documentation defect. The privacy policy carries another product's name throughout, branded "Meme Tracker": "This Privacy Policy describes the privacy practices of GMGN.AI ('Meme Tracker', 'we', 'us' or 'our')", with a data-rights contact link that reads literally https://t.me/Meme Trackerai.

So, is GMGN safe?

Safe against what. On the question of the operator taking funds, what we found as of 6 August 2026 is reassuring: no verified infrastructure compromise reported anywhere we looked, a 1,000,000 USDT top bounty tier run through HackenProof, an anti-MEV campaign fought in public, and compensation paid twice without users having to file claims. On the question of keeping access, the documentation points the other way: no exportable key, no seed phrase, no export on any chain including wallets you brought yourself, an EVM import that replaces the previous address, and a wallet whose only door is a Telegram account you do not control either.

Which points to one rule rather than an avoid-it verdict: keep only trading capital in a GMGN wallet, and sweep profits out to a wallet whose keys you hold. That habit prices in every risk above and costs you a withdrawal's worth of gas. If you are still deciding whether GMGN is the right terminal at all, our GMGN vs Photon comparison and the what is GMGN overview cover the product side, and the referral code page explains exactly who gets paid what, including the fact that referred users get no discount.