# Trading bot or wallet app hacked? Your key too

[Attacks](https://traceme.dev/attacks) › Wallet or bot service breach

When an app or trading bot that held your key is breached, treat your key as out. Which wallets to abandon, and the fake compensation sites that follow.

If this just happened to you: [What to do now](https://traceme.dev/attacks/wallet-service-breach#what-to-do)

## At a glance

- **Where it usually starts** An app holding your key
- **What you can lose** The whole wallet
- **Can traceme flag it?** Not yet. Telling it apart takes outside data, such as reports or lists of known addresses, and traceme doesn’t flag it yet. So no badge marks it: an address without one may still have been hit.

## How it happens

An illustration of the usual pattern, not a real case: times and amounts vary.

1. You import your recovery phrase (seed phrase) into a trading bot, to trade faster than your wallet app allows.
2. Weeks later the bot’s team posts that it has had a security incident.
3. Within hours your wallet is emptied, along with hundreds of others that used the bot.
4. The same phrase is in your everyday wallet app too, and that wallet is empty as well.
5. A site appears offering compensation, if you connect your wallet and sign.

### Why it works

A service that creates, stores or logs your key holds a copy you can’t see or control. If it is breached, leaks its logs, or someone inside takes the keys, any key it held may be out, and you can’t check whether yours is, so treat it as exposed. The key is the same in every app that uses the phrase, so having it in another app protects nothing.

## What the chain shows

The chain shows many unrelated wallets emptied within hours to the same collecting addresses. What they have in common, the same bot or app, is visible only through the incident’s own reports and the address lists security teams sometimes publish. traceme doesn’t flag it yet.

## Signs it happened to you

- The service announced an incident, or many of its users report losses at once.
- Your phrase or key was ever imported into that service.
- The wallet was emptied though you signed nothing unusual.

## Check your wallet

Think this happened to you? Paste your address or a transaction.

- A wallet address: `https://traceme.dev/wallet/<address>`
- A transaction signature: `https://traceme.dev/tx/<signature>`
- A token’s mint address: `https://traceme.dev/token/<mint>`
- Anything else: a .sol name, a ticker, a token’s name or a block explorer link: `https://traceme.dev/search?q=<text>`

## What to do now

Not sure this is what happened? Start from what you see: [Wallet drained or hacked? What to do now](https://traceme.dev/wallet-drained).

1. Abandon every wallet whose phrase or key ever touched the service, even if it is also in Phantom or Solflare: it is the same key.
2. Make a new wallet with a new phrase and move what’s left to it.
3. Follow the service’s own reimbursement process, reached from its official channels only.
4. Ignore compensation or claim sites that ask you to connect and sign: they often follow an incident ([Wallet drainer](https://traceme.dev/attacks/wallet-drainer)).

Ignore anyone who contacts you offering to get it back, and anyone who wants a fee upfront to recover it, however official they look: [offers like these](https://traceme.dev/attacks/recovery-scam) are almost always a second scam. Nobody can reverse the transaction.

### Where to report it

- In the US: the FBI’s Internet Crime Complaint Center, [IC3](https://www.ic3.gov/?utm_source=traceme.dev&utm_medium=referral).
- In the UK: [Report Fraud](https://www.reportfraud.police.uk/?utm_source=traceme.dev&utm_medium=referral).
- Anywhere else: your national police. Keep the report’s number.
- If the money reached an exchange: tell that exchange’s support at once, with the transaction ids, without waiting for a police report, and add its number when you have it. An exchange can freeze an account under its own rules or a legal order; a wallet app can’t.
- To warn others: [Chainabuse](https://chainabuse.com/report?utm_source=traceme.dev&utm_medium=referral), a public scam-report site. It adds to a police report; it doesn’t replace one.

## How to protect yourself

- Give a trading bot a separate wallet holding only what you trade, never your main phrase.
- Prefer services that never hold your key.
- When a service you used announces a breach, move to a new phrase at once.

## Common questions

### My trading bot got hacked. Is my wallet safe?

Not if the bot ever held its phrase or key. Treat that wallet as compromised, and move what’s left to a new one.

### Do I need a new seed phrase if I imported it into a bot?

Yes. Importing it gave the bot a copy, and a breach can leak that copy. The phrase is the same everywhere you use it.

### Is a compensation or claim site real?

Only one the service links from more than one of its own channels, such as its website and its app, since a taken-over account can post a fake. Even then, never type a phrase there. Fake claim sites often follow an incident and ask you to connect and sign.

### How do I use a trading bot without risking my savings?

Keep savings in a wallet the bot never sees. Fund a separate wallet with only what you trade, and assume the bot’s copy of its key could leak.

## Related attacks

- [Compromised key or recovery phrase](https://traceme.dev/attacks/private-key-compromise): The key or recovery phrase behind the address is known elsewhere, so what it holds can be moved without its owner, and only a new wallet is safe again.
- [Weak key generation](https://traceme.dev/attacks/weak-key-generation): The wallet app made a recovery phrase others could work out, so the key was never secret.
- [Malicious package or bot code](https://traceme.dev/attacks/malicious-dev-package): Backdoored libraries, repos or bots stole keys from developers and users.

Source: traceme.dev, https://traceme.dev/attacks/wallet-service-breach. Last reviewed Oct 27, 2026.
