commonweb-cardnpm
commonweb-card is a confirmed malicious npm package (MAL-2026-10966) 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-card (npm)
What this malware does
[email protected] ships an effectively empty main module (index.js exports an empty object) and its package.json declares a dependency 'ltidisafe' whose version specifier is a direct HTTPS tarball URL to an anonymous Google Cloud Storage bucket: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.5.2.tgz. On npm install, npm downloads and installs the tarball at that URL and executes any lifecycle scripts (preinstall/install/postinstall) and top-level require side effects it contains. The tarball host is not the npm registry, not a documented vendor publisher, and not tied to the wrapper package's stated identity; its contents are controlled solely by whoever owns the GCS bucket and can be mutated at any time without a package version bump. The high version number (99.9.1) combined with a hollow wrapper and a remote tarball dependency matches the dependency-confusion loader 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.
The OpenSSF Package Analysis project identified 'commonweb-card' @ 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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commonweb-card (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-card across your stack and pipelines.
If you installed it — respond
Remove commonweb-card 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-card 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-card 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks commonweb-card-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.