Which versions of commonweb-balance are malicious?

The following npm versions of commonweb-balance are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate commonweb-balance if I installed it?

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.

I already installed commonweb-balance — how do I know if it already compromised me?

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

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

Malicious package

commonweb-balancenpm

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)

MAL-2026-13439

Immediate action

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

npm uninstall commonweb-balance

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

7455a26ab96be134244f14c67b9e3fbf63033f1b974cf45ad0620d5a6eda0581

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commonweb-balance (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commonweb-balance across your stack and pipelines.
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 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 commonweb-balance 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. commonweb-balance on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016672

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database