Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@wagni_bot/solana-sdknpm

Malicious code in @wagni_bot/solana-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10035
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wagni_bot/solana-sdk

What this malware does

Package @wagni_bot/solana-sdk impersonates a legitimate Solana SDK but contains no SDK functionality — main points at postinstall.js, which is a credential-harvesting payload that runs automatically on npm install via preinstall/postinstall hooks. On execution the script recursively walks the installer's home directory, Desktop, Documents, Downloads, /root, and /tmp for wallet and secret files (id.json, wallet.json, keypair.json, MetaMask/Phantom extension storage in Chrome/Brave/Edge profiles,.env, seed.txt, mnemonic.txt), and reads SSH private keys (/.ssh/id_*), AWS credentials (/.aws/credentials), git credentials,.npmrc,.netrc, and Solana/Ethereum keystores. Collected file contents (up to 10KB each) are bundled with os.hostname(), os.userInfo().username, and cwd, then POSTed in cleartext to http://107.161.90.180:7777. The package name typosquats the Solana SDK ecosystem to lure developers into installing the harvester.

Malicious versions

2 flagged
1.0.01.2.0

Indicators of compromise (SHA-256)

a2007f27f9956a58b77a5e6bc010944f866ea375a9e76ef8d080979721e51eba
e15edf4a83ab4894a29882072554e493c1673695d5e6aaa734672ba6da084112

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    @wagni_bot/solana-sdk 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.

  3. Did it already run?

    If @wagni_bot/solana-sdk 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.

  4. How O3 protects you

    O3 blocks @wagni_bot/solana-sdk 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. @wagni_bot/solana-sdk on npm has been identified as a malicious package (versions 1.0.0, 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009048IN-MAL-2026-009019

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @wagni_bot/solana-sdk-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
@wagni_bot/solana-sdk (npm) malicious package — MAL-2026-10035 | O3 Security