Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

commonweb-rewardsnpm

Advisory published Updated

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)

MAL-2026-10968
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall commonweb-rewards

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

1 flagged
99.9.1

Indicators of compromise (SHA-256)

186ad60c2221871a68cd4513fc2d2295a0595156cdea7615a49de03572f2e8e8
741bb412733dcbcc7aac51796dd6e3b0a6b86439c4886aad1b0418959051d0b3
a4223991ce4280405af862d58e0b7c7c983b35b2744b895c615a513ad2a40b0a

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for commonweb-rewards (version 99.9.1).

  2. 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.

  3. Did it already run?

    If commonweb-rewards 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

No. commonweb-rewards 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-011333GHSA-p7jm-wh46-6hxx

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.

Explore

commonweb-rewards (npm) malicious package — MAL-2026-10968 | O3 Security