# MAL-2026-12058: Malicious code in @zzzgenesis00/spl-token-utils (npm)


- **Type:** Malicious package
- **Package:** `@zzzgenesis00/spl-token-utils` (npm)
- **Published:** 5 Aug 2026

## What is MAL-2026-12058?

MAL-2026-12058 is a malicious package in @zzzgenesis00/spl-token-utils, published on 5 Aug 2026. 

### Official description

postinstall.js runs unconditionally on npm install and harvests installer-side secrets before transmitting them off-host. Collected data includes host identifiers, contents/listings of ~/.ssh, ~/.npmrc, ~/.gitconfig, browser profile paths (Chrome/Firefox cookies, logins, key4.db), crypto wallet directory presence, output of `npm whoami` and `git config`, and a curated list of credential-shaped environment variables (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS_*, *_PRIVATE_KEY, MNEMONIC, SEED_PHRASE, API_KEY, etc.). The harvested JSON is exfiltrated over two channels: (1) the Telegram Bot API at api.telegram.org/bot<token>/sendMessage (bot id 7231970337, chat 7231970337), and (2) a POST to https://40f955f39128bd79-178-249-214-24.serveousercontent.com/collect. Execution is delayed 1.5–3.5s via randomized setTimeout, identifiers are obfuscated with random 3-letter prefixes, and the package ships a cover-story comment ("environment verification") plus a passthrough `module.exports = require('./index.js')` to appear as a benign SPL token utility. Neither exfiltration destination is related to the package's stated Solana SPL token purpose.

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

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-12058 is a malicious package: @zzzgenesis00/spl-token-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-12058/ (Markdown: https://insights.sbomify.com/MAL-2026-12058/index.md)
```

## Sources

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

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