@capsense/core-ui@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 lifecycle hooks and beacon source establish automatic disclosure of host and user identifiers to hardcoded external endpoints without installer consent. This supports blocking the package as install-time data exfiltration.
Decision evidence
public snapshot- All three npm install lifecycle stages automatically run beacon.js.
- The beacon reads the machine hostname, username, and platform and combines them with package and lifecycle identifiers.
- The beacon sends that identifying label through DNS and HTTPS to an OAST host and HTTPS to webhook.site.
- The OAST recipient is hardcoded in the package source.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgAll three npm install lifecycle stages automatically run beacon.js.
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/core-ui@99.99.100.
See all versions of @capsense/core-ui for other recorded verdicts.
- Avoid installing @capsense/core-ui@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.