Malicious code in @capsense/ccx-welcome-page (npm)
The advisory, in context
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (0f63b73ae5e707b0eecee16f97f8ab26b350d135547448fbf6e005ba33303060)
The package publishes under the @capsense scope at version 99.99.100 and wires all three npm lifecycle hooks (preinstall, install, postinstall) to run beacon.js. beacon.js collects os.hostname(), os.userInfo(), and os.platform() and sends the installer's hostname, username, and OS to two hardcoded attacker-controlled collectors: a DNS lookup against the Interactsh OAST subdomain dbf2v9d8dg559apcd93guf6i7uxrn5coo.oast.pro and an HTTPS GET to webhook.site/59675304-bec1-4ca0-8409-8d37b65ec116 with the host identity in the query string. The scope+version combination (public @capsense scope, implausibly high 99.99.100) is the canonical dependency-confusion shape, intended to override a private internal @capsense package during resolution and fire the beacon on any internal build that pulls the public version. The self-label as a 'dependency-confusion PoC' does not change the behavior: any installer whose build resolves this package has their host identity shipped to third-party collectors without consent.
Source: ghsa-malware (ecd5f17a5f3f4128a9a96453aa873b5f447eccc12563702e0e84d8b63b0719b8)
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 (08a76d2425b34728eb502d47ba660eefd26e944864de58d8022e82c367dd55b2)
The OpenSSF Package Analysis project identified '@capsense/ccx-welcome-page' @ 99.99.100 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Affected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
All releases from the beginning; no upper bound recorded
No fix recorded for this interval.
2 explicitly affected versions
99.99.100, 99.99.99
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"99.99.100",
"99.99.99"
]
}