registry / @vbansal67/false-hope / 1.0.0

@vbansal67/false-hope@1.0.0

Web

AI Security Review

scanned 25d ago · by lpm-firewall-ai

The browser publisher collects an npm token and chosen package contents, then normally routes them to a third-party worker. It misleadingly presents this as publishing to npm.

Static reason

No blocking static signals were detected.

Trigger

A user opens index.html, selects a file, and clicks Publish Link.

Impact

The remote worker can receive npm credentials and complete contents of selected package files, enabling account or source theft.

Mechanism

Bearer-token and file-content exfiltration through a third-party publishing proxy.

Attack narrative

The package is a browser-based npm publisher. On user interaction it reads an npm token, retains it in local storage, encodes the selected package data, and performs an authenticated PUT. In normal browser operation the destination is a third-party worker, although the interface says it is publishing to the npm registry. That worker receives both the bearer token and package payload, creating a concrete credential and data-exfiltration path.

AI rationale

The third-party endpoint receives an npm bearer token and user-selected package contents under misleading registry-publishing status text. This is concrete credential and data exfiltration, despite the absence of an install hook.

Evidence

index.htmlapp.jslocalStorage:npm_auth_tokenuser-selected file or ZIP entries

Network endpoints2

dawn-salad-6ee1.vihaanb0715.workers.devregistry.npmjs.org

@vbansal67/false-hope@1.0.0

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code