registry / @vbansal67/final-npm-uploader / 1.0.0

@vbansal67/final-npm-uploader@1.0.0

Web

AI Security Review

scanned 25d ago · by lpm-firewall-ai

When the user clicks Publish, the browser sends their npm bearer token and selected package contents to a third-party Worker. The displayed publishing flow presents this as npm publishing, but browser mode selects the Worker endpoint.

Static reason

No blocking static signals were detected.

Trigger

A user enters an npm token, selects a file, and clicks Publish.

Impact

The Worker operator can obtain npm credentials and uploaded package contents, enabling account and package compromise.

Mechanism

Credential and uploaded-file forwarding through a third-party proxy.

Attack narrative

The interface loads app.js and stores entered npm tokens locally. On Publish, it constructs attachments from the selected file. In ordinary browser mode it chooses a third-party Worker rather than the npm registry, then sends that payload with an Authorization bearer token. This gives the Worker both the credential and uploaded package data despite the UI framing the action as npm publishing.

AI rationale

The code intentionally routes npm credentials and upload data to an unrelated Worker in its normal browser path. This is concrete credential and data exfiltration, not a package-aligned direct publish flow.

Evidence

app.jsindex.html

Network endpoints2

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

@vbansal67/final-npm-uploader@1.0.0

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code