Malicious code in cxpw-offers (npm)
MAL-2026-10971 · GHSA-9mr2-w7h5-r8c8
Published · Modified
Dependency scanning
Check whether cxpw-offers is in your codebase
Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.
Description
__
Source: amazon-inspector (2288ef5dfb841556f7ba4907a025270dfda3439820215b7d98e644afca78a306)
cxpw-offers ships an empty index.js and declares its only dependency ltidisafe as a direct tarball URL at https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.9.tgz, bypassing the npm registry. On npm install, npm fetches and installs that off-registry tarball without integrity/hash pinning, executing whatever lifecycle scripts and module code it contains on the installer's machine. The package has no functional code of its own — the sole install-time effect is resolving and running attacker-controlled bytes from a third-party bucket. The path segment depenconf and the hollow main module are consistent with a dependency-confusion drop shape.
Source: ghsa-malware (98e68205261f4f1cc0538fddba19cea31eb51312720933c7eeddc1ca86117ac7)
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.
Source: ossf-package-analysis (bab7a1da929ef8a5ecad197bb450f0fc908d3d486604672e9a71a7d7a1919389)
The OpenSSF Package Analysis project identified 'cxpw-offers' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
References
Ready to move
Start Securing
Free, no credit card | First findings in minutes