consumerweb-calurlsnpm
Advisory published Updated
consumerweb-calurls is a confirmed malicious npm package (MAL-2026-10970) 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 consumerweb-calurls (npm)
What this malware does
[email protected] ships an effectively empty package (empty index.js, no lifecycle scripts) whose sole effect on install is to resolve a runtime dependency ltidisafe from a direct tarball URL on an anonymous Google Cloud Storage bucket at https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.5.6.tgz rather than from the npm registry. The GCS bucket is not npm, not a documented publisher domain, and the URL carries no integrity hash, so the bucket owner can swap the tarball contents at any time. On npm install, npm fetches this tarball and executes its lifecycle scripts and main module inside the installer's dependency graph, bypassing npm registry scanning. The version number 99.9.1 and the hollow contents are consistent with a lure package whose only purpose is to introduce the off-registry 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.
The OpenSSF Package Analysis project identified 'consumerweb-calurls' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for consumerweb-calurls (version 99.9.1).
If you installed it — respond
Remove consumerweb-calurls 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 consumerweb-calurls 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks consumerweb-calurls-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.