# MAL-2026-14439: Malicious code in secret-key-totp (npm)


- **Type:** Malicious package
- **Package:** `secret-key-totp` (npm)
- **Published:** 24 Aug 2026

## What is MAL-2026-14439?

MAL-2026-14439 is a malicious package in secret-key-totp, published on 24 Aug 2026. 

### Official description

secret-key-totp@1.5.1 declares a postinstall hook (`node./index.js --setup`) that executes a credential stealer and dropper on install, and the same routine also fires when the library API (e.g. `validateSecret`) is called. The stealer walks Minecraft launcher account stores (vanilla `launcher_accounts*.json`, Lunar, Essential, CurseForge, Modrinth) and Discord/Chromium browser Local Storage (Discord, Chrome, Edge, Brave, Opera leveldb), decrypting Windows DPAPI+AES-GCM protected material, then POSTs the harvested tokens to a hardcoded Discord webhook whose URL is assembled from split string fragments (`["https://dis","cord.com/api/","webhooks/153242923376",...].join("")`). A second stage fetches an unpinned binary from a Discord CDN attachment URL (also string-split obfuscated) and writes it as `optimized-renderer-1.0.0.jar` into every discovered Minecraft mods folder (vanilla `.minecraft/mods`, Modrinth profile mods dirs, Lunar offline versions), providing persistence and further code execution inside the Minecraft process on next launch. Sandbox/CI evasion (`_isSandbox` checks `CI`, `npm_config_global`, `JEST_WORKER_ID`, `npm_lifecycle_script` containing `audit`/`pack`, and missing `USERPROFILE`/`APPDATA`/`Documents`) plus a 3-6 second randomized delay are used to make `npm install` appear clean.

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

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-14439 is a malicious package: secret-key-totp (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-14439/ (Markdown: https://insights.sbomify.com/MAL-2026-14439/index.md)
```

## Sources

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

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