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

"Is GMGN safe" is usually answered with a verdict. That is the wrong shape of answer. GMGN is not a fraud, has no verified compromise of its own infrastructure, and has paid compensation when its users were harmed. It also holds your private keys and will not give them back, which is a different kind of risk that most reviews of GMGN never mention because GMGN's own documentation buries it under a page title that says the opposite.

This page lays out what GMGN says, where its own documents contradict each other, and what that means for how much money you should keep there. Nothing here is financial advice.

The fact that decides everything else

GMGN's wallet documentation is unambiguous:

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.

Where	What GMGN says	What it implies
Wallet docs	All chains are prohibited from exporting private keys, including imported wallets	The key exists somewhere you cannot reach
Agent API docs	Adopts the GMGN hosted wallet architecture where private keys are not stored locally	Server-side key handling, stated as a feature
Phantom login	GMGN will create a multi-chain custodial wallet account based on your Phantom wallet	GMGN's own word for it is custodial
Bug bounty	Top tier covers unauthorized access to GMGN wallets, funds, or private keys	Only meaningful if GMGN has authorized access

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." You cannot get unauthorized access to a key that nobody has.

Nothing in any GMGN document claims MPC, threshold signing, secure enclaves or any other architecture that would let GMGN sign without holding a key. Absent that, a server-held key is the reading the evidence supports.

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 are current. Both are published by GMGN.

The Terms go further with a disclaimer written in capitals, and the carve-out in it is 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

The qualifier is "in your own web3 wallets." Your Phantom or Rabby wallet, in other words. The GMGN-generated wallet is not covered by that sentence. GMGN's safety documentation makes the broader claim 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." That is a statement about what GMGN does, and there is no evidence contradicting it. It is not the same as a statement about what GMGN could do.

What "cannot exit" costs 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, precisely because the Telegram account is the weakest link in the chain.

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 genuinely non-custodial path costs you the product. You can use GMGN with a browser extension wallet through "Trade with Wallet", which keeps your keys where they 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: self-custody or 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.

Withdrawal holds are not a scam, they are a design

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).

Control	Rule	What triggers the complaint
Where you withdraw	Website only. The Telegram bot cannot withdraw at all	Users hunt for a Withdraw button in the bot and conclude funds are frozen
2FA	Google Authenticator must be bound before any withdrawal	Setup is required first, so the first attempt always fails
Whitelist	Transfers only go to whitelisted addresses; whitelisted addresses then bypass 2FA	A fresh destination address is simply not selectable
3-hour hold	No withdrawals for 3 hours after first whitelist setup or any whitelist change	Reads as a freeze; it is a fixed cooling-off period
24-hour hold	24-hour withdrawal hold after re-binding Google Authenticator	New phone, re-bind, then a day of waiting
Max button	Never sends the full balance; a minimum is retained for account rent and gas	Reads as a skimmed fee, is actually rent-exemption plus gas

Every row comes from GMGN's own withdrawal documentation. These controls are good security. They are also the controls of an exchange, not a wallet, and the cost is that an attacker who compromises your session cannot drain you instantly, while you cannot move fast either. If your withdrawal is not blocked by one of the rows above, our transaction failure guide covers the error codes that explain the rest.

The front-running accusation, and what the data says

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).

A company that skims its own users' trades does not campaign against MEV, publish the mechanics, and reimburse the losses. No specific, credible allegation naming GMGN as the front-runner surfaced in this research. 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", which is both self-serving and, in the main, accurate.

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. GMGN does not defensively own the obvious TLD variants, which leaves the door open.

Real	What it is
gmgn.ai	The app. Everything else on this list is a subdomain or a support surface
docs.gmgn.ai	Official documentation, and the source of most quotes on this page
papi.gmgn.ai	API host
www.gmgn.cc	Official chart embeds, plus the info@gmgn.cc support address. Not a typosquat
x.com/gmgnai	The only account GMGN tells users to verify the real Telegram group against
t.me/gmgnai	Official community group
security@gmgn.ai	Security contact, alongside the HackenProof bounty program

Anything else is unofficial. That includes every gmgn.io, gmgn.com, gmgn.net, gmgn.org and gmgn.app variant, none of which serve a live GMGN site. GMGN moved its official signal channels to private channels specifically to keep scam ads out (alert channel docs).

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). What they contain:

• Governing law is the British Virgin Islands, with disputes going to arbitration at the BVI International Arbitration Centre before a tribunal of three.
• No legal entity is ever named. The counterparty is "GMGN.AI" with no company number, registered address or officers, and section 19.5 directs all questions, complaints and claims to a Telegram group and an X account.
• No KYC. Nothing in the Terms, the privacy policy or the documentation describes identity verification under any circumstance. No license, registration or equivalent is claimed anywhere.
• Prohibited jurisdictions are Afghanistan, Cuba, Iran, North Korea and Syria, plus anyone on UN, US OFAC or EU sanctions lists. The United States is not restricted, and enforcement appears to rest on user self-representation.
• Section 4.1 authorizes GMGN to deduct fees directly from your wallet per transaction, with the right to change the fee schedule at any time, effective on posting.
• Section 8.14 prohibits users from front-running, wash trading and ramping. There is no reciprocal undertaking by GMGN.

Then there is the tell. The privacy policy is a botched find-and-replace of another product's document, branded "Meme Tracker" throughout: "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. Against theft by the operator, the evidence is reassuring: no verified infrastructure compromise, 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. Against loss of access, the evidence is the opposite: no key, no seed phrase, no export on any chain including wallets you brought yourself, an EVM import that deletes 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.

Cite this page

These figures are free to quote. Copy the citation or the link below.

Plain-text citation

GMGNGuide. "Is GMGN Safe? Custody, Private Keys, and What You Actually Control." Published August 6, 2026, updated August 6, 2026. https://gmgnguide.com/security/is-gmgn-safe-custody-private-keysCopy

HTML link

<a href="https://gmgnguide.com/security/is-gmgn-safe-custody-private-keys">Is GMGN Safe? Custody, Private Keys, and What You Actually Control — GMGNGuide</a>Copy

Methodology and reuse

The custody policy, withdrawal holds and quoted policy language on this page are taken verbatim from GMGN's own documentation, its Terms of Service at gmgn.ai/static/tos.html, and its published bug bounty program. They were read from the GMGN TG wallet documentation on August 6, 2026 and re-verified against the live app. Exchanges change their schedules, so treat any figure older than that date as needing a fresh check — the date above is the one to compare against.

You may republish these figures with attribution and a link to https://gmgnguide.com/security/is-gmgn-safe-custody-private-keys.