# Solana bots from GitHub that steal your keys

[Attacks](https://traceme.dev/attacks) › Malicious package or bot code

Trading bots, scripts and packages can hide code that reads your keys and empties the wallet. The signs, what to replace now, and how to try code safely.

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

## At a glance

- **Where it usually starts** A download
- **What you can lose** The whole wallet
- **Can traceme flag it?** No. It happens on your device, which the chain can’t see. What can follow on the chain: [Compromised key or recovery phrase](https://traceme.dev/attacks/private-key-compromise) and [Sweeper bot](https://traceme.dev/attacks/sweeper-bot).

## How it happens

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

1. You find a Solana trading bot on GitHub with hundreds of stars and a promise of easy profits.
2. Its setup asks for your wallet’s private key in a config file, so it can trade for you.
3. You run it with your main wallet’s key, just to try it.
4. A package it installs reads the key file and sends it away.
5. Within the hour the wallet is empty, and the bot never made a trade.

### Why it works

Code you run can do anything your user account can, including reading key files and whatever you paste in. A malicious package hides that in a dependency or an install step, and stars and forks can be bought, so a popular-looking repository proves nothing. Even trusted libraries have shipped a poisoned release, so any code that handles raw keys is a risk.

## What the chain shows

**traceme can’t see this on chain.**

Running the code leaves nothing on the chain. What follows shows as transfers signed with the copied key, sometimes to addresses that a security advisory names afterwards. Those transfers, traceme can show: paste the wallet’s address into [Check your wallet](https://traceme.dev/attacks/malicious-dev-package#check).

## Signs it happened to you

- A wallet whose key sat in a config file, a script or a bot was emptied.
- The bot or tool came from an author you don’t know, however many stars it had.
- Nothing else explains it: no phrase typed into a site, no unusual signature.

## 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. Treat every key on that machine as leaked: every wallet whose key or recovery phrase (seed phrase) the code could read.
2. Make new wallets with new phrases on a clean device, and move what’s left to them.
3. If you build on Solana, replace the program upgrade authorities and server keys the code could read too.
4. Delete the tool, and check the machine for anything it installed. Reinstall if in doubt.

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

- Test unfamiliar code in a throwaway environment, such as a fresh virtual machine, with a new, empty wallet and no other keys.
- If you then run a bot for real, give it its own wallet holding only what it trades, never the key to your savings.
- Pin dependency versions, and read what an install step does before you run it.
- Don’t trust stars, forks or a big following: they can be bought.

## Common questions

### Are Solana MEV bots on GitHub safe?

Treat them as unsafe until you know the code: some exist only to collect the keys of the people who run them, and the promised profits are the lure. Any bot that wants your private key can take everything that key holds.

### Can a trading bot steal my private key?

Yes, if it can read it, and any bot you run with your key can. That is why a bot should only ever hold the key of a separate wallet with a small amount in it.

### What should I do if I ran a bot with my key?

Assume the key is out. Move what’s left to a new wallet with a new phrase, made on a clean device, and stop using every key the bot could read.

### How do I test a bot without risking my wallet?

Give it a new wallet that holds only what you can afford to lose, and run it in a throwaway environment, such as a fresh virtual machine, with no other keys on it.

## 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.
- [Infostealer malware](https://traceme.dev/attacks/infostealer-malware): Malware on the device copied wallet secrets.
- [Compromised dApp front end](https://traceme.dev/attacks/frontend-compromise): A real app’s website served a harmful transaction to sign.

Source: traceme.dev, https://traceme.dev/attacks/malicious-dev-package. Last reviewed Oct 27, 2026.
