@capsense/ccx-welcome-page@99.99.100
Authorized security research placeholder for responsible disclosure to Microsoft MSRC (dependency-confusion PoC). Non-malicious: beacons package name and host only, no secrets. Please contact the reporter and reserve this scope.
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest activates the beacon automatically during installation, and the source shows identifying data sent to fixed external endpoints without installer consent. This is an install-time disclosure of machine and user identifiers, so blocking publication is warranted.
Decision evidence
public snapshot- package.json runs beacon.js in preinstall, install, and postinstall.
- beacon.js collects the machine hostname, username, and platform, then combines them with package and lifecycle identifiers.
- beacon.js sends the resulting identifier to a fixed OAST host and webhook.site during installation; no consent check is shown.
Source & flagged code
8 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs beacon.js in preinstall, install, and postinstall.
package.jsonView on unpkg · L7Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @capsense/ccx-welcome-page@99.99.100.
See all versions of @capsense/ccx-welcome-page for other recorded verdicts.
- Avoid installing @capsense/ccx-welcome-page@99.99.100. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.