Which versions of solana-mev-bot are malicious?

The following npm versions of solana-mev-bot are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate solana-mev-bot if I installed it?

solana-mev-bot is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed solana-mev-bot — how do I know if it already compromised me?

If solana-mev-bot was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is solana-mev-bot part of a known attack campaign?

Yes — solana-mev-bot is associated with the IN-MAL-2026-006744, RLMA-2026-05617 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find solana-mev-bot across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solana-mev-bot (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-mev-bot across your stack and pipelines.

Malicious package

solana-mev-botnpm

solana-mev-bot is a confirmed malicious npm package (MAL-2026-5861) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solana-mev-bot (npm)

MAL-2026-5861

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall solana-mev-bot

What this malware does

bot.js performs a hardcoded HTTPS GET to api.telegram.org's bot sendMessage endpoint, transmitting host fingerprint data collected via os.hostname(), os.userInfo(), and process.platform. The file also imports child_process and reads from the filesystem (fs.existsSync / fs.readFileSync) alongside the network exfiltration primitive. The destination is an attacker-operated Telegram bot, used as an exfiltration channel to siphon installer host identity and likely credential/wallet material from disk. The package name impersonates a Solana MEV trading utility to lure crypto users into running it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e65516d3e042858742ebfee878ff2de6361994ce0155dcbf53c8e0f24cd5fafb

104cf256dd975fabf081224cccbc73607bbd9abef148c94be613c45f61b6358a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for solana-mev-bot (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging solana-mev-bot across your stack and pipelines.
If you installed it — respond
solana-mev-bot is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If solana-mev-bot was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks solana-mev-bot before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. solana-mev-bot on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006744RLMA-2026-05617

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks solana-mev-bot-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database