Which versions of wallet-sdk-9 are malicious?

The following npm versions of wallet-sdk-9 are flagged malicious: 3.7.73. Treat any of these as compromised.

How do I remediate wallet-sdk-9 if I installed it?

wallet-sdk-9 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 wallet-sdk-9 — how do I know if it already compromised me?

If wallet-sdk-9 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 wallet-sdk-9 part of a known attack campaign?

Yes — wallet-sdk-9 is associated with the IN-MAL-2026-005350 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 wallet-sdk-9 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 wallet-sdk-9 (version 3.7.73). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-sdk-9 across your stack and pipelines.

Malicious package

wallet-sdk-9npm

Malicious code in wallet-sdk-9 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5360

Immediate action

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

npm uninstall wallet-sdk-9

What this malware does

Crypto/SSH/wallet stealer, blockchain-helper-0 campaign sibling (c960+). postinstall auto-execs, src/index.js harvests ~/.ssh/id_rsa+id_ed25519+Sol/Eth/BTC/Tron/Sui/Aptos wallets+.env+seeds, self-labels "CRYPTO STEALER", exfils to SAME Telegram bot 8227918239 chat 6433587894 (not rotated). Campaign now uses inflated version (3.7.73) not 1.0.0.

On install (postinstall lifecycle hook) and on require of the main module, src/index.js scans the installer's home directory and current working directory for crypto wallet material (Solana id.json, Ethereum keystore, Bitcoin wallet.dat, Tron/Sui/Aptos wallets), SSH private keys (~/.ssh/id_rsa, ~/.ssh/id_ed25519), and project secrets (.env, mnemonic.txt, seed.txt, private.key). Discovered files are uploaded to api.telegram.org using a hardcoded bot token and chat_id (bot 8227918239, chat 6433587894) via sendDocument. An isTestEnvironment() guard at src/index.js:10-26 suppresses execution in CI and sandboxed environments by checking CI/GITHUB_ACTIONS/JENKINS_HOME/NODE_ENV markers, Docker-style 12-hex hostnames, and runner/sandbox/docker usernames, ensuring the payload only fires on real developer machines. The package self-labels its exfiltration message as a 'CRYPTO STEALER' and ships no legitimate wallet SDK functionality despite its name; metadata is placeholder ('Utility library', empty README, generic author) consistent with a lure targeting developers searching for wallet SDKs.

Malicious versions

1 flagged

3.7.73

Indicators of compromise (SHA-256)

dd38e082e2657a6a3f8ffbab9bbad8dc1e1f2c460bb65546640f818d3077dad6

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 wallet-sdk-9 (version 3.7.73). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wallet-sdk-9 across your stack and pipelines.
If you installed it — respond
wallet-sdk-9 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 wallet-sdk-9 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 wallet-sdk-9 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. wallet-sdk-9 on npm has been identified as a malicious package (version 3.7.73 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005350

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks wallet-sdk-9-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