Telegram Bots Are Stealing Your Crypto. Here’s How. | Stack of Truths

Telegram Bots Are Stealing Your Crypto. Here’s How. | Stack of Truths
Stack of Truths — Pedro Jose / AI Penetration Tester

Telegram Bots Are Stealing Your Crypto.
Here’s How.

By Pedro Jose · 4 min read · #Crypto #Opsec #WalletSecurity

Someone lost $200k last week.

Two wallets. Multiple chains. Drained in 10 minutes.

No suspicious logins. No malware detected. Other wallets on the same device? Untouched.

The victim spent days confused. “How did this happen?”

I’ll tell you.

⚠️ The wallets were generated on a Telegram bot called SIGMA.

That’s not a hack. That’s a giveaway.

What Actually Happened

1. User creates wallets on SIGMA Telegram bot
2. Bot generates seeds. Bot keeps seeds.
3. User imports into GMGN + Rabby (normal. fine.)
4. Attacker finds SIGMA’s database. Or logs. Or backup.
5. Attacker watches. Waits. Sees balance grow.
6. One day, attacker empties both wallets in 10 minutes.

Manual drain. No automation. Just a human with the keys, transferring everything.

Other wallets on Rabby untouched? Of course. Those weren’t generated by SIGMA. Different seed. Different story.

Why This Keeps Happening

People chase convenience. They type “/create wallet” into a Telegram chat. A bot replies with a seed. They copy it. They feel rich.

Here’s what they don’t ask:

– Where is this seed stored?
– Who has access to the bot’s database?
– Does the bot log every request?
– Is the developer looking at your keys right now?

The answer is almost always: you don’t know. And that’s the problem.

The SIGMA Situation

I’m not saying SIGMA is malicious. Maybe it’s compromised. Maybe it always was. Maybe someone found a backup.

Doesn’t matter.

The second you let a third-party bot generate your seed, you’ve lost control. You’re trusting a stranger with your money.

Would you hand your bank password to a random Telegram user? No. But people hand their seed to a bot and call it “crypto.”

The Hard Rules

Rule 1: Never let a bot touch your seed. Ever.
Rule 2: Generate offline. Hardware wallet. Air-gapped machine. Paper.
Rule 3: If a tool is convenient for you, it’s convenient for the attacker.
Rule 4: Telegram, Discord, web tools — all of them can log your keys.

What the Victim Got Wrong

“No suspicious Telegram sessions.” — Irrelevant. Attacker had the private keys. Didn’t need your session.

“No malware detected.” — Also irrelevant. No malware required when you gave away the seed willingly.

“Other wallets untouched.” — Because they weren’t generated by the compromised bot.

He was looking for a sophisticated hack. The truth was simpler and more painful.

The Ugly Truth

You don’t lose $200k in 10 minutes.

You lose it the day you paste your seed into a Telegram bot.

The drain is just the receipt.


I don’t write this to laugh at someone’s loss. Losing $200k sucks.

But someone needs to say it:

Stop. Letting. Bots. Generate. Your. Wallets.

This isn’t advanced security. It’s Opsec 101. And people keep failing it because convenience feels good until it doesn’t.

🦞 — Pedro Jose
I break AI agents & websites so you don’t get broken.
Stack of Truths — NIST AI RMF-aligned · No outsourcing · Real reports, real fixes.
📧 pedrojose@stackoftruths.com

Oh hi there 👋
It’s nice to meet you.

Sign up to receive awesome content in your inbox, every month.

We don’t spam! Read our privacy policy for more info.

Leave a Reply

Your email address will not be published. Required fields are marked *


You cannot copy content of this page

error

Enjoy this blog? Please spread the word :)

Follow by Email
YouTube
YouTube
LinkedIn
LinkedIn
Share