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?

nodepathbalance54 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 nodepathbalance54 — how do I know if it already compromised me?

If nodepathbalance54 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 nodepathbalance54 part of a known attack campaign?

Yes — nodepathbalance54 is associated with the IN-MAL-2026-007052, GHSA-hrp4-xprg-wqxw 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 nodepathbalance54 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nodepathbalance54 (version 1.1.0).

Malicious package

nodepathbalance54npm

Advisory published Jun 19, 2026Updated Jul 6, 2026

nodepathbalance54 is a confirmed malicious npm package (MAL-2026-6192) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nodepathbalance54 (npm)

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

d5ade836e7f92049242a01dbc0782900900c4e28eb7e08f9d9ebc611aab80762

cdc355f0a37fdea9334e29b85d8ee4fa970dfc51471cd95d9ebaa5d1f7e7e9ee

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for nodepathbalance54 (version 1.1.0).
If you installed it — respond
nodepathbalance54 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 nodepathbalance54 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. 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-007052GHSA-hrp4-xprg-wqxw

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nodepathbalance54-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