Telegram Bot Rug Pull Warning Signs

What a Telegram bot rug pull actually is

A Telegram bot rug pull is the operator of the bot refusing withdrawals, moving deposited balances, or closing the bot and its channel and disappearing. The trading may have been genuine up to that point. The decision to stop honouring balances is made by the people running the software, not by the market.

That is why a price chart tells you nothing about it. The token you bought can be trading normally, your entry can be well in profit, and the balance shown in the bot can still be gone, because that balance is a number the operator's servers keep and the operator can stop paying.

Three different failures, one nickname

People use "rug" for events that have little in common. Separating them matters, because each one has different warning signs and a different first move.

A fourth case, a token that simply will not sell, is a contract problem rather than an operator leaving, and it is covered elsewhere.

The order the signals arrive in

An exit rarely starts with an announcement. Money movement usually comes first: withdrawals slow, then need review, while deposits keep working. The Telegram presence changes next, with a quiet channel, deleted posts or a new username. Documents follow, as fee pages, terms and public pages get edited or taken down. Panic, pressure and deadlines tend to arrive last, once users have already noticed.

One line frames everything below: whether the bot generated the wallet for you or you imported your own changes what an exit looks like from your side.

None of this is financial advice.

Token rug, operator exit, impersonator copy: three different failures

People use "rug pull" for three separate events. They fail in different places, and the first move after each one is different. Sort the failure before you react.

Token rug: the coin failed, not the bot

You asked the bot to buy a token, and the token's own developer pulled its liquidity or dumped supply on holders. The bot executed the trade it was given. Your position in that coin is what failed, and the bot's fee page, terms and support have nothing to do with it. First move: check the token on chain, confirm whether sells still go through and how much liquidity remains, and stop buying more of it. Do not open a support ticket about the bot.

Operator exit: the withdrawal is the thing in doubt

The team behind the bot stops honouring withdrawals, moves deposited funds, or shuts the bot and its channel and disappears. Here the bot is the failure, and the money you are trying to get out is the money at risk. First move: stop depositing, screenshot balances and transaction history while the bot still shows them, and try the smallest possible withdrawal to see whether the queue moves at all.

Impersonator copy: the money never reached the real service

A fake bot wearing a real bot's name and handle takes your deposit, or asks for a seed phrase and takes the wallet. First move: close the fake, then reach the real bot only through the handle published on that bot's own website or documentation. Banana Gun lists @BananaGun_bot at bananagun.io, and Bloom lists @BloomSolana_bot in its docs at docs.bloombot.app. A handle forwarded in a group chat or a DM is not a source.

Why the split matters

With a token rug you can still withdraw whatever the bot owes you, so the account is fine. With an operator exit, the withdrawal itself is the thing in doubt, and timing matters. With an impersonator there is no account to recover, because the money never reached the real service.

The sorting test

Three questions separate them quickly. Does the bot still show your balance correctly, and does that balance match the wallet on chain? Does the bot's own channel still exist and still post? And is the handle you are typing into the one printed in the bot's own documentation?

Who holds the keys: generated wallet versus imported wallet

The custody model decides what a rug pull looks like from your side. Neither setup is safe or unsafe on its own. What changes is where the risk sits, and therefore which signal you should be watching.

A wallet the bot generates for you

You start the bot, it creates a wallet and gives you a deposit address. The material that can move that balance stays on the operator's servers, which is what lets the bot sign trades for you and show a running balance inside the chat. The trade-off is that the operator also controls the thing that can move your money.

An exit in this model is not a hack. It looks like a withdrawal that never lands, a queue that needs "review", or a minimum that quietly rises. Your protection is speed and small balances: keep only what you are actively trading in the bot, and withdraw the rest. You cannot move funds the bot will not release.

A wallet you import or connect yourself

Here you bring a wallet you already control, either by importing a private key or by connecting and signing approvals. The bot does not need your keys to trade. It needs permission, and that permission is the exposure.

What matters is which contract you approved and what that contract can do. A hostile contract, or one changed after you approved it, is a bigger risk than whatever the operator intends. The advantage is that approvals can be revoked from your own wallet, without the bot's permission or cooperation.

What to watch, and the rule for both

With a generated wallet, watch withdrawal behaviour. With an imported wallet, watch your approvals and read what the bot's contract asks you to sign next, particularly the first time you use a new function.

Sniping and copy trading are where wallets and approvals get connected most often, so the custody question arrives early. Both feature pages are worth reading before you connect anything: sniping bots and copy trading bots.

Whichever model you use, never share a seed phrase or private key with anyone: not a bot, not a support account, not an admin who offers to help in a direct message. No legitimate operator or support person needs it, and anyone asking for it is working against you.

Signal one: deposits still welcome, withdrawals stalled

If you watch only one thing, watch the difference between money going in and money coming out. A bot that is about to keep your funds still needs new deposits to arrive. So incoming payments stay smooth, the deposit address keeps working, support keeps replying, and the product looks alive. Outgoing payments are the part that gets throttled. The widening gap between the two is the signal.

The variants to recognise

Withdrawals rarely stop with an announcement. They get harder in small, plausible ways:

• A raised withdrawal minimum. The number moves up until your balance no longer qualifies.
• A new withdrawal fee that did not exist when you deposited, sometimes large enough to make the payout pointless.
• A queue or cooldown introduced "for security" or "during maintenance", with no end date.
• Selective processing. Small withdrawals clear; larger ones sit in review indefinitely.
• Support that answers instantly about anything else, then goes quiet the moment you ask about a payout, or forwards you to a second account that never resolves it.

Why the pattern shows up this way

An operator who intends to keep operating needs the deposit flow intact. Choking incoming payments would kill the business and warn everyone at once. Choking outgoing payments buys time: every stalled withdrawal is one more day of deposits from users who have not noticed yet. That is why the two directions behave differently, and why the asymmetry, not any single delay, is what you are reading.

What to compare

Two checks are concrete. First, put the balance the bot shows for you next to the wallet on chain: if the bot's number and the on-chain number disagree, find out why before you send anything else. Second, compare how long your last small withdrawal took with how long an earlier one took. Minutes versus "under review" is a change you can measure.

What to do

Test with the smallest withdrawal the bot allows, before depositing anything further. Record the timestamp, the amount, and the transaction hash or reference. If it clears, you have a baseline for next time. If it does not, stop depositing.

One slow withdrawal is not proof. Networks congest, queues build, and manual review sometimes happens for real reasons. What matters is direction: a friction pattern that only ever runs one way, with deposits easy and payouts hard, is the most common shape of an exit already in progress.

Signal two: the Telegram presence changes

The Telegram account is the whole shopfront for a bot, which makes it the cheapest place to stage a wind-down. Read the account itself, not just the balance inside the bot.

The username changes

A bot renaming its username can be an ordinary rebrand. It is also the cheapest way to strand existing users: the old handle goes quiet or passes to someone else, and people who type the name they remember land on the copy. Until the new handle is confirmed on the bot's own website or documentation, treat a rename as a red flag. An announcement inside the channel proves little, because the channel is exactly what may have changed hands.

A second bot with the same branding

A new bot with a similar name, a fresh channel and the same logo and tone, appearing around the same time the original goes quiet, is the impersonation pattern. Deposits sent to the newcomer have no history behind them: no withdrawals paid to anyone you can check, no record of how the bot behaved through a bad week. The two events arriving together is the detail worth noticing.

Smaller signals in the same place

• The channel clears its history, or comments and group chat are closed or wiped.
• Admins stop posting while the deposit address stays live.
• The pinned post stops being updated, so onboarding links point somewhere stale.
• Support goes silent, or starts replying from a new username.

Verify the handle at the source

Confirm the handle on the bot's own documentation or website. Not a pinned message, not a forwarded link, not a search result. Bots that publish an official handle make this a ten-second habit:

Bookmark the handle you verified. If the account in your chat list stops matching it, you are looking at a different account.

Signal three: the paperwork drifts

Document drift is a change to a bot's public paperwork that is not explained in public. The fee page is rewritten, the terms lose a section, the audit page stops loading, or the documentation site redirects somewhere new, and no announcement in the channel accounts for it. On its own, one edit proves nothing. As a pattern, it shows the operator is changing the record after users have relied on it.

The three pages worth watching

• The fee page. It is the operator's own statement of what it charges. If the number changes quietly, the page is no longer a reliable reference for your costs.
• The terms page. It sets out what happens to your balance, including withdrawal conditions. Sections that disappear from terms are more serious than sections that are added.
• The audit page. An audit page is a claim the operator once made. If it vanishes, the claim goes with it, even though users may still be repeating it.

A business decision or a quiet rewrite

A fee change announced in the channel, with a date and a reason, is a business decision. You can accept it or move on.

A fee page quietly rewritten, a clause deleted, or a documentation site that suddenly redirects is a different event. The change is designed to be missed. Treat unexplained edits to terms or audit pages as a stronger warning than a fee increase that is openly posted.

Keep your own copy

Some bots publish a fee page with clear figures. Banana Gun's site (bananagun.io), Bloom's fee structure page (docs.bloombot.app), BONKbot's fee structure page (docs.bonkbot.io), Maestro's documentation (docs.maestrobots.com) and Sigma's fee page (docs.sigma.win) are all public pages you can open and keep. A bot whose docs state no fee at all has given you less to compare, so keep a copy of whatever is published.

Save the link and the date you read it. A later rewrite then becomes something you can see, rather than something you have to remember.

Pressure tactics and behaviour around the exit

A failing operator usually needs one more thing before disappearing: fresh deposits. That need shows up as persuasion, and it tends to arrive in a small number of recognisable shapes.

Urgency dressed as opportunity

• A push to deposit before a migration, an upgrade or a "cutover date".
• A limited-time bonus that pays more the larger the balance you leave in the bot.
• A new token or points programme that only counts if you lock funds inside the bot rather than withdraw them.
• A promise that withdrawals are paused now but will resume once the upgrade lands.

Each of these converts your balance into a promise. The straightforward test for any migration claim: can you withdraw first and deposit afterwards? A real upgrade survives that order. If the answer is that the old balance is frozen while the new bot takes fresh deposits, the move is a transfer of your money, not an improvement to the product.

Support that arrives in your DMs

An account claiming to be an admin, offering to fix a stuck withdrawal for a fee, offering to recover funds, or asking for your seed phrase or private key. None of these are ever legitimate. Support does not need your seed phrase, and a withdrawal does not cost an extra payment to release.

A chat that has been tidied

Real questions deleted. Critical users banned. The remaining messages full of accounts that post only about how smoothly withdrawals are working. Read the pattern rather than any single message: a channel where complaints vanish is telling you something about the operator's priorities.

These are behaviours to recognise, not a verdict on any particular bot. Treat each one as a reason to reduce exposure: withdraw what you can, stop adding funds, and keep the messages and screenshots.

What to do in the first hour

The first hour is about keeping options open. It is not about arguing with a bot or waiting for a reply that may never come.

1. Stop depositing

No top-ups, no "just enough to cover the withdrawal fee", no new positions. Whatever the bot says about needing a minimum balance, a deposit will not fix a withdrawal that has stopped.

2. Try the smallest withdrawal the bot allows

Do it now, while the bot still responds. A small successful withdrawal tells you the payout route works; a failed one tells you where you stand. Write down the exact error text and the time.

3. Capture evidence while the bot still loads

Screenshot your balance, your deposit and withdrawal history, the transaction hashes of everything you put in, the handle you are talking to, and the date. Save the fee and terms pages as they look right now, plus the address of the page you got them from. If those pages change later, you will have the earlier version.

4. Check the handle against the bot's own docs

Open the bot's official site or documentation and read the handle there, not in any message you have received. Bots such as Banana Gun, Bloom and BONKbot publish theirs, and that is the habit worth keeping for any bot. Treat every "support" account that messages you first as unverified.

5. Act by custody model

• Generated wallet: keep trying the withdrawal route at intervals and log each attempt with a timestamp. That record is the useful thing you can build.
• Imported wallet: revoke the approvals you no longer want, from the wallet side, rather than waiting for the bot to act. Check what is still approved before you sign anything new.

What not to do

• Never send a seed phrase or private key to anyone, including "support".
• Do not pay a recovery fee.
• Do not move funds into a bot that appears in your direct messages.
• Do not chase the position with a bigger deposit.

Trading memecoins can lose all of the money put in. None of this is financial, legal or tax advice.

Checking a bot before you deposit anywhere

Ten minutes of reading before the first deposit is cheaper than any recovery attempt afterwards. The routine is the same every time.

Four things to find

• The official handle, on the bot's own website or documentation, not from a forwarded message, a group admin or a Telegram search.
• The fee page, stating what the bot charges on each chain it supports.
• The terms, including the part that says what happens to a balance if the service stops.
• A saved copy: bookmark those pages and note the date you read them, so a later rewrite is something you can see.

What a complete paper trail looks like

An operator that publishes its handle, states its fee on every supported chain and writes terms covering balances gives you three points of comparison. That is the minimum for judging a bot as a business rather than a username. Bots with all three can be lined up side by side at /bots.

Where to practise the handle habit

Open each bot's own site or docs and check that the handle there matches the one you are about to message. If the only place you can find a handle is a Telegram search, you have not confirmed it.

The rule that survives every check

Keep deposits small enough that a freeze is survivable, and test a withdrawal before you scale up. That holds whether the paperwork is perfect or thin. If you want to narrow the list first, /chain/solana collects the Solana bots, and the feature pages cover what you actually use a bot for, such as /feature/sniping and /feature/copy-trading.

Compare the bots side by side at /bots, where each one is listed with its official handle and the documentation its terms come from.

Frequently asked questions

How do I know if a Telegram trading bot is about to rug?

Watch behaviour, not promises. Warning signs: withdrawals slow down or move "under review" while deposits still land; support answers only in DMs; the fee or docs page stops matching what the bot actually charges; the Telegram handle changes without a notice on the bot's own site; admins delete questions in the group; you are pushed to deposit more to "unlock" a withdrawal or a tier. Before depositing, read the bot's own fee docs and confirm the handle there rather than in a pinned message someone else copied. A bot that holds your key can move your funds at any time. These signs raise risk; they do not prove intent.

Is a bot with an anonymous team automatically a scam?

No. An anonymous team is a risk factor, not proof of fraud, and many Telegram bots are run by pseudonymous developers. What anonymity changes is accountability: there is no registered company to complain to and no realistic route to recover funds if they disappear. So judge the things you can check. Does the bot publish fee terms on its own docs, and does the charge match them? Is the official handle listed on that same site? Are withdrawals processed on normal timing? Does the public channel keep critical questions up? Weigh those signals against the amount you are prepared to leave in the bot.

The bot changed its username. Is that normal or a red flag?

Treat it as a red flag until you confirm it at the source. Usernames change for ordinary rebranding, but the same mechanic helps a scammer: the real bot drops a handle, someone registers it, and old users tap the wrong chat. Before you deposit again, open the bot's own website or docs and check which handle is listed there today. If the docs still show the old name, or list no handle at all, stop and do not send funds. Ignore any DM announcing the change. Open the bot from the site page each time rather than from chat history.

Deposits still work but withdrawals are under review. Should I keep waiting?

Stop depositing now. Working deposits while withdrawals sit "under review" is the classic shape of an exit: new money keeps arriving while old balances cannot leave. Ask three things. Is there a public statement with a date and a reason? Does support answer in the open channel or only in DMs? Does a small test withdrawal go through? Screenshot your balance, your transaction history and the bot's fee docs. Never send more funds to "unlock" a withdrawal, and never share a seed phrase with anyone offering to recover it. With no public explanation, plan on the funds being at risk.

Can a fake bot take my funds even if the real bot is fine?

Yes, easily. Impersonator bots copy the name, the profile picture and even pinned messages, then message you first with a "wallet verification" link or a request for your seed phrase. The real bot's reputation does nothing for you if you are typing to a copy. The only safe route is the official handle published on the bot's own website or docs; BONKbot's docs, for instance, list @bonkbot_bot. Save that handle once, check it character by character, and open the bot from the site rather than from a DM or a group member list. Anyone asking for a seed phrase is not support.

Does importing my own wallet protect me if a bot shuts down with my funds?

Partly. Holding your own seed means you can open the same wallet in another app if the bot disappears, so you are not locked out of the address. It does not stop the bot moving funds: a bot that trades for you needs access to sign or a key, and token approvals can stay live after you leave. So import your own wallet, revoke approvals you no longer use, and keep only trading amounts in the hot wallet you connect to bots. A separate wallet per bot limits what one failure can reach.

Sources

• Banana Gun official site
• Bloom fee structure
• BONKbot fee structure
• Maestro documentation
• Sigma fees