commonweb-walletnpm
commonweb-wallet is a confirmed malicious npm package (MAL-2026-10969) that steals credentials and exfiltrates sensitive data (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in commonweb-wallet (npm)
What this malware does
[email protected] is an empty wrapper (index.js is module.exports = {}; package.json has empty author/description and an implausible 99.9.1 version) whose sole dependency ltidisafe is declared as a direct HTTPS tarball URL pointing at a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.5.1.tgz) unrelated to any known npm publisher. On npm install, npm downloads and installs that off-registry tarball into the installer's node_modules and executes its lifecycle hooks and require()-time code. The bucket contents are mutable, unpinned by hash, and not subject to npm registry integrity or provenance checks, so whatever bytes are served at install time run on the installer's machine. The wrapper contributes no functionality of its own; its only effect is to smuggle attacker-controlled code into the dependency tree of anyone installing this wallet-named package.
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-wallet' @ 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
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commonweb-wallet (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-wallet across your stack and pipelines.
If you installed it — respond
commonweb-wallet 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 commonweb-wallet 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-wallet 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-wallet-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.