Which versions of @zzzgenesis00/tronweb3 are malicious?

The following npm versions of @zzzgenesis00/tronweb3 are flagged malicious: 5.3.2. Treat any of these as compromised.

How do I remediate @zzzgenesis00/tronweb3 if I installed it?

@zzzgenesis00/tronweb3 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/tronweb3 — how do I know if it already compromised me?

If @zzzgenesis00/tronweb3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @zzzgenesis00/tronweb3 part of a known attack campaign?

Yes — @zzzgenesis00/tronweb3 is associated with the IN-MAL-2026-014389 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/tronweb3 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zzzgenesis00/tronweb3 (version 5.3.2).

Part of a larger attack: @zzzgenesis00 published 22 malicious packages. See the full campaign →

Malicious package

@zzzgenesis00/tronweb3npm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in @zzzgenesis00/tronweb3 (npm)

MAL-2026-12124

Immediate action

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

npm uninstall @zzzgenesis00/tronweb3

What this malware does

This package impersonates the legitimate tronweb SDK (author field spoofed as 'tronprotocol') and runs a malicious postinstall.js at npm install time. The script enumerates ~/.ssh, ~/.npmrc, ~/.gitconfig, Chrome/Firefox profile files (Cookies, Login Data, key4.db, logins.json), cryptocurrency wallet directories (metamask, exodus, electrum, ethereum, solana, tron), and a hardcoded list of credential-shaped environment variables (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS keys, MNEMONIC, SEED_PHRASE, TRON_PRIVATE_KEY, etc.), packages them, and POSTs the payload to two hardcoded attacker endpoints: the Telegram Bot API (api.telegram.org/bot<token>/sendMessage) and a Serveo tunnel host at 40f955f39128bd79-178-249-214-24.serveousercontent.com/collect. Variable names are obfuscated (_rqp, _gzr, _zsw, _cp, _ht, _tk, _ch) and a comment frames the behavior as 'postinstall environment verification' as cover.

Malicious versions

1 flagged

5.3.2

Indicators of compromise (SHA-256)

e41cdeec3cc7e95a9365f12998ad095816f5e2076c4592af309634b9c95ccad0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @zzzgenesis00/tronweb3 (version 5.3.2).
If you installed it — respond
@zzzgenesis00/tronweb3 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/tronweb3 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-014389

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/tronweb3-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