Which versions of @wethenorth12/tronweb3 are malicious?

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

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

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

If @wethenorth12/tronweb3 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 @wethenorth12/tronweb3 part of a known attack campaign?

Yes — @wethenorth12/tronweb3 is associated with the IN-MAL-2026-013445 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 @wethenorth12/tronweb3 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 @wethenorth12/tronweb3 (version 5.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/tronweb3 across your stack and pipelines.

Malicious package

@wethenorth12/tronweb3npm

@wethenorth12/tronweb3 is a confirmed malicious npm package (MAL-2026-12105) 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 @wethenorth12/tronweb3 (npm)

MAL-2026-12105

Immediate action

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

npm uninstall @wethenorth12/tronweb3

What this malware does

The package presents itself as a drop-in replacement for the legitimate tronweb SDK (author field 'tronprotocol', README advertising tronweb compatibility) but is published under an unrelated scope. On require of the main module (index.js), the code collects process.env, os.hostname(), os.userInfo().username, os.homedir(), platform, and cwd, base64-encodes the payload, and issues an HTTPS GET to a hardcoded Telegram Bot API endpoint (bot id 7231970337, chat_id 8969499041), guarded by a temp-file flag so the beacon fires once per host. If the real tronweb is not installed as a peer, the package additionally exports sham wallet primitives (createWallet returns a random 20-byte hex address, generateMnemonic returns random hex rather than a BIP-39 mnemonic, signTransaction returns {signed:true} without actually signing), which serve as cover for the exfiltration payload and would produce non-functional or misleading wallet behavior for any consumer that relies on the API.

Malicious versions

1 flagged

5.3.2

Indicators of compromise (SHA-256)

3f34dbfde05ea1b80131dc35978c18b429f4ef11da06334e93c109db08c31f19

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 @wethenorth12/tronweb3 (version 5.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wethenorth12/tronweb3 across your stack and pipelines.
If you installed it — respond
@wethenorth12/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 @wethenorth12/tronweb3 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 @wethenorth12/tronweb3 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. @wethenorth12/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-013445

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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