Malicious Solana bot masquerading as Pump.fun tool drains wallets in GitHub scam

A malicious Solana bot disguised as a popular Pump.fun trading tool has surfaced on GitHub, draining unsuspecting users’ crypto wallets, cybersecurity firm SlowMist revealed.

The attack is the latest example of how open-source platforms can be weaponized to exploit the decentralized finance (DeFi) space.

This malicious Solana bot incident began when a user downloaded what appeared to be a benign Node.js app claiming to facilitate Solana-based token trading via Pump.fun. But instead of offering any functionality, it silently compromised the user’s wallet, leading to the complete theft of their assets.

GitHub deception: A trojan horse in open source

The bogus project masquerading as a legitimate Pump.fun bot was uploaded to GitHub, gaining apparent credibility through stars and interactions from fake GitHub accounts.

The malicious Solana bot was cleverly engineered to gain trust by mimicking the behavior and branding of real crypto tools.

Cybersecurity experts at SlowMist explained that the Node.js project contained a dependency that fetched code from an external GitHub repository, bypassing typical NPM registry checks.

“This is a textbook method cybercriminals use to smuggle malicious code undetected,” said Yu Xian, founder of SlowMist. “The malicious Solana bot used a custom GitHub link to avoid scrutiny, a tactic we’ve seen growing across DeFi-related exploits.”

Once downloaded and executed, the malicious Solana bot scanned the victim’s system for crypto wallet information. It then exfiltrated private keys and wallet credentials to a server controlled by the attacker.

According to SlowMist’s technical breakdown, the attack vector included a rogue JavaScript package nested inside dependencies that appeared harmless. This allowed it to fly under the radar until it was too late.

“The script harvested sensitive data and transferred it instantly. The victim had no chance to act before the wallet was completely drained,” SlowMist stated in a detailed report on X.

Fake popularity, real consequences

One disturbing aspect of this malicious Solana bot scam was the use of artificially inflated GitHub activity to fake credibility.

Attackers created multiple bogus accounts to star, fork, and comment on the project—making it appear legitimate to average users.

This social engineering tactic is becoming increasingly common in crypto-related scams, where users often rely on GitHub metrics to judge a project’s safety.

“It’s a brutal reminder that trust signals on GitHub can be manufactured,” warned PeckShield, another blockchain security firm. “Always vet the code and verify dependencies—don’t rely solely on stars or forks.”

SlowMist emphasized that GitHub should not be viewed as a safe haven by default. The malicious Solana bot example is a wake-up call for developers and traders alike to reassess their approach to open-source security.

“Never blindly trust GitHub repositories, especially those claiming to offer trading bots or wallet tools,” SlowMist advised. “Examine code carefully or run it in isolated environments.”

The firm is now working with other cybersecurity entities to track down the threat actor and coordinate takedowns of similar repositories.

Solana users urged to stay vigilant

As the popularity of Solana-based platforms grows, so does the attack surface. The malicious Solana bot exploit highlights the need for better education around operational security (OpSec) when handling digital wallets.

Experts recommend:

• Verifying all GitHub dependencies manually

• Avoiding unofficial bots or trading tools

• Using hardware wallets to store funds offline

• Employing sandboxed environments when testing open-source code

The exposure of the malicious Solana bot on GitHub is yet another harsh reminder that even trusted platforms can host dangerous code.

As open-source continues to power innovation in crypto, security practices must evolve to prevent such catastrophic losses.

Cybercriminals are innovating just as fast as the blockchain space is growing. Users must stay alert, and security must be built into every layer—from code to clicks.