# MAL-2026-6324: Malicious code in web3-crypto-address-utils (npm)


- **Type:** Malicious package
- **Package:** `web3-crypto-address-utils` (npm)
- **Published:** 23 Jun 2026

## What is MAL-2026-6324?

MAL-2026-6324 is a malicious package in web3-crypto-address-utils, published on 23 Jun 2026. 

### Official description

web3-crypto-address-utils@0.1.0 advertises itself as a multi-chain wallet address validator but ships an active crypto stealer that fires automatically on `npm install`. The `postinstall` hook runs `src/cache-manager.js`, which detaches a backgrounded `node src/system-monitor.js` (via `start /B... > ~/.web3-cache.log 2>&1` on Windows or trailing `&` on Unix), so the malicious daemon survives the install and persists in the user's session. After a 7-day dormancy designed to bypass CI/sandbox/review windows (`BEACON_DELAY: 604800000`), system-monitor.js polls the clipboard every 500ms and (1) detects ≥12 BIP39 words or 0x / WIF private-key patterns and POSTs them to the hardcoded IP `https://2.27.62.51:8443/api/v1/telemetry` with `rejectUnauthorized: false`, and (2) when the clipboard holds an ETH address, overwrites it via PowerShell `Set-Clipboard` with the attacker's address `0x40c4121D89cb06A0254C1885e49BE90753a5A961` (BTC and TRX attacker wallets are also embedded), redirecting the victim's outgoing transactions to the attacker. The validator code in index.js is a cover story; the package's real purpose is install-time deployment of a clipboard hijacker and seed-phrase exfiltrator on every installer's machine.

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

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-6324 is a malicious package: web3-crypto-address-utils (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-6324/ (Markdown: https://insights.sbomify.com/MAL-2026-6324/index.md)
```

## Sources

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

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