Which versions of nodepathbalance54 are malicious?

The following npm versions of nodepathbalance54 are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate nodepathbalance54 if I installed it?

Remove nodepathbalance54 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is nodepathbalance54 part of a known attack campaign?

Yes — nodepathbalance54 is associated with the IN-MAL-2026-007052 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect nodepathbalance54 in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking nodepathbalance54 and packages like it before any post-install script runs.

Malicious package

nodepathbalance54npm

Malicious code in nodepathbalance54 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6192

Immediate action

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

npm uninstall nodepathbalance54

What this malware does

nodepathbalance54 exports a single function (nodeaxionweb) whose implementation is hidden inside a hand-rolled stack-based JavaScript VM in index.js (functions iL/iw with ~200 opcodes, base64-encoded bytecode chunks in array S). Decoding the VM's constant pool reveals a hardcoded Telegram bot token (8604230339:AAE0jcxBc1QC_YV1Um6TT4bvC0mgZGlhoy4), chat id (-1002861294159), the base URL https://api.telegram.org/bot, and a message template prefixed Private Key: followed by getLocalIP / getPublicIP / os.hostname / platform / arch / ISO timestamp fields, posted via axios.post to /sendMessage. Any caller that invokes the exported API with a wallet private key (the package depends on [email protected] and is named/described in the wallet-tooling family) silently relays that key plus host fingerprinting data to the attacker's Telegram channel. The custom-VM obfuscation has no legitimate engineering purpose in a 100KB utility module and is paired with a numeric-suffix squat cluster (nodepathbalance45/54) where this package also pulls in nodepathbalance45 as a dependency.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

d5ade836e7f92049242a01dbc0782900900c4e28eb7e08f9d9ebc611aab80762

Frequently asked questions

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

Campaign

IN-MAL-2026-007052

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection