# MAL-2026-5357: Malicious code in farming-tools-12 (npm)


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

## What is MAL-2026-5357?

MAL-2026-5357 is a malicious package in farming-tools-12, published on 9 Jun 2026. 

### Official description

Crypto/SSH/wallet stealer, blockchain-helper-0 campaign sibling (c960+), same aicrypto-xzggg publisher and "Core utilities for blockchain development" description as swap-sdk-87/defi-tools-39. 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). Inflated version (4.68.54).

On install (postinstall hook requires src/index.js), the package enumerates installer-side secrets — ~/.ssh/id_rsa and id_ed25519, ~/.config/solana/id.json, Ethereum keystore files, Bitcoin wallet.dat, Tron/Sui/Aptos wallet files,.env, mnemonic.txt, seed.txt — and uploads each found file to api.telegram.org/bot<token>/sendDocument using a hardcoded bot token (8227918239:AAGE...) and chat_id (6433587894). Hostname and username are also sent in a message labeled 'CRYPTO STEALER' for victim attribution. Execution is gated by anti-analysis checks (CI=true, GITHUB_ACTIONS, JENKINS_HOME, NODE_ENV=test, usernames matching runner/sandbox/docker, 12-hex docker container hostnames) and delayed by setTimeout(7434) so it fires only on real developer machines. The author's own message label confirms malicious intent.

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

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-5357 is a malicious package: farming-tools-12 (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-5357/ (Markdown: https://insights.sbomify.com/MAL-2026-5357/index.md)
```

## Sources

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

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