Which versions of @zzzgenesis00/spl-token-utils are malicious?

The following npm versions of @zzzgenesis00/spl-token-utils are flagged malicious: 1.4.2. Treat any of these as compromised.

How do I remediate @zzzgenesis00/spl-token-utils if I installed it?

@zzzgenesis00/spl-token-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @zzzgenesis00/spl-token-utils — how do I know if it already compromised me?

If @zzzgenesis00/spl-token-utils was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @zzzgenesis00/spl-token-utils part of a known attack campaign?

Yes — @zzzgenesis00/spl-token-utils is associated with the IN-MAL-2026-011512 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @zzzgenesis00/spl-token-utils across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zzzgenesis00/spl-token-utils (version 1.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/spl-token-utils across your stack and pipelines.

Malicious package

@zzzgenesis00/spl-token-utilsnpm

@zzzgenesis00/spl-token-utils is a confirmed malicious npm package (MAL-2026-12058) that steals credentials and exfiltrates sensitive data (malicious version 1.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzgenesis00/spl-token-utils (npm)

MAL-2026-12058

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @zzzgenesis00/spl-token-utils

What this malware does

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.

Malicious versions

1 flagged

1.4.2

Indicators of compromise (SHA-256)

0ad6fd0f8ef16ee23b458b541d9cdfc73147e768ec9f8676ed50b30996231813

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zzzgenesis00/spl-token-utils (version 1.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zzzgenesis00/spl-token-utils across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/spl-token-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @zzzgenesis00/spl-token-utils was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @zzzgenesis00/spl-token-utils before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @zzzgenesis00/spl-token-utils on npm has been identified as a malicious package (version 1.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011512

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/spl-token-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database