registry / @vbansal67/npm-publishinginginginginging / 1.0.0

@vbansal67/npm-publishinginginginginging@1.0.0

Web

AI Security Review

scanned 25d ago · by lpm-firewall-ai

Opening the HTML publisher and clicking Publish sends an NPM bearer token and selected package contents through an unaffiliated Cloudflare Worker. The bundled token makes credential compromise immediately actionable.

Static reason

No blocking static signals were detected.

Trigger

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

Impact

The Worker operator can capture the token and uploaded package data, then publish, alter, or take over packages authorized by that token.

Mechanism

Credential and file forwarding through a third-party proxy.

Attack narrative

The package presents a package-publishing form with a prefilled NPM credential. In ordinary web use it routes the publish request through a Cloudflare Worker and includes the bearer token in the request headers. It also serializes the selected file or ZIP contents into the request payload. This gives the Worker operator both the credential and package data before any intended npm registry operation.

AI rationale

This is a concrete credential-exfiltration path disguised as an npm publisher, reinforced by an embedded NPM credential. The lack of lifecycle hooks does not mitigate the malicious behavior once the packaged browser entry point is opened.

Evidence

index.htmlapp.jspackage.json

Network endpoints2

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

@vbansal67/npm-publishinginginginginging@1.0.0

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code