commonweb-balancenpm
Advisory published Updated
commonweb-balance is a confirmed malicious npm package (MAL-2026-13439) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in commonweb-balance (npm)
What this malware does
[email protected] is an empty shell package (empty index.js, no functionality) whose only effect on install is resolving its single declared runtime dependency ltidisafe from a direct tarball URL at https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.5.tgz rather than from the npm registry. On npm install, npm downloads and installs whatever bytes are served at that URL into the installer's node_modules, bringing that code into the dependency tree outside npm registry review. The GCS bucket is publisher-unrelated (no matching author or homepage metadata on the host package) and mutable — whoever controls the bucket can change the served tarball contents at any time without republishing to npm. The host package has no legitimate function other than to pull this out-of-registry dependency into installers, matching the dependency-chain dropper / lure pattern.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for commonweb-balance (version 99.9.1).
If you installed it — respond
Remove commonweb-balance 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 activity or persistence.
Did it already run?
If commonweb-balance 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks commonweb-balance-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.