@lensmcp/vite-plugin@1.25.41
LensMCP Vite plugin — valtio alias, source transform, and browser event bridge.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe default browser replay records password fields without masking and uploads those recordings to the local LensMCP bridge for storage. Although the destination defaults to loopback and the package is intended for observability, automatic unmasked credential capture is unrelated to ordinary event reporting and creates a concrete credential exposure risk.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Vite serves an app using the plugin with its default configuration and no replay-off setting.
Impact
Passwords entered into the observed app may be retained in replay files and exposed to local LensMCP processes or anyone with access to that storage.
Mechanism
The injected browser recorder leaves password inputs unmasked, then POSTs recordings to the plugin’s local replay endpoint, which stores them under `.lensmcp/replay` by default.
Attack narrative
When Vite serves an app with the default plugin configuration, session replay is enabled unless explicitly turned off. The recorder disables masking for password inputs and uploads replay data to the local bridge, which stores recordings under `.lensmcp/replay` by default. This can retain credentials entered into the observed app without explicit replay consent.
AI rationale
The default browser replay records password fields without masking and uploads those recordings to the local LensMCP bridge for storage. Although the destination defaults to loopback and the package is intended for observability, automatic unmasked credential capture is unrelated to ordinary event reporting and creates a concrete credential exposure risk.
Evidence
lib/plugin.jslib/replay-setting.js.lpm-dependency-evidence-d466afe7-36e2-4f76-85da-7a7f82c423eb/1/npm-linux/replay-source.js.lpm-dependency-evidence-d466afe7-36e2-4f76-85da-7a7f82c423eb/2/npm-linux/lib/replay-store.js.lensmcp/replay/**.lensmcp/capture.json
Network endpoints1
127.0.0.1:<dynamic-port>/replay
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- The plugin passes `replay: true` to its injected browser runtime whenever replay is enabled.
- Replay defaults to enabled when no environment setting, option, or capture-file setting disables it.
- The recorder defaults `maskAllInputs` to false and sets `maskInputOptions.password` to false, leaving password inputs unmasked.
- The recorder uploads replay data in POST request bodies to its configured endpoint.
- The plugin configures replay’s endpoint as HTTP on the bridge host and port; the bridge defaults to `127.0.0.1`.
- Replay data is stored under `.lensmcp/replay` by default, with an environment variable override.
Evidence against
- The package is an observability plugin, and its README describes streaming application events to LensMCP over a local WebSocket.
- The bridge defaults to loopback, and replay can be disabled with `LENSMCP_REPLAY=off`.
- The behavior runs when Vite serves the app; package metadata has no install lifecycle scripts.
Behavioral surface
EnvironmentVars
Source & flagged code
9 flaggedlib/plugin.jsView file
1package = @lensmcp/vite-plugin; repositoryIdentity = lensmcp; dependency = @babel/core
L1: "use strict";var z=Object.defineProperty;var g=(e,n)=>z(e,"name",{value:n,configurable:!0});var Z=Object.defineProperty,d=g((e,n)=>Z(e,"name",{value:n,configurable:!0}),"c");import...
L2: `);if(t!==B)return null;const u=f??e.wsPort??0,r=process.env.LENSMCP_APP||process.env.NX_TASK_TARGET_PROJECT;return buildInlineClientRuntime({host:p,port:u,token:o,hmrRecovery:e.hm...
L3: (() => {
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
lib/plugin.jsView on unpkg · L1•matchType = malicious_source_fingerprint_signature
signature = 118688338f0ed54a
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @lensmcp/vite-plugin@1.25.39
matchedPath = lib/plugin.js
matchedIdentity = npm:QGxlbnNtY3Avdml0ZS1wbHVnaW4:1.25.39
similarity = 1.000
shingleOverlap = 5
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
lib/plugin.jsView on unpkg2ken:o,hmrRecovery:e.hmrRecovery!==!1,...r?{app:r}:{},...b()?{replay:!0}:{}})},async transform(t,u){if(!s||!S)return null;const r=u.split("?")[0]??u;if(r.includes("/node_modules/")||!/\.[jt]sx$/.test(r))return n
Findings
9 High2 Medium1 Low
HighCopied Package Dependency Bridgelib/plugin.js
HighKnown Malware Source Fingerprint Signaturelib/plugin.js
HighAi Review Evidencelib/plugin.js
HighAi Review Evidencelib/replay-setting.js
HighAi Review Evidence.lpm-dependency-evidence-d466afe7-36e2-4f76-85da-7a7f82c423eb/1/npm-linux/replay-source.js
HighAi Review Evidence.lpm-dependency-evidence-d466afe7-36e2-4f76-85da-7a7f82c423eb/1/npm-linux/replay-source.js
HighAi Review Evidence.lpm-dependency-evidence-d466afe7-36e2-4f76-85da-7a7f82c423eb/1/npm-linux/replay-source.js
HighAi Review Evidencelib/plugin.js
HighAi Review Evidence.lpm-dependency-evidence-d466afe7-36e2-4f76-85da-7a7f82c423eb/0/npm-linux/lib/constants.js
MediumEnvironment Vars
Affected versions and remediation
This report applies to @lensmcp/vite-plugin@1.25.41.
See all versions of @lensmcp/vite-plugin for other recorded verdicts.
- Avoid installing @lensmcp/vite-plugin@1.25.41. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.