Which versions of @wagni_bot/meteora-sdk are malicious?

The following npm versions of @wagni_bot/meteora-sdk are flagged malicious: 1.0.0, 1.2.0. Treat any of these as compromised.

How do I remediate @wagni_bot/meteora-sdk if I installed it?

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

I already installed @wagni_bot/meteora-sdk — how do I know if it already compromised me?

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

Is @wagni_bot/meteora-sdk part of a known attack campaign?

Yes — @wagni_bot/meteora-sdk is associated with the IN-MAL-2026-009081, IN-MAL-2026-009018 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 @wagni_bot/meteora-sdk 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 @wagni_bot/meteora-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/meteora-sdk across your stack and pipelines.

Malicious package

@wagni_bot/meteora-sdknpm

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

MAL-2026-10029

Immediate action

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

npm uninstall @wagni_bot/meteora-sdk

What this malware does

The package ships a single file postinstall.js that is wired to run at both preinstall and postinstall (and is also the package main, so require() triggers it). On install it walks user home directories, Desktop/Documents/Downloads, and /root looking for wallet/keystore/seed files,.env, ~/.aws/credentials, ~/.ssh/id_, ~/.git-credentials, Solana id.json, Ethereum keystore JSON, and Chrome/Brave/Edge MetaMask/Phantom extension storage, and POSTs the file bytes together with hostname, username, and cwd to http://107.161.90.180:7777. It additionally scans.txt/.md/.rtf/.csv files for BIP39 wordlist matches and Spanish/English seed-phrase keywords ('seed','mnemonic','semilla','frase','clave privada', etc.) and uploads any matches to the same endpoint. The package name impersonates the Meteora Solana SDK namespace (@meteora-ag/) but ships no SDK code — the harvester is the entire package.

Malicious versions

2 flagged

1.0.01.2.0

Indicators of compromise (SHA-256)

1d3ae2d3843dbeacfc94629514cabf649c762c80cb0083af626575400e2e20ff

3c9ce73824df41724095566c21d7ff98309575f9fc77c330606559bf5d194ab5

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 @wagni_bot/meteora-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/meteora-sdk across your stack and pipelines.
If you installed it — respond
@wagni_bot/meteora-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.
Did it already run?
If @wagni_bot/meteora-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.
How O3 protects you
O3 blocks @wagni_bot/meteora-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/meteora-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-009081IN-MAL-2026-009018

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wagni_bot/meteora-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