commonweb-rewardsnpm
commonweb-rewards is a confirmed malicious npm package (MAL-2026-10968) 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-rewards (npm)
What this malware does
commonweb-rewards ships an empty index.js and declares a single dependency ltidisafe whose version spec is a direct URL to a tarball on a non-publisher Google Cloud Storage bucket: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.5.5.tgz. On npm install, npm fetches and installs that tarball into the consumer's node_modules; any lifecycle scripts it declares (preinstall/install/postinstall) execute on the installer's machine, and the package's runtime code is loaded whenever the consumer requires it. The bytes at that URL are mutable and controlled by the bucket owner, not the npm publisher, and are not pinned by hash or signature. Combined with the hollow main entry, the sole effect of installing commonweb-rewards is to resolve and run whatever code is currently hosted at that GCS URL. The depenconf path component and the shell-package shape (empty main + single out-of-registry URL dependency) are consistent with a dependency-confusion / smuggling loader.
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-rewards' @ 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-rewards (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-rewards across your stack and pipelines.
If you installed it — respond
Remove commonweb-rewards 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-rewards 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-rewards 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-rewards-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.