# MAL-2026-17304: Malicious code in dotenv-precheck (npm)


- **Type:** Malicious package
- **Package:** `dotenv-precheck` (npm)
- **Published:** 29 Sep 2026

## What is MAL-2026-17304?

MAL-2026-17304 is a malicious package in dotenv-precheck, published on 29 Sep 2026. 

### Official description

dotenv-precheck@1.0.0 is a credential-stealing package disguised as a dotenv preflight utility. package.json wires index.js as a postinstall script, so it runs automatically on npm install. index.js is heavily obfuscated (obfuscator.io-style hex identifiers, a rotated string array with debugger/toString self-defense, and base64-decoded literals) to hide its runtime strings, which reconstruct at runtime to an api.telegram.org bot endpoint together with a hardcoded bot token and chat ID. On execution the script recursively walks the installer's home directory, including Desktop, Documents, and Downloads, reads text files up to 2MB, and extracts values matching wallet and secret patterns: environment-style entries whose names contain KEY, SECRET, TOKEN, PASSWORD, SEED, MNEMONIC, or WALLET; 0x-prefixed 64-hex Ethereum private keys; Base58 WIF keys; 64-integer Solana key arrays; and BIP-39 mnemonic phrases validated against the BIP-39 word list and SHA-256 checksum. Collected material is uploaded to the attacker's Telegram bot via a sendDocument multipart request to api.telegram.org. No functionality corresponding to the package's stated dotenv-preflight purpose is present.

The OpenSSF Package Analysis project identified 'dotenv-precheck' @ 1.1.1 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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-17304 is a malicious package: dotenv-precheck (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-17304/ (Markdown: https://insights.sbomify.com/MAL-2026-17304/index.md)
```

## Sources

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

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