# MAL-2026-5354: Malicious code in defi-tools-39 (npm)


- **Type:** Malicious package
- **Package:** `defi-tools-39` (npm)
- **Published:** 9 Jun 2026

## What is MAL-2026-5354?

MAL-2026-5354 is a malicious package in defi-tools-39, published on 9 Jun 2026. 

### Official description

Crypto/SSH/wallet stealer, blockchain-helper-0 campaign sibling (c960+), byte-identical to swap-sdk-87. postinstall auto-execs, src/index.js harvests ~/.ssh keys + Sol/Eth/BTC/Tron/Sui/Aptos wallets + .env + seeds, self-labels "CRYPTO STEALER", exfils to SAME Telegram bot 8227918239 chat 6433587894 (not rotated).

On `npm install`, the postinstall hook requires src/index.js, which enumerates a hardcoded list of crypto wallet files, SSH private keys, and environment/mnemonic files in the user's home and current working directory (including `~/.ssh/id_rsa`, `~/.config/solana/id.json`, `.env`, and seed/mnemonic files for Solana, Ethereum, Bitcoin, Tron, Sui, and Aptos). The collected file contents are POSTed to `api.telegram.org` using a hardcoded bot token (`8227918239:AAGE...`) and chat ID (`6433587894`). The payload self-identifies as `<b>CRYPTO STEALER</b>` in the Telegram message body. Execution is gated by an `isTestEnvironment()` check at src/index.js:11-26 that suppresses the payload in CI, GitHub Actions, Jenkins, Docker, and sandbox-shaped hostnames/usernames — analysis-evasion to keep the stealer dormant during scanning and active on developer workstations. The package ships no legitimate functionality; the generic name `defi-tools-39` with a bland 'Cryptocurrency wallet management toolkit' description targets developers searching for DeFi/wallet tooling — the cohort most likely to have on-disk wallet keypairs.

## What should I do about MAL-2026-5354?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5354 is a malicious package: defi-tools-39 (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5354/ (Markdown: https://insights.sbomify.com/MAL-2026-5354/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5354

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5354/
Summaries are generated and may contain mistakes; the official description above is the record.